Autonomous system detail

AS219

Not announced

Operated by DNIC-AS-00219 - Navy Network Information Center (NNIC).

Summary

// analyst note
Dormant/legacy ASN. WHOIS resolves to NNIC (U.S. Navy/DoD); last seen routing 2008-12-02, withdrawn since. allocated_date 1988-08-09 is the autnum top-level registration event (nested entity dates 2006-09-21 / 2009-06-24 are decoys). All routing sources (RIPEstat, CAIDA, bgp.he.net, bgp.tools) agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-19; not in Spamhaus ASN-DROP, C0nw0nk/ASN-BlackList, brianhama/bad-asn-list, or NANOG abuse threads.
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

AS219 is a legacy autonomous system number registered under ARIN to the Navy Network Information Center (NNIC), a U.S. Department of Defense / Department of the Navy entity. The ARIN autnum record carries a top-level registration date of 1988-08-09, making it one of the lowest-numbered and oldest ASNs in existence — an ARPANET-era allocation. The key triage point for AS219 is that it is effectively dormant today: every routing source consulted (RIPEstat, CAIDA AS Rank, bgp.he.net, bgp.tools) agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, zero customers, and no IXP memberships. RIPEstat's routing history shows AS219 last originated a prefix (192.245.200.0/24) on 2008-12-02 and first appeared (199.208.197.0/24) on 2000-08-18; since then it has been withdrawn from the global table while the ARIN registration remains active — the expected posture for a reserved/legacy DoD slot. Its CAIDA AS rank of 79,459 sits near the bottom of the global ranking, reflecting complete routing inactivity, and its customer cone is a singleton (the ASN itself, 0 prefixes, 0 addresses). The registrant org NNIC sits at 2465 Guadalcanal Road, Bldg 1265, Virginia Beach, VA, with ARIN registration and abuse handling routed through DISA-Columbus, Ohio — a standard DoD ARIN practice rather than anything specific to AS219. NNIC administers 80+ ASNs for the Navy/DoD; AS219's own prior usage is not documented in any publicly accessible source. No notable public abuse signal was found as of June 2026 — not in Spamhaus ASN-DROP, the C0nw0nk or brianhama community blocklists, or NANOG archives — which is consistent with a clean, dormant ASN that announces no IP space and therefore presents no active surface for abuse.

Operator
Navy Network Information Center (NNIC) — U.S. Department of the Navy / DoD; ARIN org handle NNICN-1 [Confirmed] — ARIN RDAP autnum/219 registrant entity (corroborated by bgp.tools, ipinfo.io)
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP; RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1988-08-09 (ARIN registry date from the autnum TOP-LEVEL events[] registration event, NOT an IEEE date — IEEE publishes no ASN registration dates); last changed 2011-07-05 [Confirmed] — ARIN RDAP autnum top-level events
Org status
active U.S. federal government entity (Department of the Navy / DoD); ARIN registration and abuse via DISA-Columbus, OH (standard DoD practice) [Confirmed] — ARIN RDAP
Website
navy.mil (domain associated per IPinfo; the official site returned HTTP 403 and could not be fetched directly) [Likely] — ipinfo.io/AS219
Contacts
abuse disa.columbus.ns.mbx.arin-registrations@mail.mil; phone +1-844-347-2457 ext2; ARIN POC REGIS10-ARIN; registrant address 2465 Guadalcanal Road, Bldg 1265, Virginia Beach, VA 23459; admin contact 300 North James Road, Whitehall, OH 43213 [Confirmed] — ARIN RDAP, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-19 — not in Spamhaus ASN-DROP, the C0nw0nk/ASN-BlackList or brianhama/bad-asn-list community blocklists, or NANOG archives; NANOG hits are mechanical BGP-update reports only. Dormant ASN announcing nothing, so IP-level threat-feed inclusion is structurally impossible

[Confirmed] — github.com/C0nw0nk, github.com/brianhama, seclists.org/nanog

Network & routing

Network type
U.S. military / government (DoD) network; AS219 is legacy/dormant — not in the global routing table [Confirmed] — bgp.tools, ipinfo.io, bgp.he.net
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.tools (2026-06)
Routing/peering
NOT announced — 0 RIS peers seeing it (0/327 v4, 0/324 v6); 0 observed neighbours; CAIDA degree total 0 (customer 0, peer 0, provider 0); last seen routing 192.245.200.0/24 on 2008-12-02, first seen 199.208.197.0/24 on 2000-08-18 [Confirmed] — RIPEstat routing-status; no PeeringDB entry exists for AS219
[Confirmed] — peeringdb.com
RPKI
not assessable — AS219 announces no prefixes, so there are no ROAs to validate (RIPEstat rpki-validation skipped, no prefix to query) [Unknown] — RIPEstat rpki-validation
Notable usage
AS219 is one of 80+ ASNs assigned to NNIC for U.S. Navy/DoD network administration; NNIC manages large IP blocks for naval units under OTHER ASNs, but AS219 itself carries no active prefixes and its specific prior usage is not publicly documented [Confirmed for the inactivity; Likely for the broader NNIC ASN-count] — networksdb.io NNIC listing, bgp.tools
Analyst note
Encountered as a dormant legacy ASN registered to NNIC (U.S. Navy/DoD). The 1988-08-09 allocated_date is the autnum TOP-LEVEL registration event; nested entity dates (NNICN-1 2006-09-21, REGIS10-ARIN 2009-06-24) are decoys and were ignored. Clean, inactive ASN.
[ 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.