AS412
Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.
Summary
- // analyst note
- Dormant/legacy DoD ASN, returned by ARIN as a block record (handle AS379, range 379-508). Top-level registration event 1989-08-04 recorded as allocated_date (first-party RIR fact); nested entity dates (7ESG 2008-06-05, REGIS10-ARIN 2009-06-24) are decoy org/contact dates. RIPEstat/CAIDA/bgp.he.net agree on zero current announcements, zero cone.
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus DROP/ASN-DROP, AbuseIPDB, or NANOG archives.
About this ASN.
AS412 is a legacy 16-bit autonomous system number registered under ARIN to Air Force Systems Networking, a U.S. Department of the Air Force / Department of Defense entity. It is not an individually registered ASN: ARIN returns it as part of the contiguous block AS379–AS508 (handle AS379, block name AFCONC-BLOCK1-AS), whose registrant vCard reads "Air Force Systems Networking" at 501 East Moore Drive, Building 884, Room 1100, Gunther Annex, Maxwell AFB, AL. The administrative, technical, and abuse point of contact is DISA-Columbus (300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil). The key triage point for AS412 is that it is effectively dormant today: every routing source consulted (RIPEstat, CAIDA AS Rank, bgp.he.net) agrees it announces zero IPv4 and zero IPv6 prefixes and has no active peers, upstreams, or customers. Its CAIDA AS rank of 79,459 sits near the bottom of the global ranking, and its customer cone is a singleton (the ASN itself, 0 prefixes, 0 addresses). Historically it originated a single prefix, 162.24.0.0/16, first seen in the global routing table on 2000-08-18 and last seen on 2016-10-04; it has not been visible in RIPE RIS since. No RIS peer currently sees it (0/323 v4, 0/321 v6). No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus DROP/ASN-DROP, AbuseIPDB, or NANOG archives — consistent with a clean, unrouted legacy DoD block number rather than an actively operated network.
- Operator
- Air Force Systems Networking (U.S. Department of the Air Force / DoD; ARIN registrant handle 7ESG, Maxwell AFB, AL) [Confirmed] — ARIN RDAP autnum/412 registrant vCard
- Country / RIR
- US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), ARIN RDAP
- Allocated
- 1989-08-04 (ARIN RDAP autnum TOP-LEVEL registration event, NOT an IEEE date — IEEE publishes no ASN registration dates); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events[]
- Website
- Unknown — no dedicated public site located; a wpafb.af.mil article returned HTTP 403 to automated fetch [Unknown] — wpafb.af.mil
- Org status
- active per ARIN registry status; operationally dormant/not announced [Confirmed] — ARIN RDAP status "active", RIPEstat as-overview announced:false
- Contacts
- abuse/admin/tech disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus, Whitehall, OH); registrant HQ Maxwell AFB, AL [Confirmed] — ARIN RDAP, RIPEstat abuse-contact-finder
Security/abuse context (NEUTRAL, DATED)
no notable public abuse signal found as of 2026-07-02 — not in Spamhaus DROP/ASN-DROP, AbuseIPDB, or NANOG archives; consistent with an unrouted legacy DoD block number
Network & routing
- Network type
- U.S. military/government enterprise (DoD/Air Force) number holding; secondary sources describe Air Force data-communications support but no first-party service description was located [Likely]
- Size
- dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes currently; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / CAIDA AS Rank (2026-07)
- Routing/peering
- NOT announced — 0 RIS peers seeing it (0/323 v4, 0/321 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); cliqueMember false, seen false [Confirmed] — RIPEstat routing-status / CAIDA ASRank. bgp.he.net lists one historically observed peer, AS381 (also Air Force Systems Networking)[Likely] — bgp.he.net/AS412
- RPKI
- not assessable — AS412 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation was skipped (no prefix supplied) [Confirmed] — RIPEstat, bgp.he.net/AS412
- Peering policy
- Unknown — no policy document found; PeeringDB net lookup for AS412 returned HTTP 404 [Unknown] — peeringdb.com/net?asn=412
- Related ASNs
- sibling ASNs in the AS379–AS508 (AFCONC-BLOCK1-AS) block share the "Air Force Systems Networking" name (e.g. AS379, AS381, AS399, AS400) [Confirmed for block membership; Likely for individual siblings] — ARIN RDAP block record
- Assignment class
- allocated as part of ARIN block AS379–AS508 (AFCONC-BLOCK1-AS); not individually registered [Confirmed] — ARIN RDAP startAutnum 379 / endAutnum 508
- History
- originated 162.24.0.0/16 (a /16 = 65,536 IPv4 addresses); first_seen 2000-08-18, last_seen 2016-10-04 — not seen in the global table since [Confirmed] — RIPEstat routing-status, bgp.he.net/AS412
- Analyst note
- Encountered as a dormant legacy DoD ASN returned by ARIN as a block record (handle AS379, range 379–508). The top-level registration date 1989-08-04 is the block/autnum registration event and is recorded as a first-party RIR fact; nested entity dates (7ESG registrant 2008-06-05, REGIS10-ARIN POC 2009-06-24) are org/contact decoy dates and were NOT used for allocated_date. Clean, inactive ASN.