Autonomous system detail

AS748

Not announced

Operated by DNIC-AS-00748 - United States Department of Defense (DoD).

Summary

// analyst note
Dormant DoD/DISA ASN under the DNIC address block; not seen announcing any prefix since 2022-06-21. allocated_date left null because two proposed 'registration' dates (1993-05-26, 2007-01-12) traced to nested entity-level records, not the autnum's own top-level events[], which carries only a 'last changed' entry — confirmed on two independent RDAP re-fetches. No operator-official website was located.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-27; Qrator Radar shows zero leaks/hijacks/bogons/amplifiers, but this likely reflects the ASN having no active BGP announcements rather than a verified clean record.
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: Medium

AS748 is a dormant U.S. Department of Defense autonomous system that currently announces zero IPv4 and zero IPv6 prefixes — RIPEstat's as-overview shows announced: false, and it has not been visible originating routes since 2022-06-21.

The ASN is registered under ARIN to the U.S. Department of Defense (entity handle USDDD), administered through DISA (Defense Information Systems Agency) via the Defense Network Information Center (DNIC), DISA-Columbus. Its only recorded routing history is a single IPv4 block, 140.16.106.0/23, first seen 2019-05-15 and last seen 2022-06-21 — never announced since, and no IPv6 space was ever observed.

CAIDA corroborates the dormancy independently: AS rank 79459 is registry-derived (CAIDA flags seen: false, cliqueMember: false), with zero upstream, peer, and customer degree, and a customer cone limited to the ASN itself (1 ASN, 0 prefixes, 0 addresses). No PeeringDB network record exists for AS748 (both the API and web lookup return HTTP 404, a verified absence rather than a failed query) — consistent with a closed government network that does not publish peering terms.

The ASN's own top-level ARIN RDAP registration date could not be confirmed. Two research angles independently proposed a "registration" event (1993-05-26 and 2007-01-12), but a third angle re-fetched the raw autnum object twice and found the top-level events[] array contains only a "last changed" entry (2025-09-12), with no registration eventAction present at all.

The two proposed dates most likely came from nested entity-level records (a POC registration and an org registration) rather than the ASN's own allocation event. Given that direct, twice-verified read of the source structure, allocated_date is recorded as genuinely unresolved rather than guessed.

Operator
United States Department of Defense (DoD); administered by DISA (Defense Information Systems Agency) via the Defense Network Information Center (DNIC), DISA-Columbus [Confirmed] — ARIN RDAP autnum, ARIN RDAP entity USDDD
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum record for AS748
Allocated
Unknown — the RDAP autnum object's top-level events[] array carries only a "last changed" event (2025-09-12); no top-level "registration" eventAction is present, confirmed on two independent re-fetches. Two nested entity-level dates (org registration 2007-01-12, POC registration 1993-05-26) exist but are decoys, not the ASN's own allocation date
[Confirmed absence] — ARIN RDAP autnum record for AS748
Org status
active per ARIN RDAP autnum status field; last changed 2025-09-12 [Confirmed] — ARIN RDAP autnum record for AS748
Contacts
disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (abuse contact); DISA-Columbus, 300 North James Road, Whitehall, OH 43213 (technical/admin POC); registrant address 3990 E. Broad Street, Columbus, OH 43218 [Confirmed] — RIPEstat abuse-contact-finder for AS748, ARIN RDAP entity USDDD

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-27 — Qrator Radar shows zero leaks/hijacks/bogons/amplifiers, though this largely reflects the ASN having no active announcements to measure; Spamhaus and Talos reputation lookups both returned HTTP 403 and are Unknown, not confirmed-clean

[Likely] — radar.qrator.net/as748, CAIDA AS Rank API

Network & routing

Network type
U.S. federal government / military network [Confirmed] — ARIN RDAP autnum record
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses currently announced, 0 IPv6 prefixes; historically originated only one IPv4 block, 140.16.106.0/23, first seen 2019-05-15, last seen 2022-06-21 [Confirmed] — RIPEstat as-overview / announced-prefixes / routing-status for AS748
Routing/peering
NOT currently announced — CAIDA asnDegree totals 0 (upstream 0, peer 0, customer 0), customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; no PeeringDB network record exists (404 verified on both API and web lookup) [Confirmed] — CAIDA AS Rank API for AS748, peeringdb.com/asn/748
RPKI
not assessable — no currently-announced prefix exists to validate against; the RPKI-validation query requires a prefix parameter that could not be supplied [Unknown] — stat.ripe.net/AS748
Notable usage
no confirmed operator-official statement of current usage found. Per third-party BGP looking-glass data only (not operator-confirmed), AS748 is cross-referenced with AS27064 (DoD Network Information Center) [Likely, third-party source only] — bgp.he.net/AS748
Related ASNs
AS27064 (DoD Network Information Center), per third-party bgp.he.net cross-reference only [Likely] — bgp.he.net/AS748
Last changed
2025-09-12 [Confirmed] — ARIN RDAP autnum top-level events
Analyst note
encountered as a dormant DoD/DISA ASN registered under the DNIC address block, no longer visible in the global routing table since mid-2022; the operator-official website could not be identified (a WebFetch of disa.mil returned no AS748/DNIC-specific content), so website is left Unknown rather than guessed.
[ 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.