Autonomous system detail

AS724

Not announced

Operated by DNIC-ASBLK-00721-00726 - United States Department of Defense (DoD).

Summary

// analyst note
Dormant legacy DoD ASN with no top-level RDAP registration event (only a 2025-09-12 'last changed' event) - a genuine registry gap, confirmed via untruncated re-fetch, not a policy-driven null. Four sources (RIPEstat, CAIDA, bgp.he.net, bgp.tools) agree on zero current announcements and zero BGP relationships; a single uncorroborated third-party claim of 6 prefixes/2 peers was rejected as stale.
// security note
NEUTRAL/DATED: no notable public abuse signal, BGP hijack, or NANOG-archive mention found for AS724 as of 2026-07-25; reflects absence of indexed search results, not a confirmed clean check against a live blocklist API.
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: Likely

AS724 is a legacy autonomous system registered to the U.S. Department of Defense that is currently dormant: four independent routing sources (RIPEstat, CAIDA AS Rank, bgp.he.net, bgp.tools) agree it announces zero IPv4 and zero IPv6 prefixes today, and bgp.he.net records it as absent from the global routing table since 2025-08-07.

The ASN sits inside DNIC-ASBLK-00721-00726, a single legacy pre-ARIN block covering AS721 through AS726 registered to org handle USDDD (United States Department of Defense). Operational administration runs through DISA-Columbus (the historical "DoD Network Information Center," DNIC), 300 North James Road, Whitehall, OH; the registrant org address is 3990 E. Broad Street, Columbus, OH.

Routing was not always dormant: RIPEstat's history shows AS724 first announced 205.66.11.0/24 on 2000-08-18 and last announced 140.2.64.0/18 on 2021-12-16, before going fully unrouted. CAIDA's AS Rank places it at 79,459 with a customer cone of a single ASN (itself), zero prefixes, and zero addresses — no customers, peers, or upstreams (degree total 0). It has no PeeringDB network entry, though the broader U.S. DoD PeeringDB org lists other ASNs from the same numeric neighborhood.

The autnum's top-level RDAP record carries no "registration" event — only a "last changed" event dated 2025-09-12 — so the true original allocation date is a genuine registry gap rather than a value we chose to omit; that gap was confirmed on a fresh, untruncated RDAP re-fetch.

Operator
United States Department of Defense (DoD); ARIN registrant handle USDDD; operationally administered by DISA-Columbus (DoD Network Information Center / DNIC), 300 North James Road, Whitehall, OH 43213 [Confirmed] — ARIN RDAP autnum
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum
Allocated
Unknown — the top-level autnum record for block AS721–AS726 (DNIC-ASBLK-00721-00726) carries no 'registration' eventAction, only a 'last changed' event dated 2025-09-12; verified via a fresh untruncated RDAP re-fetch (fetch-canonical.mjs --max-bytes 0) [Confirmed] — ARIN RDAP
Org status
active (ARIN RDAP autnum status "active"; associated entity records "validated"), checked 2026-07-25 [Confirmed] — ARIN RDAP
Contacts
disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (abuse; authoritative RIR ARIN); NOC/technical handle MIL-HSTMST-ARIN (registered 1993-05-26); admin/technical handle REGIS10-ARIN [Confirmed] — RIPEstat abuse-contact-finder, ARIN RDAP

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal, BGP incident, or NANOG-archive mention found for AS724 as of 2026-07-25; reflects absence of indexed search hits, not a confirmed clean check against a live blocklist API

[Unknown] — searched Spamhaus/AbuseIPDB-style threat-feed terminology and NANOG/seclists archives

Network & routing

Network type
government/military enterprise network, not a commercial ISP; part of a legacy pre-RIR classful DoD allocation block; not directly confirmed to carry NIPRNet traffic itself, inferred from operator identity [Likely] — ARIN RDAP, en.wikipedia.org/wiki/Defense_Information_System_Network
Size
dormant — 0 IPv4 / 0 IPv6 announced prefixes, 0 address estimate; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat, bgp.he.net, bgp.tools, CAIDA AS Rank (checked 2026-07-25)
Routing/peering
not currently routed — last seen in the global table 2025-08-07 (bgp.he.net); historical announcements ran 2000-08-18 to 2021-12-16 (RIPEstat routing-status); CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB network entry [Confirmed]. One uncorroborated third-party community source reports 6 IPv4 prefixes / 2 peers, contradicted by four independently agreeing Confirmed sources — treated as stale/unreliable, not used [Unknown]
RPKI
not assessable — AS724 announces no prefixes, so there are no ROAs to validate [Confirmed]
Notable usage
no discrete named public-facing service attributable to AS724; it is one of six ASNs (721–726) in a single legacy DoD block administered by DISA-Columbus for internal DoD network operations, consistent with backbone/administrative infrastructure rather than a branded service
[Unknown/Likely] — ARIN RDAP
Related ASNs
AS721 (block-start handle for DNIC-ASBLK-00721-00726); AS725 (fellow DoD ASN listed in the DoD PeeringDB org, id 17705); AS27064 (low-confidence community association via bgp.he.net, not RIB-verified) [Likely for AS721/AS725; Unknown for AS27064]
Analyst note
Dormant legacy DoD ASN inside a shared 721–726 block; no top-level RDAP registration date exists and no current routing was found across four sources. Live administrative identity resolves to DISA-Columbus, but no discrete service is attributable to AS724 specifically, and it has no PeeringDB presence.
[ 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.