Autonomous system detail

AS624

Not announced

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

Summary

// analyst note
AS624 is not standalone-registered; it falls inside the shared block object DNIC-ASBLK-00616-00665 (AS616-AS665). The autnum's own top-level RDAP events give allocated_date 1990-04-19 and last_updated 2025-09-12 — entity-level POC/org dates nested in the same response (1993, 2007, 2009, 2026) are decoys and were excluded. All routing sources agree AS624 is currently unannounced.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17; not in Spamhaus ASN-DROP/SBL, AbuseIPDB, GreyNoise, Shadowserver, or NANOG mailing-list archives specific to AS624.
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: High

AS624 is a legacy autonomous system number administered by ARIN within the shared registration block DNIC-ASBLK-00616-00665, which spans AS616 through AS665 and is registered to the United States Department of Defense (DoD), registrant handle USDDD. Administrative contacts route through DISA-Columbus (the Defense Information Systems Agency's Columbus, Ohio facility), which handles NOC, technical, and abuse functions for the block on behalf of the DoD Network Information Center. The autnum object's own top-level RDAP events show a registration date of 1990-04-19 and a last-changed date of 2025-09-12; several entity-level records nested in the same RDAP response carry different dates (1993, 2007, 2009, 2026) tied to individual point-of-contact and organization handles rather than the autnum itself, and those are correctly excluded here as decoys distinct from the autnum's own registration event. Every routing-data source consulted — RIPEstat, CAIDA AS Rank, and Hurricane Electric's BGP Toolkit — agrees AS624 is currently unannounced: zero IPv4 and IPv6 prefixes, zero observed BGP peers, and a CAIDA customer cone containing only itself. This pattern is typical of many DoD DNIC-block ASNs, which are often administratively reserved rather than actively routed on the public Internet. No notable public abuse or threat-intelligence signal specific to AS624 was found across Spamhaus, AbuseIPDB, GreyNoise, Shadowserver, or NANOG mailing-list archives.

Operator
United States Department of Defense (DoD); registrant handle USDDD; administered via the DoD Network Information Center / DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/624
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin); ARIN RDAP
Allocated
1990-04-19 — autnum top-level "registration" event; last changed: 2025-09-12 — autnum top-level "last changed" event [Confirmed, corroborated by 3 independent angles] — https://rdap.arin.net/registry/autnum/624
Org status
active at the registry level (autnum status "active"); registrant United States Department of Defense (DoD), handle USDDD [Confirmed] — https://rdap.arin.net/registry/autnum/624
Website
no dedicated public website exists for AS624 or a standalone "DoD Network Information Center" site; parent agency DISA's disa.mil "about" pages did not resolve to substantive content during verification [Unknown] — https://www.disa.mil/

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17 — not in Spamhaus ASN-DROP/SBL, AbuseIPDB, GreyNoise, Shadowserver, or NANOG mailing-list archives specific to AS624

[Likely] — https://www.spamhaus.org/blocklists/do-not-route-or-peer/, https://www.abuseipdb.com/

Abuse contact

disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil

[Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)

Network & routing

Network type
US federal government / military allocation, not a commercial or transit ISP ASN [Confirmed] — https://bgp.he.net/AS624
Routing status
NOT announced — 0 IPv4/IPv6 prefixes, 0 RIS peers seeing it (of 326 v4 / 322 v6 total peers), 0 observed neighbours, CAIDA AS rank 79459, customer cone = singleton (1 ASN, 0 prefixes, 0 addresses) [Confirmed] — RIPEstat routing-status, CAIDA AS Rank, https://bgp.he.net/AS624
Peering policy
none publicly published for AS624 or the DoD NIC; DISA's DISN Connection Process Guide governs how DoD components and mission partners connect to DISN but is not a commercial-style open peering policy [Likely] — https://dl.dod.cyber.mil/wp-content/uploads/connect/CPG/ConnProcGuide.html
RPKI
not assessable — AS624 announces no prefixes, so no ROAs exist to validate [Confirmed] — RIPEstat rpki-validation (skipped, requires a prefix)
Notable usage
no ASN-specific notable public usage was verified; consistent with an administratively reserved, not publicly routed DoD block ASN (distinct from AS8003 GRS-DoD, which was involved in the 2021 "dark IP space" announcements) [Likely] — https://bgp.he.net/AS624
Registry block
DNIC-ASBLK-00616-00665 (AS616–AS665), a single shared RDAP object; AS624 has no standalone per-ASN registration in ARIN's system [Confirmed] — https://rdap.arin.net/registry/autnum/624
Decoy dates excluded
entity-level dates (MIL-HSTMST-ARIN registration 1993-05-26 / last changed 2026-02-12; REGIS10-ARIN registration 2009-06-24 / last changed 2026-02-12; USDDD org registration 2007-01-12 / last changed 2025-03-13) belong to POC/org handles nested under the autnum, not the autnum's own top-level events, and were correctly excluded from allocated_date
[Confirmed] — ARIN RDAP autnum entities[]
[ 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.