Autonomous system detail

AS191

Not announced

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

Summary

// analyst note
1988-era DoD/Navy legacy ASN. WHOIS resolves to NNIC; admin contact routed through DISA-Columbus. All routing sources (RIPEstat, CAIDA, bgp.tools, ipinfo.io) agree on zero announcements, zero peers, zero cone. ASN range 1-1876 assigned by ARIN.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-19; not in Spamhaus ASN-DROP, CleanTalk, AbuseIPDB, blocklist.de, 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

AS191 is a legacy autonomous system number registered under ARIN to the Navy Network Information Center (NNIC), the U.S. Navy / Department of Defense organization that manages naval network address space. The "DNIC-AS-00191" handle follows the Defense Network Information Center (DNIC) naming convention applied across DoD ASN registrations, and the org handle NNICN-1 lists a registrant address in Virginia Beach, VA. AS191 is one of the oldest ASNs in existence: the ARIN RDAP autnum top-level registration event is dated 1988-05-18, contemporaneous with the early DDN/ARPANET era, and the record was last changed 2011-07-05. The key triage point for AS191 is that it is allocation-active but effectively dormant: every routing source consulted (RIPEstat, CAIDA AS Rank, bgp.tools, ipinfo.io) agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, and zero observed neighbours. RIPEstat sees 0 of 327 v4 RIS peers and 0 of 323 v6 RIS peers carrying it, CAIDA marks seen=false with a rank of 79,459, and its customer cone is a singleton (the ASN itself, 0 prefixes, 0 addresses). It does not appear among NNIC's currently active ASNs on PeeringDB, which is consistent with a legacy/decommissioned allocation retained within the DoD's large historical ASN portfolio. RPKI posture cannot be assessed because there are no active originations and therefore no ROAs. No notable public abuse signal was found as of June 2026 — AS191 is absent from the Spamhaus ASN-DROP feed and from CleanTalk, AbuseIPDB, and NANOG archives — which is unsurprising for a non-routing ASN that carries no live IP space.

Operator
Navy Network Information Center (NNIC) (U.S. Navy / DoD; org handle NNICN-1; ASN handle DNIC-AS-00191) [Confirmed] — ARIN RDAP autnum, whois.arin.net/rest/asn/AS191
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), ARIN RDAP
Allocated
1988-05-18 (ARIN registry date from the autnum top-level 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 ARIN allocation (ASN status: active) but effectively dormant on the public DFZ; registrant Navy Network Information Center (NNIC), 2465 Guadalcanal Road, Bldg 1265, Virginia Beach, VA 23459, US [Confirmed] — ARIN RDAP autnum
IANA block
ASN range 1–1876, assigned by ARIN (IANA 16-bit Autonomous System Numbers Registry) [Confirmed] — RIPEstat as-overview
Contacts
admin/abuse via DISA-Columbus (Defense Information Systems Agency), 300 North James Road, Whitehall, OH 43213; email disa.columbus.ns.mbx.arin-registrations@mail.mil; phone +1-844-347-2457 ext. 2 (contact handle REGIS10-ARIN) [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 (430-entry feed checked; AS191 absent), CleanTalk, AbuseIPDB, blocklist.de, or NANOG archives; a non-routing ASN carries no live IP space to generate abuse, though it remains a theoretical hijack candidate if an adversary originated prefixes under it

[Confirmed] — spamhaus.org/drop/asndrop.json, bgp.tools/as/191

Network & routing

Network type
U.S. Department of Defense / U.S. Navy military network; AS191 is legacy/inactive within NNIC's large ASN portfolio [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.tools / ipinfo.io (2026-06)
Routing/peering
NOT announced — 0 RIS peers seeing it (0/327 v4, 0/323 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); 0 observed neighbours; no upstreams or peers visible in any source [Confirmed]. No PeeringDB entry for AS191; no operator-specific peering policy document found [Confirmed]
RPKI
not assessable — AS191 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation skipped (no prefix supplied) [Unknown]
Notable usage
AS191 (DNIC-AS-00191) is an early/legacy DoD ASN registered May 1988 (DDN/ARPANET era) to NNIC, which manages Navy and DoD IP space including NIPRNET-adjacent blocks; it carries no active routes as of June 2026 and is likely a dormant allocation within DoD's historical ASN holdings
[Likely] — ARIN RDAP, networksdb.io NNIC profile, en.wikipedia.org/wiki/Defense_Data_Network
Analyst note
Encountered as a 1988-era DoD/Navy legacy ASN that is allocation-active in ARIN but announces nothing on the public Internet. WHOIS resolves to NNIC with administrative contact routed through DISA-Columbus. 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.