Autonomous system detail

AS723

Not announced

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

Summary

// analyst note
Shared-block RDAP record (AS721-AS726), not a per-ASN record. allocated_date is genuinely Unknown: the autnum's top-level events[] array holds only a 'last changed' entry (2025-09-12), no top-level 'registration' event; the entity-level USDDD org date (2007-01-12) is a decoy tied to the contact record, not the ASN. Routing is fully corroborated as dormant (0 prefixes, 0 peers) across RIPEstat, CAIDA ASRank, and bgp.he.net.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-25; not in Spamhaus, AbuseIPDB, general threat feeds, or NANOG archives.
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

AS723 is a dormant, unrouted autonomous system number registered under ARIN to the United States Department of Defense (DoD), operationally managed by the Defense Information Systems Agency (DISA). As of July 2026 it announces zero IPv4 and zero IPv6 prefixes, has zero observed BGP peers or upstreams, and carries a CAIDA AS Rank of 79,459 — consistent with an ASN not currently used on the public Internet.

AS723 sits inside DNIC-ASBLK-00721-00726, a shared ARIN block covering AS721 through AS726 that is registered as a single RDAP object to the DoD (org handle USDDD, 3990 E. Broad Street, Columbus, OH). Because the record is block-level rather than per-ASN, several fields — including the allocation date — describe the block as a whole, not AS723 individually.

The RDAP autnum object's top-level events array carries only a "last changed" entry (2025-09-12); it holds no top-level "registration" event, so the original allocation date cannot be confirmed from this record. Entity-level dates nested under contacts, such as the USDDD org's 2007-01-12 registration, describe those contact records rather than the ASN's own allocation, and are not substituted here.

DISA operates the DODIN (Department of Defense Information Network) and its DISN transport layer, connecting to commercial/Internet networks only through DoD CIO-approved Access/Peering Gateways as a matter of general DISN architecture policy. No AS723-specific peering policy, PeeringDB record, or named service ties to this ASN individually; it is presumed part of DoD's broader legacy DNIC ASN holdings.

Operator
United States Department of Defense (DoD); network operationally managed by the Defense Information Systems Agency (DISA), a DoD combat support agency. ARIN registrant org handle USDDD. [Confirmed] — https://rdap.arin.net/registry/autnum/723
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/723
Allocated
Unknown — the autnum RDAP record's top-level events[] array contains only a "last changed" entry (2025-09-12); no top-level "registration" event is present in this shared block record. Entity-level dates (e.g. USDDD org 2007-01-12) belong to contact records, not the ASN's own allocation.
[Confirmed] — https://rdap.arin.net/registry/autnum/723
ASN block
part of DNIC-ASBLK-00721-00726 (AS721–AS726), a shared DNIC block registered to USDDD, 3990 E. Broad Street, Columbus, OH 43218 [Confirmed] — https://rdap.arin.net/registry/autnum/723
Org status
Active per ARIN RDAP status field; registrant is the US Department of Defense, a federal government entity; DISA (referenced in admin/tech contacts) is a DoD combat support agency headquartered at Fort Meade, MD [Confirmed] — https://rdap.arin.net/registry/autnum/723
Contacts
disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (abuse/technical/noc, MIL-HSTMST-ARIN); disa.columbus.ns.mbx.arin-registrations@mail.mil (REGIS10-ARIN); 300 North James Road, Whitehall, OH 43213 [Confirmed] — https://rdap.arin.net/registry/autnum/723

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 — not in Spamhaus, AbuseIPDB, general threat feeds, or NANOG archives; dormant DoD-held legacy ASN

[Likely] — https://www.spamhaus.org/blocklists/spamhaus-blocklist/, https://www.abuseipdb.com/

Network & routing

Network type
US federal government / military network; DISA operates the DODIN/DISN infrastructure; not a commercial ISP or hosting provider [Likely] — https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/801001p.pdf
Size
dormant — 0 IPv4/IPv6 prefixes, 0 address estimate; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://asrank.caida.org/asns/723, https://stat.ripe.net/AS723
Routing/peering
NOT announced — 0 RIS peers observing it (0/331 v4, 0/324 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in RIPEstat, CAIDA, or bgp.he.net [Confirmed]. No AS723-specific PeeringDB record (404) or public peering policy; general DISN policy routes external connections through DoD CIO-approved Access/Peering Gateways
[Likely] — https://www.peeringdb.com/asn/723, https://dl.dod.cyber.mil/wp-content/uploads/connect/pdf/unclass-DISN_CPG.pdf
RPKI
not assessable — no announced prefixes, so there are no ROAs to validate [Confirmed] — https://stat.ripe.net/AS723
Notable usage
no AS723-specific usage documentation found; presumed part of DoD's broader legacy DNIC ASN holdings operated under DISA's DODIN/DISN infrastructure [Unknown]
Related ASNs
part of the AS721–AS726 shared DNIC block; sibling DoD ASNs exist elsewhere in DNIC space (e.g. AS749, which does have a PeeringDB record) [Likely] — https://www.peeringdb.com/asn/723
Last changed
2025-09-12 (RDAP top-level "last changed" event) [Confirmed] — https://rdap.arin.net/registry/autnum/723
Analyst note
Shared block RDAP record (AS721–AS726) rather than a per-ASN record; allocated_date is left Unknown because the top-level events[] array carries only a "last changed" entry, and the entity-level 2007-01-12 date belongs to the USDDD org contact, not the ASN itself. Routing is unambiguous across RIPEstat/CAIDA/bgp.he.net: fully dormant, zero announcements.
[ 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.