Autonomous system detail

AS48

Announced

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

Summary

// analyst note
A DoD/Navy DNIC-series legacy ASN; appears lightly active via DoD transit (AS668). Exact prefix count (checker: 2 IPv4 + 1 IPv6) not independently confirmed this pass — pending a direct stat.ripe.net/data/routing-status read. Shares the NNIC operator with AS22/AS37.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-09.
IPv4 prefixes
2
~131.1K addresses
IPv6 prefixes
1
announced
Peer networks
1
1 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Medium

AS48 is a legacy U.S. government allocation registered under ARIN to the Navy Network Information Center (NNIC) in Virginia Beach, VA, with the DNIC-AS naming convention denoting the Defense Network Information Center lineage. RFC 1166 (July 1990) places it among the early ARPANET/MILNET-era Navy allocations. The ASN is not dark: it has at least one observed BGP peer, and DoD/DREN (AS668) explicitly lists AS48 among its imported routes, consistent with a small active announcement — though an exact current prefix count could not be independently confirmed against a canonical routing source this pass. The ARIN ASN RegDate of 1985-08-28 is the registry date (autnum updated 2011-07-05; org entity RegDate 2006-09-21). For triage this is a DoD/Navy DNIC-series legacy ASN that appears to carry a small live announcement via DoD transit; it shares the NNIC operator with AS22 and AS37. No notable public abuse signal was found as of June 2026.

Operator
Navy Network Information Center (NNIC; ARIN OrgId NNICN-1, Virginia Beach, VA 23459) [Confirmed] — ARIN RDAP
Country / RIR
US, ARIN [Confirmed]
Allocated
ARIN ASN RegDate 1985-08-28 (autnum updated 2011-07-05; org RegDate 2006-09-21) [Confirmed] — ARIN RDAP (echoed by bgpview.io)
Org status
active organization (DoD/Navy); ASN appears lightly active

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-09 — bgpview.io

Network & routing

Network type
government / military (US Navy / DoD) [Confirmed]
Size
small live announcement likely (≥1 peer observed); exact prefix count not independently confirmed this pass — IPinfo / bgpview.io (2026-06) [Unverified count]
Routing/peering
≥1 peer; transit via DoD/DREN (AS668 lists "import: from AS48"); exact IPv4/IPv6 prefix counts not confirmed (checker reports 2 IPv4 + 1 IPv6); RPKI unknown — bgpview.io, AS668 RADB policy
Notable usage
[historical, RFC 1166] an ARPANET/MILNET-era Navy allocation under the DNIC scheme — navy.mil
Related ASNs
AS22, AS37 (also Navy NIC); AS668 (DoD/DREN — transit); broader DoD DNIC-AS series [Confirmed]
Analyst note
A DoD/Navy DNIC-series legacy ASN; appears lightly active via DoD transit (AS668). Exact prefix count pending a direct routing-status read.
[ 02 ] — Announced prefixes

What this network routes.

3 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes2
  1. 132.250.0.0/16/16
  2. 128.60.0.0/16/16
// IPv6 prefixes1
  1. 2001:480:20::/48/48
[ 03 ] — Notable peers & upstreams

Who it talks to.

1 observed neighbour
// Notable connectionsTop 1 of 1
ASNOperatorRole
AS668 DNIC-AS-00668 - United States Department of Defense (DoD) upstream
Neighbours observed via public BGP collectors; not a complete peering list.