Autonomous system detail

AS642

Not announced

Operated by DNIC-ASBLK-00616-00665 - United States Department of Defense (DoD).

Summary

// analyst note
AS642 is a member of DoD's shared DNIC-ASBLK-00616-00665 block (AS616-AS665), not an individually-delegated ASN, so ARIN RDAP, PeeringDB, and routing sources all resolve to the block level. All routing sources (RIPEstat, CAIDA) agree on zero announcements, zero peers, zero cone. An unverifiable 'PENS-NET-AS' third-party claim was checked and excluded as uncorroborated.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17 via Spamhaus and NANOG archive searches; direct AbuseIPDB page fetch blocked (HTTP 403) and left Unknown rather than assumed clean.
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

AS642 is a legacy autonomous system number belonging to a fifty-member ARIN block, DNIC-ASBLK-00616-00665 (AS616 through AS665), registered to the United States Department of Defense. Unlike most ASNs, DoD's DNIC allocations under this range are not individually sub-delegated with their own RDAP or PeeringDB entities — querying AS642 in ARIN's RDAP system returns the shared block record (handle AS616), whose top-level registration event dates to 1990-04-19, with the most recent metadata update on 2025-09-12. Administrative and technical contact runs through DISA (Defense Information Systems Agency), Columbus, Ohio, at the DoD Network Information Center. Operationally, AS642 is currently dormant: RIPEstat reports zero announced IPv4 or IPv6 prefixes and zero visible RIS peers, and CAIDA AS Rank places it at 79,459 with a customer cone containing only itself, zero degree in every direction, and no clique membership. No PeeringDB profile exists for AS642 (a direct lookup returns HTTP 404), and no ASN-specific public abuse, botnet, or spam signal was found across Spamhaus, NANOG archives, or general OSINT searches, though a direct AbuseIPDB page fetch was blocked (HTTP 403) and so remains formally unverified rather than assumed clean. One unconfirmed third-party claim tying AS642 to a "PENS-NET-AS / Navy NNIC" identity could not be corroborated against any primary source and is excluded here.

Operator
United States Department of Defense (DoD), via the DNIC-ASBLK-00616-00665 block (block registrant handle USDDD; DISA-Columbus admin/technical contact) [Confirmed] — https://rdap.arin.net/registry/autnum/642
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/642
Allocated
1990-04-19 (ARIN RDAP autnum top-level registration event for the DNIC-ASBLK-00616-00665 block, AS616–AS665, of which AS642 is a member — not an IEEE date, and not the nested entity/org "last changed" dates, which are decoys); last changed 2025-09-12
[Confirmed] — https://rdap.arin.net/registry/autnum/642
Org status
registry status "active" per ARIN RDAP (the block record itself), while BGP/operational status is dormant — these are reported as two distinct axes, not collapsed [Confirmed] — https://rdap.arin.net/registry/autnum/642, https://bgp.he.net/AS642

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17 across Spamhaus resource pages and NANOG archive searches; a direct AbuseIPDB page fetch (abuseipdb.com/check/AS642) returned HTTP 403 and is therefore Unknown rather than confirmed-clean

[Likely] — https://www.spamhaus.org/blocklists/spamhaus-blocklist/

Network & routing

Network type
Government/Military — DoD DNIC address/AS block administered by DISA [Confirmed] — https://ipinfo.io/AS642, https://rdap.arin.net/registry/autnum/642
Size / routing status
dormant — 0 announced IPv4 prefixes, 0 announced IPv6 prefixes, 0 RIS peers seeing it (of 326 v4 / 321 v6 peers), 0 observed neighbours [Confirmed] — https://stat.ripe.net/AS642
CAIDA AS Rank
79,459; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; cliqueMember false; seen false; asnDegree total/customer/peer/provider all 0 [Confirmed] — https://asrank.caida.org/asns/642
Peering policy / PeeringDB
no PeeringDB profile exists for AS642 (direct lookup returns HTTP 404); no AS642-specific public peering policy found. DoD's general commercial-peering posture is governed DISN-wide via a DoD-CIO-approved gateway per DISA's Connection Process Guide, but that document does not name AS642 specifically
[Unknown] — https://www.peeringdb.com/asn/642, https://dl.dod.cyber.mil/wp-content/uploads/connect/CPG/ConnProcGuide.html
RPKI
not assessable — AS642 announces no prefixes, so RIPEstat's rpki-validation check requires a prefix parameter and could not run; there are no ROAs to validate [Confirmed] — https://stat.ripe.net/AS642
Notable usage / operator website
no ASN-specific operator website found; no evidence of current production routing under AS642 (0 originated prefixes/peers as of 2026-07-17) [Unknown for website; Confirmed for dormancy] — https://bgp.he.net/AS642
Geo footprint
registrant/technical contact addresses only — DISA-Columbus, 300 North James Road, Whitehall, OH 43213, US, and registrant org address 3990 E. Broad Street, Columbus, OH 43218, US (CAIDA lat/long are unset placeholders, not real coordinates) [Confirmed] — https://rdap.arin.net/registry/autnum/642
Related ASNs
member of the same DNIC-ASBLK-00616-00665 block as AS616 through AS665 [Confirmed] — https://rdap.arin.net/registry/autnum/642
Analyst note
an unverifiable third-party claim ("PENS-NET-AS", attributed to Navy NNIC) surfaced in one search snippet but could not be corroborated via ARIN RDAP, bgp.he.net, or ipinfo.io, and a targeted follow-up search failed to reproduce it; excluded from Fields/JSON as unconfirmed.
[ 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.