Autonomous system detail  ·  US flag US

AS162

Not announced

Last known operator Navy Network Information Center (NNIC), US DoD (administered under DISA). No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
Dormant legacy DoD ASN; WHOIS resolves to NNIC under DISA. Registry-active but unrouted (0/327 IPv4 and 0/320 IPv6 RIS peers; CAIDA rank 79459, cone of self only). Routing and abuse nulls are sourced and consistent across RIPEstat, CAIDA, bgp.he.net, and bgp.tools.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-16 (no Spamhaus/AbuseIPDB/CleanTalk/FraudGuard listing, no BGP-hijack record, no NANOG security mention).
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  ·  8 sources  ·  How this page is checked

AS162 is a very-low-number, legacy Autonomous System Number registered through ARIN to the Navy Network Information Center (NNIC), a US Navy element administered under the Defense Information Systems Agency (DISA). Its ARIN handle is DNIC-AS-00162 — the "DNIC" prefix marks it as part of the Department of Defense's historic Data Network Identification Code block — and the AS162 record carries a registration event of 1988-03-01, placing it among the earliest autonomous systems ever assigned. The registrant org record (NNICN-1) lists 2465 Guadalcanal Road, Building 1265, Virginia Beach, VA 23459, while administrative and abuse contact routes to DISA Columbus (300 North James Road, Whitehall, OH 43213) via disa.columbus.ns.mbx.arin-registrations@mail.mil. The key triage point is that the registry record is active but the ASN is operationally dormant: as of June 2026 it announces zero IPv4 and zero IPv6 prefixes and is not present in the global routing table. RIPEstat shows 0 of 327 IPv4 RIS peers and 0 of 320 IPv6 RIS peers seeing it; CAIDA reports rank 79459 with a customer cone of just itself, zero AS-degree, no IXP presence, and no clique membership. With no announced address space there is no observable RPKI posture and no attack surface — consistent with the absence of any abuse-feed listing, blocklist entry, BGP-hijack record, or NANOG security mention found across the sources checked. NNIC the organisation remains active (org record last updated 2025-03-13) and holds many other DoD ASNs; AS162 itself is best described as a reserved/legacy DoD ASN that is no longer routed in the public DFZ.

Operator
Navy Network Information Center (NNIC), a US Navy / DoD entity administered under DISA (ARIN OrgId NNICN-1, Virginia Beach, VA) [Confirmed] — ARIN RDAP/WHOIS
Country / RIR
US, ARIN [Confirmed] — https://whois.arin.net/rest/asn/AS162
Allocated
ARIN AS162 registration event 1988-03-01 (one of the earliest ASN assignments); AS record last changed 2011-07-05; registrant org NNICN-1 registered 2006-09-21, last updated 2025-03-13 [Confirmed] — https://rdap.arin.net/registry/autnum/162
Org status
active US federal entity (NNIC under DISA); registrant org record NNICN-1 last updated 2025-03-13 — the organisation is active even though AS162 itself is dormant [Confirmed] — https://whois.arin.net/rest/org/NNICN-1

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-16 — no Spamhaus/AbuseIPDB/CleanTalk/FraudGuard listing, no BGP-hijack record, no NANOG security thread; the null reflects the ASN's dormant routing state (no exposed IPs), not a coverage gap

[Confirmed] — bgp.tools / bgp.he.net

Network & routing

Network type
US federal military/government network; legacy DoD ASN, currently dormant (announces no prefixes, absent from the global routing table) [Confirmed] — bgp.tools / bgp.he.net
Size
zero announced address space — 0 IPv4 prefixes, 0 IPv6 prefixes, 0 IPs; CAIDA customer cone = 1 ASN / 0 prefixes / 0 addresses [Confirmed] — bgp.he.net / RIPEstat / CAIDA (2026-06)
Routing/peering
not announced; 0/327 IPv4 RIS peers and 0/320 IPv6 RIS peers seeing it; 0 observed BGP neighbours; no upstreams, peers, or customers; no IXP presence (CAIDA ixp=null); RPKI posture Unknown (no prefixes announced, so no ROAs observable)
[Confirmed for the null routing state] — RIPEstat / bgp.he.net / bgp.tools
Notable usage
legacy DoD/USN ASN (handle DNIC-AS-00162) registered 1988-03-01; NNIC operates many other DoD autonomous systems, but AS162 specifically carries no active address space [Confirmed] — https://whois.arin.net/rest/asn/AS162
Related ASNs
NNIC holds numerous other DoD ASNs (e.g., AS22, AS37, AS48, AS84, AS89, AS139, AS141, AS148) [Likely] — ipinfo.io / networksdb.io
Analyst note
Encountered as a dormant legacy DoD ASN; WHOIS resolves to NNIC under DISA. Registry-active but unrouted; the sourced abuse/routing nulls are honest data, not gaps.
[ 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.