Autonomous system detail

AS214

Not announced

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

Summary

// analyst note
Dormant/legacy DoD/Navy ASN. RDAP status active and NNIC org administratively current, but no BGP announcements since early 2010. 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 DROP/SBL, CleanTalk, AbuseIPDB, 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

AS214 is a legacy autonomous system number registered under ARIN to the Navy Network Information Center (NNIC), the U.S. Department of the Navy entity that administers routing and IP-address allocation for Navy facilities. It was allocated on 1988-07-12, placing it among the earliest entries in the IANA 16-bit AS Numbers registry (block 1–1876, assigned by ARIN). The number carries the DNIC (Defense Network Information Center) naming convention used across the Navy's ~90 ASNs and is one of a large family of low-numbered DoD allocations. The triage point for AS214 is that it is effectively dark 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 peers, zero upstreams, and zero customers. RIPEstat reports 0 of 327 IPv4 RIS peers and 0 of 324 IPv6 RIS peers seeing it as of 2026-06-19. CAIDA ranks it 79,459 with an asnDegree of 0 across all dimensions and a singleton customer cone (the ASN itself, 0 prefixes, 0 addresses). The only historical routing trace is prefix 188.116.64.0/18, first seen 2009-12-05 and last seen 2010-03-16 — the ASN has been routing-dark since early 2010. RPKI posture is not assessable because there are no active originations and therefore no ROAs. No notable public abuse signal was found as of June 2026 — not in Spamhaus DROP/SBL, CleanTalk, AbuseIPDB, or NANOG archives — which is structurally expected for a dormant government/military allocation with no attack surface. The NNIC organization itself remains administratively active in ARIN (admin contact record last touched 2026-02-12); abuse and registration contacts route through DISA-Columbus.

Operator
Navy Network Information Center (NNIC), U.S. Department of the Navy (ARIN handle AS214 / DNIC-AS-00214) [Confirmed] — ARIN RDAP, ipinfo.io/AS214, bgp.he.net/AS214
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), CAIDA (country ISO=US)
Allocated
1988-07-12 (ARIN RDAP autnum top-level registration event — a first-party RIR fact, NOT an IEEE date); RDAP record last changed 2011-07-05 [Confirmed] — rdap.arin.net/registry/autnum/214
ASN block
IANA 16-bit AS Numbers registry block 1–1876, assigned by ARIN [Confirmed] — RIPEstat as-overview
Org status
active U.S. federal government entity (Department of the Navy); ARIN admin contact record last updated 2026-02-12 (org remains active), while AS214 itself is dormant/not actively routed [Confirmed] — ARIN RDAP, ipinfo.io
Website
navy.mil (primary domain per ARIN/IPinfo records; no dedicated NNIC subdomain or standalone site found) [Likely] — ipinfo.io/AS214, ip2location.com/as214
Contacts
abuse / registration via disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus); registrant address 2465 Guadalcanal Road, Building 1265, Virginia Beach, VA 23459 [Confirmed] — RIPEstat abuse-contact-finder, ARIN RDAP entity vcard

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-19 — not in Spamhaus DROP/SBL, CleanTalk ASN blacklist, AbuseIPDB, or NANOG archives; expected for a dormant government/military allocation with no active prefixes and no attack surface

[Confirmed] — spamhaus.org, cleantalk.org, ipinfo.io, bgp.tools

Network & routing

Network type
U.S. federal government / military — Department of the Navy internal network infrastructure; AS214 is one of ~90 ASNs held by NNIC under the DNIC naming convention [Confirmed] — ARIN RDAP, networksdb.io (NNIC), peeringdb.com/org/18365
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses — RIPEstat routing-status / CAIDA AS Rank (2026-06)
Routing/peering
NOT announced — 0/327 IPv4 RIS peers and 0/324 IPv6 RIS peers seeing it; CAIDA asnDegree total 0 (customer 0, peer 0, provider 0); observed_neighbours 0; no PeeringDB entry for AS214 specifically [Confirmed] — RIPEstat routing-status, CAIDA, bgp.he.net
Historical routing
only trace is prefix 188.116.64.0/18 (16,384 addresses), origin AS214, first seen 2009-12-05, last seen 2010-03-16 — routing-dark since [Confirmed] — RIPEstat routing-status
RPKI
not assessable — AS214 announces no prefixes, so there are no ROAs to validate (rpki-validation skipped, no prefix to supply) [Confirmed] — RIPEstat rpki-validation
AS rank
79,459 (CAIDA AS Rank; seen=false, cliqueMember=false, ixp=null — not observed in the current global routing table) [Confirmed] — CAIDA asrank
Related ASNs
NNIC holds ~90 ASNs under the DNIC convention (e.g. AS22, AS84, AS219, AS256, AS257, AS768, AS2749, AS5058 among others) [Likely per third-party DB] — networksdb.io (NNIC), bgp.tools
Analyst note
Encountered as a dormant legacy DoD/Navy ASN. RDAP status is active and the NNIC org is administratively current, but the number has carried no BGP announcements since early 2010. Clean, inactive ASN; community/forum corroboration is sparse, consistent with a low-profile military network rather than a data gap.
[ 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.