Autonomous system detail

AS244

Not announced

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

Summary

// analyst note
Dormant/legacy ASN. RDAP resolves to DoD/DISA-Columbus, but there is no live routing under AS244. RIPEstat, CAIDA, bgp.he.net, and bgp.tools all agree on zero announcements, zero peers, zero cone. allocated_date 1988-10-05 is the ARIN autnum top-level registration event (first-party RIR fact). A single-sourced historical-operator claim (ITT/Federal Electric) was not asserted.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-20; absent from Spamhaus ASN-DROP, no NANOG threads, no documented BGP hijack/route-leak.
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

AS244 is a legacy autonomous system number registered under ARIN to the United States Department of Defense (DoD), operated by the DoD Network Information Center (DNIC) — a function of the Defense Information Systems Agency (DISA) administered out of DISA-Columbus in Whitehall/Columbus, Ohio. The ASN dates to the earliest era of the Internet: its ARIN autnum carries a top-level registration event of 1988-10-05, placing it among the oldest allocated ASNs and reflecting the DoD's foundational role in the ARPANET and the Defense Data Network (DDN). Historically the DNIC managed network registration services — hostnames, IP addresses, routing — for the DDN segments (ARPANET, MILNET, MINET, SACDIN), as well as the .mil top-level domain, with DISA assuming that role from the Defense Communications Agency in the 1990s. The triage point for AS244 today is that it is effectively dormant: every routing source consulted (RIPEstat as-overview/announced-prefixes, CAIDA AS Rank, bgp.he.net, bgp.tools) agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, and no IXP presence. Its CAIDA AS rank of 79,459 sits near the bottom of the global ranking, reflecting complete routing inactivity, and its customer cone is a singleton (the ASN itself, 0 prefixes, 0 addresses). PeeringDB lists an open peering policy, but this is nominal given there is no active routing. RPKI posture cannot be assessed because there are no active originations and therefore no ROAs to validate. No notable public abuse signal was found as of June 2026 — AS244 is absent from Spamhaus ASN-DROP, surfaced no NANOG threads, and has no documented BGP hijack or route-leak incidents — consistent with a clean, dormant ASN held by a US federal government operator.

Operator
United States Department of Defense (DoD); DoD Network Information Center (DNIC), operated by DISA-Columbus; ARIN org handle USDDD [Confirmed] — ARIN RDAP autnum/244, ipgeolocation.io/browse/asn/AS244
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum/244; RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1988-10-05 (ARIN autnum top-level registration event — a first-party RIR fact, NOT an IEEE date); last changed 2025-09-12 [Confirmed] — ARIN RDAP autnum top-level events
Org status
active US federal government agency (Department of Defense); registrant org USDDD, address 3990 E. Broad Street, Columbus, OH 43218 [Confirmed] — ARIN RDAP autnum/244
Contacts
abuse/hostmaster disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil; NOC "Network DoD" +1-844-347-2457; NOC address DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — ARIN RDAP autnum/244; RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-20 — AS244 is absent from Spamhaus ASN-DROP (list begins at AS245), no NANOG archive threads, and no documented BGP hijack or route-leak incidents; with zero routed prefixes it presents no active attack surface

[Confirmed] — spamhaus.org/drop/asndrop.json, bgp.he.net/AS244

Network & routing

Network type
US federal government / military network; historically tied to the DDN / MILNET infrastructure and .mil registration via the DNIC; AS244 is legacy/inactive today [Confirmed] — en.wikipedia.org/wiki/MILNET, ipgeolocation.io/browse/asn/AS244
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses — RIPEstat announced-prefixes / CAIDA AS Rank / bgp.he.net (2026-06)
Routing/peering
NOT announced — RIPEstat as-overview announced:false; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source; not seen in BGP [Confirmed]. PeeringDB lists an open peering policy, but it is nominal given no active routing [Confirmed for the listed policy]
RPKI
not assessable — AS244 announces no prefixes, so there are no ROAs to validate; bgp.he.net shows 0 RPKI-valid and 0 RPKI-invalid origins [Confirmed]
Notable usage
one of the earliest allocated ASNs (registered 1988), tied to the DoD's foundational ARPANET/DDN role; the DNIC managed network registration for the Defense Data Network and the .mil TLD, with DISA-Columbus continuing .mil administration. AS244 is dormant — no prefixes announced — but the ASN and ARIN registration remain active [Confirmed for dormancy/registration; Likely for the DNIC historical scope] — ipinfo.io/AS244, en.wikipedia.org/wiki/MILNET
PeeringDB
net ID 33167 (status ok); DoD operates multiple ASNs in PeeringDB under org 17705; no IX presence listed [Confirmed] — peeringdb.com/net/33167, peeringdb.com/org/17705
Analyst note
Encountered as a dormant legacy ASN registered to the US DoD; WHOIS/RDAP resolves to DoD/DISA-Columbus, but there is no live routing under AS244. Clean, inactive ASN. A historical-operator claim (ITT / Federal Electric Corporation → Vectrus) appeared in a single A5 source only and is tagged [Likely] at best; it is NOT asserted as fact here, since the current ARIN registrant is the DoD.
[ 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.