Autonomous system detail

AS630

Not announced

Operated by DNIC-ASBLK-00616-00665 - United States Department of Defense (DoD).

Summary

// analyst note
Dormant DoD/DNIC-block ASN. WHOIS/RDAP resolves to a shared block record (AS616-AS665) administered by DISA-Columbus for the US DoD. All routing sources (RIPEstat, CAIDA, PeeringDB) agree on zero announcements, zero peers, zero cone. Not listed among PeeringDB's 20 public DoD ASNs.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17; IPinfo lists ASN type as Inactive with 0 ICMP-responsive IPs in its latest scan.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Medium

AS630 is registered under ARIN as part of DNIC-ASBLK-00616-00665, a single shared autnum block spanning AS616 through AS665, entirely allocated to the United States Department of Defense (DoD) under the historic DoD Network Information Center (DNIC) numbering scheme. The block-level RDAP record carries a top-level registration event dated 1990-04-19, with a most-recent "last changed" event on 2025-09-12; the record's registry status is "active" even though the ASN itself shows no live routing presence. The administrative/technical contact runs through the Defense Information Systems Agency's Columbus, Ohio facility (DISA-Columbus), while the registrant organization on file is the United States Department of Defense at a separate Columbus address. Every routing-data source consulted — RIPEstat, CAIDA AS Rank, and general BGP toolkits — agrees AS630 announces zero IPv4 and zero IPv6 prefixes, has no visible peers or upstreams, and sits in a singleton customer cone (itself only). CAIDA ranks it 79,459th globally, and IPinfo separately classifies it as an "Inactive" ASN type with zero ICMP-responsive addresses in its most recent scan. No public abuse or threat-intelligence signal was found for AS630 as of 2026-07-17. It does not appear in PeeringDB's DoD organization listing (20 sibling DoD ASNs are listed there; AS630 is not one of them), and no dedicated operator website, published peering policy, or verified notable-usage claim could be sourced — those aspects stay Unknown rather than guessed.

Operator
United States Department of Defense (DoD); block administered by DISA-Columbus (300 North James Road, Whitehall, OH 43213) [Confirmed] — https://rdap.arin.net/registry/autnum/630
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/630, RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1990-04-19 (ARIN RDAP autnum TOP-LEVEL registration event for the DNIC-ASBLK-00616-00665 block covering AS630); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/630 (corroborated independently by three research angles; entity-level dates for MIL-HSTMST-ARIN 1993-05-26, REGIS10-ARIN 2009-06-24, and the USDDD org record 2007-01-12 are decoys and were not used)
Org status
ARIN registry status "active" for the DNIC-ASBLK-00616-00665 block (registry-record status, not route-announcement activity) [Confirmed] — https://rdap.arin.net/registry/autnum/630
Contacts
abuse/technical/NOC — disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil, +1-844-347-2457 ext2; administrative/technical registration — disa.columbus.ns.mbx.arin-registrations@mail.mil [Confirmed] — https://rdap.arin.net/registry/autnum/630

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17; IPinfo lists the ASN type as "Inactive" with 0 ICMP-responsive IPs in its latest internet-wide scan

[Likely] — https://ipinfo.io/AS630, https://www.spamhaus.org/blocklists/spamhaus-blocklist/

Network & routing

Network type
U.S. federal government / military network infrastructure (DoD-internal), not a commercial transit or eyeball operator [Likely] — https://rdap.arin.net/registry/autnum/630, https://www.peeringdb.com/org/17705
Size / routing
dormant — 0 IPv4 and 0 IPv6 announced prefixes; 0/326 RIS peers seeing v4, 0/322 seeing v6; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS630, https://asrank.caida.org/asns/630
Routing/peering
NOT announced; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible; not listed among the 20 DoD ASNs in PeeringDB org/17705 [Confirmed] — https://asrank.caida.org/asns/630, https://stat.ripe.net/AS630, https://www.peeringdb.com/org/17705
RPKI
not assessable — AS630 announces no prefixes, so RIPEstat's rpki-validation check was skipped (requires a --prefix param) [Confirmed] — https://stat.ripe.net/AS630
Notable usage
Unknown/unverified — a third-party aggregator (ipinfo.io) loosely associates the block with mail.mil-style hostnames, but this reflects the DoD NIC hostmaster contact mailbox rather than a confirmed first-party claim of hosted services [Unknown] — https://ipinfo.io/AS630
Related ASNs / block
shared block registration AS616–AS665 (DNIC-ASBLK-00616-00665); the individual ASN 630 resolves to this block-level RDAP record [Confirmed] — https://rdap.arin.net/registry/autnum/630
Peering policy / website
Unknown — no public peering policy or dedicated operator website found; DISA's general site does not publish per-ASN or peering pages [Unknown] — https://www.disa.mil/
Analyst note
Encountered as a dormant DoD/DNIC-block ASN sharing a single ARIN autnum record with siblings across AS616–AS665; registry-active but zero live BGP presence across every routing source checked.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.