Autonomous system detail  ·  US flag US

AS718

Not announced

Last known operator United States Department of Defense (DoD). No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
Dormant DoD DNIC-block ASN with zero announcements across RIPEstat, CAIDA, bgp.tools, and bgp.he.net. allocated_date recorded as null because the autnum's top-level RDAP events[] genuinely carries no registration event (independently re-verified); a 2007-01-12 date exists only at the nested USDDD entity level and was excluded as a decoy. WebSearch was unavailable all session, so notable-usage and full abuse-history checks remain incomplete.
// security note
NEUTRAL/DATED/PARTIAL: no notable public abuse signal found as of 2026-07-25; Talos and Spamhaus lookups returned errors rather than confirmed-clean results; ASN is currently unrouted (0 prefixes), limiting abuse surface.
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  ·  10 sources  ·  How this page is checked

AS718 is a dormant, unrouted legacy autonomous system registered to the United States Department of Defense (DoD) under ARIN's DNIC (Defense/military) block, currently announcing zero IPv4 and zero IPv6 prefixes anywhere in the public routing table.

The ARIN RDAP registry lists the autnum's RIR handle as DNIC-AS-00718, status active, with contacts under "Network DoD" at DISA-Columbus (300 North James Road, Whitehall, OH 43213) and the registrant org listed as USDDD (3990 E. Broad Street, Columbus, OH 43218).

Routing data is unanimous across sources: RIPEstat shows 0 of 328 RIS peers seeing it on IPv4 and 0 of 324 on IPv6; CAIDA AS Rank places it at 79,459 with zero total degree (no customers, peers, or providers) and a customer cone of just itself, 0 prefixes, 0 addresses; bgp.tools and bgp.he.net independently corroborate zero originated prefixes and zero observed peers. RPKI posture is not assessable since there are no announced routes to validate.

The autnum's own top-level RDAP events[] carries only a "last changed" entry (2025-09-12); it has no top-level "registration" event, so the allocation date is genuinely absent from the authoritative record. A separate research angle surfaced a 2007-01-12 date, but that belongs to the nested USDDD *entity* object, not the autnum itself, and per this project's decoy rule should not be substituted in; it is recorded here only as a caveat.

No operator-official page documenting AS718's specific purpose was located — DISA's own site renders as an unpopulated JavaScript shell via automated fetch — and PeeringDB has no net object for this ASN (404), consistent with a non-commercial, non-advertising government allocation rather than an actively operated network.

Exposure
none observed — AS718 originates zero IPv4/IPv6 prefixes, so it has no live announced address space to serve as an attack or scanning source at this time.
Abuse signal
no notable public abuse reports found as of 2026-07-25, but this is a partial check — Cisco Talos and Spamhaus lookups returned errors (403/404) rather than confirmed-clean results, and WebSearch was unavailable all session.
RPKI
not assessable — zero announcements means no ROAs exist to validate against.
Registry hygiene
RDAP object is well-formed and status active, with a current abuse contact (disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil) on file via RIPEstat's abuse-contact-finder.
Operator
United States Department of Defense (DoD); ARIN RIR handle DNIC-AS-00718 [Confirmed] — https://rdap.arin.net/registry/autnum/718
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/718
Allocated
Unknown — the autnum's top-level RDAP events[] contains no "registration" event, only a "last changed" event dated 2025-09-12; independently re-verified with a full (non-truncated) re-fetch [Confirmed for the absence]. A 2007-01-12 date exists but is attached to the nested USDDD entity object, not the autnum top-level, and is excluded as a per-instruction decoy
[Likely misattributed if used] — https://rdap.arin.net/registry/autnum/718
Org status
active per ARIN RDAP autnum status field [Confirmed] — https://rdap.arin.net/registry/autnum/718
Contacts
disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil; tel +1-844-347-2457 ext2; DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — https://stat.ripe.net/AS718, https://rdap.arin.net/registry/autnum/718

Security/abuse context (NEUTRAL, DATED, PARTIAL)

no notable public abuse signal found as of 2026-07-25; Talos and Spamhaus lookups errored rather than confirming clean; ASN is currently unrouted, limiting abuse surface

[Likely] — https://bgp.he.net/AS718, https://ipinfo.io/AS718

Network & routing

Network type
Unrouted/legacy DoD DNIC-block ASN; not publicly documented in operator terms [Likely] — https://bgp.he.net/AS718, https://rdap.arin.net/registry/autnum/718
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS718, https://asrank.caida.org/asns/718
Routing/peering
NOT announced — 0/328 RIS peers (v4), 0/324 (v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers in any source; no PeeringDB net object (404) [Confirmed] — https://stat.ripe.net/AS718, https://asrank.caida.org/asns/718, https://www.peeringdb.com/api/net?asn=718
RPKI
not assessable — zero announced prefixes means no ROAs exist to validate [Confirmed] — https://stat.ripe.net/AS718
Notable usage
Unknown — no operator-official or third-party source documents a specific purpose for AS718; DISA's own site is an unrendered JS SPA inaccessible to automated fetch [Unknown] — https://rdap.arin.net/registry/autnum/718
Related ASNs
Unknown — no confirmed sibling ASNs within the DoD DNIC block were verified this pass [Unknown]
Analyst note
AS718 is a fully dormant DoD-registered ASN with no announced routes across every routing source checked. Two research angles disagreed on allocated_date (2007-01-12 vs. absent); the routing angle independently re-verified the RDAP autnum's top-level events[] and confirmed no registration event exists there, so allocated_date is recorded as null rather than substituting the entity-level date. WebSearch was unavailable all session (budget exhausted), so notable-usage and deeper abuse-history research is incomplete and should be re-run in a future cycle.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · as observed by RouteViews at 2026-09-20 · one collector view, not a global census
// 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.