AS357

AS357 is a legacy, low-numbered autonomous system registered under ARIN to the United States Department of Defense (DoD). It does not exist in the registry as a standalone record: ARIN RDAP returns it inside the block registration DNIC-ASBLK-00306-00371 (handle AS306, startAutnum 306, endAutnum 371), a contiguous 66-ASN range allocated to the DoD Network Information Center (DNIC) and administered through DISA-Columbus. The block's top-level RDAP registration event dates to 1989-06-30, which is recorded here as AS357's allocated date — a first-party RIR fact independently corroborated by ipinfo.io's allocation field for AS357 itself; the block record was last changed 2025-09-12. Unlike the dormant legacy DoD blocks that announce nothing, AS357 is live: RIPEstat shows it currently originating roughly 16 IPv4 prefixes drawn from the DoD's 55.0.0.0/8 space (e.g. 55.49.0.0/16, 55.76.0.0/16, 55.77.0.0/17, 55.90.0.0/16, 55.98.0.0/16), totalling on the order of 393,216 addresses, and announcing zero IPv6. Its IPv4 originations are seen by 323 of 325 RIPE RIS peers, with a routing history extending back to 2011-07-22. CAIDA ranks it #12654 and classifies it as a stub/leaf AS — customer cone of one, a single upstream provider (asnDegree provider=1, peer=0, customer=0), with the upstream not named in the CAIDA payload. This is a closed government/military network, not a commercial ISP or transit provider: there is no dedicated operator website (the registrant is administered publicly via DISA), no PeeringDB network record, and no public peering policy — DoD interconnection is governed internally under DoD Instruction 8010.01. As of 2026-07-01 no notable public abuse signal was found — AS357 is not on the Spamhaus ASN-DROP list (checked directly against the live feed), and no BGP hijack, route-leak, NANOG thread, or AbuseIPDB ASN-level report specifically naming AS357 surfaced; the NANOG mailing-list archive returned HTTP 402 and could not be searched, so that source is an unverified gap rather than a confirmed clean result.

Operator

United States Department of Defense (DoD); registrant org handle USDDD, DoD Network Information Center (DNIC), administered via DISA-Columbus [Confirmed] — ARIN RDAP autnum/357, ipinfo.io/AS357, db-ip.com/as357-dod-network-information-center

Country / RIR

US, ARIN [Confirmed] — ARIN RDAP autnum/357

Allocated

1989-06-30 (ARIN RDAP autnum TOP-LEVEL registration event for the AS306–371 block, a first-party RIR fact — NOT an IEEE date); last changed 2025-09-12 [Confirmed] — ARIN RDAP autnum/357; corroborated by ipinfo.io/AS357 (same June 30, 1989 date). Three decoy nested entity dates (POC MIL-HSTMST-ARIN 1993-05-26, POC REGIS10-ARIN 2009-06-24, org USDDD 2007-01-12) correctly excluded.

Org status

active. ARIN RDAP reports status "active" for the AS306–371 block containing AS357 [Confirmed] — ARIN RDAP autnum/357

Contacts

two ARIN block contacts at DISA-Columbus, 300 North James Road, Whitehall, OH 43213 — "Network DoD" (handle MIL-HSTMST-ARIN, abuse/technical/NOC, disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil) and "Registration" (handle REGIS10-ARIN, technical/administrative, disa.columbus.ns.mbx.arin-registrations@mail.mil); both last updated 2026-02-12

[Confirmed] — ARIN RDAP autnum/357

IANA reference

AS357 sits inside the IANA 16-bit Autonomous System (AS) Numbers Registry range 1-1876, recorded there as "Assigned by ARIN" — IANA delegates the whole range to the RIR and publishes no per-ASN entry for AS357 itself, so the ARIN block record above is the lowest-level registry object that exists for it

[Confirmed] — IANA 16-bit AS Numbers Registry as reported by RIPEstat as-overview, stat.ripe.net/AS357 (queried 2026-07-28)

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-01 — NOT on Spamhaus ASN-DROP (checked directly against the live 424-entry feed); no BGP hijack/route-leak, NANOG thread, or AbuseIPDB ASN-level report specifically naming AS357. NANOG mailman archive returned HTTP 402 and could not be searched — an unverified gap, not a confirmed clean result

Network & routing

Network type

government/military internal network — not a commercial ISP, transit provider, hosting company, or IXP participant; single-homed stub AS [Confirmed] — ipinfo.io/AS357

Size

~16 IPv4 prefixes / ~393,216 IPv4 addresses (55.0.0.0/8 space, e.g. 55.49.0.0/16, 55.76.0.0/16, 55.77.0.0/17, 55.90.0.0/16, 55.98.0.0/16); 0 IPv6 [Confirmed] — RIPEstat (stat.ripe.net/AS357)

Routing/peering

currently announced — IPv4 seen by 323/325 RIS peers, IPv6 0/323; first seen 2011-07-22, last seen 2026-07-01. CAIDA rank #12654; asnDegree provider=1, peer=0, customer=0 (stub/leaf, single upstream). Upstream ASN identity Unknown — not named in the CAIDA payload; no bgp.he.net/bgp.tools corroboration performed [Confirmed for counts/rank; Unknown for upstream identity] — stat.ripe.net/AS357, asrank.caida.org/asns/357

RPKI

not evaluated — RIPEstat rpki-validation requires a specific prefix parameter that was not supplied in this pull; no ROA validation result available [Unknown] — stat.ripe.net/AS357

Peering policy

none published — no PeeringDB network record for AS357; DoD interconnection is governed internally under DoD Instruction 8010.01 (DISN-to-commercial connections route through a DoD CIO-approved gateway), which is an internal policy document, not an AS357-specific operator peering policy

[Confirmed for absence] — peeringdb.com/asn/357, esd.whs.mil DoDI 8010.01

Notable usage

announces DoD-registered IPv4 blocks within 55.0.0.0/8; no IPv6. Domain association varies by aggregator (nic.mil vs mail.mil — both legitimate DoD-family domains); canonical primary domain for AS357 specifically is Unknown [Likely] — ip2location.com/as357, ipinfo.io/AS357

AS block context

AS357 has no standalone RDAP record; it sits inside block DNIC-ASBLK-00306-00371 (handle AS306, startAutnum 306, endAutnum 371) registered as one autnum range to the DoD [Confirmed] — ARIN RDAP autnum/357

Analyst note

Encountered as a live low-numbered DoD ASN with no standalone RDAP record; block-level registration applies. WHOIS/RDAP resolve cleanly to the DoD via DISA-Columbus. No commercial operator site, PeeringDB record, or public peering policy exists — that absence is itself a sourced finding for a non-commercial government ASN.