AS208

AS208 is a legacy autonomous system number registered under ARIN to the Navy Network Information Center (NNIC), a U.S. Department of Defense entity tied to the U.S. Navy and the historical Defense Network Information Center (DNIC) numbering block. The registry name DNIC-AS-00208 reflects that early DoD allocation lineage, and the registrant address resolves to 2465 Guadalcanal Road, Building 1265, Virginia Beach, VA, with ARIN registration administration handled by DISA-Columbus in Whitehall, OH (abuse/registration contact disa.columbus.ns.mbx.arin-registrations@mail.mil). The triage point for AS208 is that it is effectively dormant: every routing source consulted — RIPEstat, CAIDA AS Rank, bgp.he.net, and bgp.tools — agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, zero customers, and no IXP presence. RIPEstat's routing history shows AS208 was last seen in the global table on 2009-10-14 announcing 164.221.0.0/16, having first appeared on 2000-10-31; it has originated nothing since. Its CAIDA AS rank of 79,459 sits near the bottom of the global ranking, with a singleton customer cone (the ASN itself, 0 prefixes, 0 addresses). RPKI posture cannot be assessed because there are no active originations and therefore no ROAs to validate. No notable public abuse signal was found as of June 2026 — AS208 is absent from Spamhaus ASN-DROP and the ipapi.is abusive-ASN list, and no NANOG route-leak, hijack, or abuse discussion naming it was located — consistent with a clean, dormant ASN held by a U.S. government operator. (Caveat: military/DoD incidents may be classified and not publicly disclosed.) NNIC holds a large block of early/legacy ASNs; abuse on sibling ASNs is not attributed to AS208.

Operator

Navy Network Information Center (NNIC), a U.S. DoD / U.S. Navy entity (ARIN org handle NNICN-1; registrant Virginia Beach, VA) [Confirmed] — ARIN RDAP autnum/208, whois.arin.net/rest/asn/AS208

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin); ARIN RDAP

Allocated

1988-06-22 (ARIN registry date from autnum top-level registration event, a first-party RIR fact, NOT an IEEE date); last changed 2011-07-05 [Confirmed] — ARIN RDAP autnum/208 top-level events

Org status

active ARIN registration (handle NNICN-1); ASN allocated 1988-06-22, last modified 2011-07-05; ASN itself dormant (no BGP announcements as of 2025–2026); contact entity REGIS10-ARIN last validated 2026-02-12 [Confirmed] — ARIN RDAP autnum/208, entity/NNICN-1

Contacts

disa.columbus.ns.mbx.arin-registrations@mail.mil (abuse/registration, DISA-Columbus, Whitehall OH); registrant 2465 Guadalcanal Road, Bldg 1265, Virginia Beach, VA 23459 [Confirmed] — ARIN RDAP, RIPEstat abuse-contact-finder

Website

no dedicated public website identified for NNIC or AS208; the U.S. Navy's main domain is navy.mil [Confirmed for absence] — ARIN RDAP

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-19 — not in Spamhaus ASN-DROP, not on ipapi.is abusive-ASN list, no NANOG discussion naming AS208; CleanTalk inaccessible (HTTP 403). With 0 prefixes originated there is effectively no live IP space to source spam/scanning/DDoS. Caveat: DoD incidents may be classified [Confirmed for the listing checks; Likely overall] — spamhaus.org/drop/asndrop.json, ipapi.is/most-abusive-asn.html, bgp.tools/as/208

Network & routing

Network type

U.S. Government / Military — DoD / U.S. Navy network infrastructure (DNIC numbering lineage); AS208 is legacy/inactive [Confirmed] — ARIN RDAP, networksdb.io NNIC profile

Size

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

Routing/peering

NOT announced (RIPEstat as-overview announced=false) — 0 RIS peers seeing it (0/327 v4, 0/323 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source. No PeeringDB record (404), so no published peering policy — Unknown [Confirmed for routing inactivity; Unknown for policy] — RIPEstat routing-status/as-overview, peeringdb.com/asn/208, bgp.tools/as/208

Routing history

first seen 2000-10-31 (164.221.192.0/21); last seen 2009-10-14 (164.221.0.0/16); withdrawn since [Confirmed] — RIPEstat routing-status

RPKI

not assessable — AS208 announces no prefixes, so there are no ROAs to validate (RIPEstat rpki-validation skipped: no prefix to check) [Unknown] — RIPEstat

Notable usage

AS208 (DNIC-AS-00208) is one of many early/legacy ASNs registered to NNIC; the portfolio spans Navy NIPRNET segments and various military base/command networks. AS208 itself is currently inactive with no advertised prefixes [Confirmed for inactivity; Likely for broader portfolio per third-party DB] — networksdb.io NNIC profile, bgp.tools/as/208, ipinfo.io/AS208

Analyst note

Encountered as a dormant legacy DoD/Navy ASN; WHOIS resolves to NNIC, last live routing was a /16 withdrawn in 2009. Clean, inactive ASN. Entity/org-level registration dates (org 2006-09-21, contact 2009-06-24) are decoys — the allocated_date is the autnum top-level 1988-06-22.