AS788

AS788 is a legacy U.S. Department of Defense (Navy) autonomous system, registered under ARIN as DNIC-AS-00788 to the Navy Network Information Center (NNIC). Its ARIN RDAP registration status is active, but the ASN currently announces zero IPv4 and zero IPv6 prefixes — it is not present on the live global routing table.

The autnum's top-level RDAP registration event dates to 1990-12-02, with a last-changed event of 2011-07-15 — both read from the RDAP autnum object's top-level events array rather than the nested registrant/contact entities, and independently corroborated by bgp.tools, which separately cites the same December 2, 1990 registration date. This places AS788 among the older DoD Network Information Center (DNIC) legacy allocations still on record.

Every routing source checked — RIPEstat, CAIDA AS Rank, bgp.he.net, and bgp.tools — agrees the ASN is currently unrouted: 0 announced prefixes, 0/328 RIS peers observing it on IPv4, 0/322 on IPv6, and no visible upstreams or peers. CAIDA ranks it 79,459 with a customer cone of one ASN (itself), zero prefixes, zero addresses. No operator-run website, peering-policy page, or PeeringDB network record was found for AS788 itself (peeringdb.com/asn/788 returns 404).

Abuse and administrative contact is delegated to DISA-Columbus (disa.columbus.ns.mbx.arin-registrations@mail.mil). Registrant contact records list Virginia Beach, VA, with the technical/abuse point of contact in Whitehall, OH — mailing addresses only, not verified network point-of-presence locations, since the ASN announces no routes.

Operator

Navy Network Information Center (NNIC); ARIN handle DNIC-AS-00788; admin/technical/abuse contact delegated to DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/788

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/788

Allocated

1990-12-02 (ARIN RDAP autnum top-level registration event, NOT a nested entity/registrant event); last changed 2011-07-15 [Confirmed] — https://rdap.arin.net/registry/autnum/788, corroborated independently by https://bgp.tools/as/788

Org status

ARIN RDAP registration status is active, but the ASN is not currently announced/routed on the global Internet [Confirmed] — https://rdap.arin.net/registry/autnum/788, https://stat.ripe.net/AS788

Contacts

abuse/admin/tech — disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus); registrant mailing address Virginia Beach, VA; technical/abuse POC mailing address Whitehall, OH [Confirmed for abuse contact via RIPEstat; Likely for addresses via RDAP entity records]

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-08-01 — not in Spamhaus material, NANOG mailing-list archives, or general web search naming AS788 or NNIC; search coverage is partial (no direct Spamhaus SBL/DROP lookup tool or NANOG full-text archive search was available)

Network & routing

Network type

U.S. DoD (Navy) legacy/government network; not a commercial ISP or content network [Likely] — https://rdap.arin.net/registry/autnum/788

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status, CAIDA AS Rank, bgp.he.net, bgp.tools (2026-08)

Routing/peering

NOT announced — 0/328 RIS peers seeing it on IPv4, 0/322 on IPv6; CAIDA degree total 0 (0 upstreams, 0 peers); no PeeringDB network record exists for AS788 itself (peeringdb.com/asn/788 returns 404) [Confirmed]

RPKI

not assessable — AS788 announces no prefixes, so there are no routes to validate; bgp.he.net shows 0 RPKI-valid and 0 RPKI-invalid origins [Confirmed for the absence of routes]

Notable usage

Unknown — no operator-official documentation of notable usage found; third-party ASN databases (ipinfo.io, db-ip, ip2location) describe it generically as an NNIC/DoD legacy allocation [Unknown]

Related ASNs

other NNIC/DoD-associated ASNs appear in third-party/PeeringDB listings under separate ASN numbers (e.g. AS22, AS84, AS257, AS2749) — these are distinct ASNs, not AS788 itself, and their PeeringDB presence does not apply to AS788 [Likely, per third-party DB]

Analyst note

A dormant-but-actively-registered DoD/Navy legacy ASN. RDAP registration is valid and dated 1990-12-02 (top-level event, cross-validated by bgp.tools), but no routing activity, peering, or public operator presence exists today. Notable-usage and website claims are recorded as sourced Unknown rather than fabricated.