Autonomous system
AS252 DNIC-AS-00252
Unclassified APNIC
Summary
US Department of Defense
government military legacy
An early US Department of Defense allocation (DNIC-AS-00252), registered through the DoD Network Information Center (DNIC), which holds many federal ASNs.
What it's used for
- US government / military networking. The generic DNIC registration does not identify a specific base or unit.
Notable
- A US government / DoD network, not a commercial ISP or host.
- The low AS number reflects a very early allocation, handed out roughly sequentially in the internet's first years.
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
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.
| AS | Network | Paths seen |
|---|---|---|
| AS668 | United States Department of Defense (DoD) | 375 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 5 prefixes · 69.12K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 6 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS252- Registry name
- DNIC-AS-00252
- Registrant
- Headquarters, USAISC
- Abuse contact
- disa.columbus.ns.mbx.arin-registrations@mail.mil
- Registered
- 1988-11-02
- Last changed
- 2011-08-24
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Headquarters, USAISC
- 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
- RPKI
- 0% valid · 0 valid, 6 with no ROA
- ROAs
- 0 authorising AS252
- ASPA
- no ASPA record
- IRR
- 67% registered · 4 of 6 announcements 1 other origin
- Route objects
- 5 naming AS252
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: 440 networks and 1,773 prefixes, as published 2026-10-13. 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