AS363

AS363 is a legacy autonomous system number registered under ARIN to the United States Department of Defense (DoD), administered through the DoD Network Information Center (DNIC) and DISA-Columbus (Defense Information Systems Agency, Whitehall/Columbus, Ohio). It is not an individually-registered ASN with its own commercial operator: ARIN's public RDAP resolves AS363 to a single block-level record — handle AS306, name DNIC-ASBLK-00306-00371, startAutnum 306, endAutnum 371 — that covers the entire 66-ASN block (AS306–AS371) allocated to DoD as one unit. The key triage point is that AS363 is effectively dormant. Every routing source consulted (RIPEstat, CAIDA AS Rank) agrees the ASN announces zero IPv4 and zero IPv6 prefixes, is seen by 0 of 325 IPv4 RIS peers and 0 of 323 IPv6 RIS peers, and has zero observed neighbours, upstreams, peers, and customers. RIPEstat's as-overview reports announced: false; its customer cone is a singleton (the ASN itself, 0 prefixes, 0 addresses), and its CAIDA AS rank of 79,459 sits near the bottom of the global ranking, reflecting complete routing inactivity. RPKI posture cannot be assessed because there are no active originations and therefore no ROAs to validate. No notable public abuse, hijack, spam, or route-leak signal was found specifically for AS363 as of July 2026 — consistent with an unrouted government legacy ASN. This is a distinct, much smaller matter from the well-documented 2021 DoD anti-squatting BGP effort (via the separate AS8003), which must not be conflated with AS363.

Operator / Registrant

United States Department of Defense (DoD) — DoD Network Information Center (DNIC), administered by DISA-Columbus; ARIN org handle USDDD [Confirmed] — ARIN RDAP autnum/363 (registrant vcard "United States Department of Defense (DoD)")

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin); RDAP registrant address Columbus/Whitehall, OH, US

Allocated

1989-06-30 (ARIN registry date for the DNIC-ASBLK-00306-00371 block that contains AS363; block-level, ARIN exposes no AS363-specific sub-record); last changed 2025-09-12 [Confirmed] — ARIN RDAP autnum top-level events (eventAction "registration"/"last changed")

Org status

active (per ARIN RDAP status "active") as a registry record; the ASN itself is not actively routed [Confirmed] — ARIN RDAP autnum/363; RIPEstat routing-status

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found for AS363 as of 2026-07-01 — not in Spamhaus/abuse.ch resource pages, AbuseIPDB, or BGP-hijack incident writeups (MANRS 2021–2025 summaries). Since AS363 is unannounced it cannot originate BGP announcements under its own ASN. Do NOT conflate with the separate 2021 DoD anti-squatting effort via AS8003 (Global Positioning Assurance Gateway)

Abuse contact

disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil

Network & routing

Network type

government/military legacy ASN number block; not a commercial ISP, content, or enterprise network. Currently unrouted/not announced on the public Internet [Confirmed] — RIPEstat as-overview (announced: false)

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / announced-prefixes; CAIDA AS Rank

Routing/peering

NOT announced — 0 of 325 IPv4 RIS peers and 0 of 323 IPv6 RIS peers see it; 0 observed neighbours; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible [Confirmed] — RIPEstat routing-status; CAIDA AS Rank

Peering policy

Unknown / not publicly published. No PeeringDB record or public peering-policy page specific to AS363 was located; DISA publishes broader DISN connection-process documents, not a public per-ASN peering policy

[Unknown] — disa.mil DISN Connection Process Guide (general DoD network policy, not AS363-specific)

RPKI

not assessable — AS363 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation was skipped (requires a specific prefix) [Unknown] — RIPEstat (rpki-validation skipped: no prefix)

Notable usage

Unknown. No public documentation ties AS363 to a named DoD component, base, or service branch; the block AS306–AS371 is registered to DNIC generally and individual ASN-to-component mapping is not disclosed in public RIR records — do not infer a specific DoD sub-agency

[Unknown] — ARIN RDAP autnum/363

Geo footprint

US — registrant DISA-Columbus, Whitehall/Columbus, OH; CAIDA reports no lat/long for the ASN (0/0, unset) and ixp=null, consistent with a non-routed ASN with no observed infrastructure [Confirmed] — ARIN RDAP autnum/363; CAIDA AS Rank

Registry-scope caveat

the RDAP object for autnum 363 is a BLOCK record (handle AS306, startAutnum 306, endAutnum 371) covering 66 ASNs; the top-level registration date is the block's, and is the only ASN-level registry date ARIN exposes for AS363. Nested entity dates (MIL-HSTMST-ARIN 1993-05-26, REGIS10-ARIN 2009-06-24, USDDD org 2007-01-12) are decoys and were NOT used

[Confirmed] — ARIN RDAP autnum/363

Analyst note

Encountered as a dormant legacy ASN within a large DoD block. WHOIS/RDAP resolves to a block-level DoD/DNIC record, not an AS363-specific operator; no announcements, peers, or cone in any source. Clean, inactive government ASN.