asn.dev

Autonomous system

AS22 DNIC-AS-00022

Unclassified ARIN

IPv4 addresses 139K 8 prefixes
IPv6 prefixes 2 counted as prefixes, not addresses
Countries 1 mostly US
Exchanges 0 recorded by PCH
Upstreams 1 0 downstream
Flagged prefixes 0 none

Summary

US Department of Defense

United States · AI-generated

government military legacy

An early US Department of Defense allocation (DNIC-AS-00022), registered through the DoD Network Information Center (DNIC).

What it's used for

  • US government / military networking.

Notable

  • A US government / DoD network, not a commercial ISP or host. The low AS number reflects an allocation from the internet's earliest years. Registered to the DoD Network Information Center, which holds many federal ASNs.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.

Transit providers

1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS668United States Department of Defense DoD409

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 8 prefixes · 139K addresses IPv6 2 prefixes

CountryNamePrefixes
USUnited States of America10

Registry

Allocation record

ARIN · via Atlas (registry + RDAP)
Registry
ARIN
Handle
AS22
Registry name
DNIC-AS-00022
Registrant
Navy Network Information Center (NNIC)
Abuse contact
disa.columbus.ns.mbx.arin-registrations@mail.mil
Registered
1984-07-30
Last changed
2011-07-05
Allocation
assigned

Declared

PeeringDB profile

self-reported
Name
NNIC AS22
Scope
Not Disclosed
Traffic ratio
Not Disclosed
Peering policy
Open

PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.

Routing security

RPKI and IRR

Full detail
RPKI
0% valid · 0 valid, 7 with no ROA
ROAs
0 authorising AS22
ASPA
no ASPA record
IRR
86% registered · 6 of 7 announcements 1 other origin
Route objects
6 naming AS22

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 446 networks and 1,852 prefixes, as published 2026-10-27. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check