Autonomous system detail

AS287

Not announced

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

Summary

// analyst note
Dormant/legacy ASN. WHOIS resolves to NNIC (U.S. Navy / DoD), but the AS has announced no prefixes since circa April 2017. RIPEstat, CAIDA all agree on zero announcements, zero peers, zero cone. allocated_date taken from the ARIN RDAP autnum top-level registration event (1989-05-17), not the org/contact entity dates.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-25; Scamalytics rates the NNIC ISP entity 0/100 fraud risk; no Spamhaus DROP listing, BGP hijack, route leak, or NANOG complaint identified for AS287.
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

AS287 is a legacy autonomous system number registered under ARIN to the Navy Network Information Center (NNIC), a U.S. Navy / Department of Defense entity that serves as the Navy's internal network registry and IP-management authority rather than a commercial ISP. The ASN dates to 1989-05-17 per ARIN RDAP, placing it among the earliest ASN assignments and consistent with the DoD's foundational role in the early Internet. The key triage point for AS287 is that it is effectively dormant today: every routing source consulted (RIPEstat as-overview and routing-status, CAIDA AS Rank) agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, zero customers, and no IXP memberships. 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). RIPEstat's RIS history shows the AS last carried a single prefix — 130.22.176.0/22 — first seen 2014-12-19 and last seen 2017-04-28, indicating it went dark circa April 2017. RPKI posture cannot be assessed because there are no active originations and therefore no ROAs to validate. Administrative and abuse contact routes through DISA Columbus (disa.columbus.ns.mbx.arin-registrations@mail.mil). No notable public abuse signal was found as of June 2026 — Scamalytics scores the NNIC ISP entity at 0/100 fraud risk, and no Spamhaus DROP listing, BGP hijack, or NANOG complaint involving AS287 was identified — consistent with a clean, dormant ASN held by a U.S. military operator.

Operator
Navy Network Information Center (NNIC) — U.S. Navy / DoD; ASN handle DNIC-AS-00287; registrant handle NNICN-1 [Confirmed] — ARIN RDAP autnum 287, ipinfo.io/AS287
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), CAIDA (country ISO US)
Allocated
1989-05-17 (ARIN registry date — RDAP autnum top-level events[] eventAction=registration; NOT an IEEE date, IEEE publishes no ASN registration dates); last changed 2011-07-05 [Confirmed] — ARIN RDAP autnum top-level events
Org status
U.S. federal government / military — component of the United States Navy, administered through DISA Columbus (Defense Information Systems Agency); not a commercial entity [Confirmed] — ARIN RDAP, networksdb.io (NNIC)
Contacts
abuse / admin via DISA Columbus, disa.columbus.ns.mbx.arin-registrations@mail.mil, +1-844-347-2457 ext.2 (handle REGIS10-ARIN), 300 North James Road, Whitehall, OH 43213; registrant address 2465 Guadalcanal Road, Building 1265, Virginia Beach, VA 23459
[Confirmed] — ARIN RDAP, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-25 — Scamalytics rates the NNIC ISP entity 0/100 fraud risk; no Spamhaus DROP/SBL listing, no documented BGP hijack or route leak, no NANOG complaints, no threat-feed hits for AS287 specifically [Likely — drawn from indexed search results, not live database API queries] — scamalytics.com (navy-network-information-center), spamhaus.org/blocklists, seclists.org/nanog

Network & routing

Network type
U.S. Department of Defense / Navy military government network; NNIC is the Navy's internal network registry and IP-management authority, not a commercial ISP; AS287 is legacy/inactive [Confirmed] — bgp.tools/as/287, ipinfo.io/AS287
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 (2026-06)
Routing/peering
NOT announced — 0 RIS peers seeing it (0/325 v4, 0/323 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible. Last RIS-observed prefix 130.22.176.0/22 (first seen 2014-12-19, last seen 2017-04-28). No PeeringDB record for AS287; no published peering policy
[Confirmed] — RIPEstat routing-status, bgp.tools/as/287, peeringdb.com (no AS287 record)
RPKI
not assessable — AS287 announces no prefixes, so there are no ROAs to validate (RIPEstat rpki-validation skipped, no prefix to supply) [Confirmed] — RIPEstat rpki-validation
Notable usage
AS287 is one of ~84 ASNs assigned to NNIC across the ARIN registry. NNIC collectively manages ~52 IPv4 network blocks (~143,872 IPs) covering Navy operational units and base infrastructure. AS287 itself is currently inactive — no prefixes announced, not present in the global BGP routing table; allocated in 1989, among the earliest ASN assignments [Likely for the broader block-count totals per third-party DB; Confirmed for AS287 inactivity] — bgp.tools/as/287, networksdb.io (NNIC), ARIN RDAP
Related ASNs
NNIC holds additional ASNs (e.g. AS22, AS257, AS788, AS2749, others) [Likely per third-party DB] — ipinfo.io/AS287, networksdb.io (NNIC)
Analyst note
Encountered as a dormant legacy ASN registered to a U.S. Navy / DoD entity; WHOIS resolves to NNIC, but the AS has announced no prefixes since circa April 2017. Clean, inactive ASN. RDAP entities[] carried two decoy registration dates (org NNICN-1 2006-09-21, contact REGIS10-ARIN 2009-06-24) — both ignored in favor of the autnum top-level 1989-05-17.
[ 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.