AS512

AS512 (DNIC-AS-00512) is a legacy autonomous system number registered under ARIN to the United States Department of Defense (DoD), administered through the DoD Network Information Center (NIC) in Columbus/Whitehall, Ohio. ARIN RDAP's top-level autnum record for AS512 carries a registration event dated 1989-08-23, making it one of the DoD's earliest ASN holdings under the DNIC block; the record's last-changed timestamp is 2025-09-12, reflecting routine registry maintenance rather than any operational change. Unlike many legacy government allocations that stay quietly routed, AS512 shows zero live routing activity today: RIPEstat and CAIDA both independently confirm zero announced IPv4 and IPv6 prefixes, zero RIS peer visibility (0 of 327 v4 peers, 0 of 321 v6 peers), zero observed upstreams or peers, and a customer cone limited to the ASN itself. CAIDA's AS Rank places it at 79,459, near the bottom of the global ranking, consistent with a dormant, unannounced resource. No operator-published website, peering policy, or notable-usage statement could be located for AS512 specifically — it does not appear in PeeringDB (404 on asn/512), and the DoD's own PeeringDB organization listing (org/17705, 20 ASNs) does not include it. Abuse and technical contact routes through DISA-Columbus. No notable public abuse or security signal was found in Spamhaus ASN-DROP or accessible NANOG archives, though this absence is best read as a byproduct of the ASN's unrouted status rather than a vetted clean-history verdict.

Operator / registrant org

United States Department of Defense (DoD), ARIN org handle USDDD [Confirmed] — https://rdap.arin.net/registry/autnum/512

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/512

Allocated

1989-08-23 (ARIN RDAP autnum TOP-LEVEL registration event; last changed 2025-09-12). Nested entity/POC dates (e.g. USDDD registrant 2007-01-12, MIL-HSTMST-ARIN POC 1993-05-26, REGIS10-ARIN POC 2009-06-24) are contact/org record dates, not the ASN's own allocation date, and were not used

[Confirmed] — https://rdap.arin.net/registry/autnum/512

Website

Unknown — no AS512-specific operator page found on disa.mil or elsewhere; only a postal address and two role-based hostmaster/registration email aliases are listed on the RDAP record [Confirmed absence] — https://rdap.arin.net/registry/autnum/512

Org status

Active (ARIN RDAP autnum status field); registering organization (U.S. DoD) is an active, ongoing federal agency [Confirmed] — https://rdap.arin.net/registry/autnum/512

Contacts

disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (abuse/technical/NOC); disa.columbus.ns.mbx.arin-registrations@mail.mil (registration) [Confirmed] — https://rdap.arin.net/registry/autnum/512

IANA reference

left blank — no IANA RFC/reference applies or was verifiable for this ASN; not fabricated [Unknown]

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-10 — not listed in Spamhaus ASN-DROP; no confirmed NANOG/seclists mentions naming AS512 specifically (one general 2021 NANOG "DoD IP Space" thread could not be fetched to confirm). Absence is consistent with AS512's unrouted status rather than a vetted clean verdict

Network & routing

Network type

U.S. federal government / military network resource operated via the DoD NIC, not a commercial ISP; no source ties AS512 to a specific named DoD sub-network (e.g. NIPRNet, DREN) [Likely] — https://rdap.arin.net/registry/autnum/512, https://www.disa.mil/network-services/

Routing/peering

NOT announced — 0 IPv4/IPv6 prefixes, 0 of 327 RIS peers (v4) and 0 of 321 RIS peers (v6) seeing it, 0 observed neighbours/upstreams/peers; CAIDA degree total 0 [Confirmed] — https://stat.ripe.net/AS512, https://api.asrank.caida.org/v2/restful/asns/512

Peering policy

Unknown / not publicly published; AS512 is absent from PeeringDB (asn/512 returns 404) and absent from the DoD's own PeeringDB org listing (org/17705, 20 listed ASNs) [Confirmed absence] — https://www.peeringdb.com/org/17705

Size / customer cone

dormant — 0 IPv4/IPv6 prefixes and addresses announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; CAIDA AS rank 79,459 [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/512

RPKI

not assessable — RIPEstat's rpki-validation endpoint requires a specific announced prefix, and AS512 announces none [Unknown/not applicable] — https://stat.ripe.net/AS512

Geo footprint

registrant postal addresses in Whitehall, OH (DISA-Columbus) and Columbus, OH (DoD org), US; CAIDA's own lat/long fields are 0,0 placeholder values, not real coordinates [Confirmed] — https://rdap.arin.net/registry/autnum/512

Notable usage

Unknown — no operator-published or third-party source describes a specific traffic role or public-facing purpose for AS512 beyond general DoD ownership [Unknown]

ASN / name

AS512 / DNIC-AS-00512 [Confirmed] — https://rdap.arin.net/registry/autnum/512

Analyst note

Legacy DoD ASN, first-block allocation (1989), currently unrouted across all consulted BGP/routing sources. No corporate-structure source ties it to a specific named DoD sub-network or to other DoD ASNs, so related_asns is left empty rather than inferred from a topology proximity search.