Autonomous system detail

AS432

Not announced

Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.

Summary

// analyst note
Dormant/legacy ASN inside U.S. Air Force flat block AFCONC-BLOCK1-AS (AS379–AS508). ARIN's flat-block representation makes the RDAP handle read AS379; allocated_date 1989-08-04 is the block-level top-level registration event (per-ASN sub-events not exposed). Nested REGIS10-ARIN POC date (2009-06-24) excluded as a contact-record decoy. RIPEstat and CAIDA agree on zero announcements, zero RIS-peer visibility, zero AS degree, cone of 1.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus DROP/ASN-DROP, NANOG archives, or general threat-intel searches.
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

AS432 is a legacy autonomous system number registered under ARIN as part of a flat bulk block record named AFCONC-BLOCK1-AS, which spans AS379 through AS508 and is held by Air Force Systems Networking — the registrant organization on file being "7ESG" (the 754th Electronic Systems Group), a U.S. Air Force unit, with DISA-Columbus (Defense Information Systems Agency) as the administrative, technical, and abuse point of contact. Because ARIN represents this range as a single flat block, the RDAP record for autnum 432 resolves to the block handle AS379 and does not expose a per-ASN sub-registration; the authoritative first-party registry date is therefore the block's top-level registration event of 1989-08-04. The key triage point for AS432 is that it is operationally dormant: every routing source consulted (RIPEstat, CAIDA AS Rank) agrees it announces zero IPv4 and zero IPv6 prefixes, is not visible on any RIS route collector (0 of 324 v4 peers, 0 of 320 v6 peers), and has an AS degree of zero across customer, peer, and provider. 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). There is no PeeringDB record (peeringdb.com/asn/432 returns 404) and no published peering policy — consistent with a non-commercial DoD allocation. RPKI posture is not assessable because there are no active originations and therefore no ROAs. No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus DROP/ASN-DROP resources, NANOG archives, or general threat-intel searches — consistent with a clean, unrouted legacy government block.

Operator
Air Force Systems Networking (U.S. Air Force; registrant org "7ESG" / 754th Electronic Systems Group, Maxwell AFB-Gunter Annex, AL; admin/tech/abuse POC DISA-Columbus) [Confirmed] — ARIN RDAP autnum/432, bgp.he.net/AS432
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum/432; RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1989-08-04 (ARIN registry date from the autnum top-level registration event; this is the AFCONC-BLOCK1-AS block record AS379–AS508 that contains AS432 — ARIN does not expose a per-ASN sub-event within a flat bulk block; NOT an IEEE date); last changed 2008-06-06
[Confirmed] — ARIN RDAP autnum top-level events
Org status
active per ARIN RDAP record status; the 754th Electronic Systems Group / DISA registrant is an active DoD entity; however AS432 itself is operationally dormant (0 announced prefixes, 0 BGP peers) so it is not currently visible on the public Internet
[Confirmed] — ARIN RDAP autnum/432, bgp.he.net/AS432
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil (+1-844-347-2457 ext.2; DISA-Columbus, 300 North James Road, Whitehall, OH 43213); registrant address 501 East Moore Dr., Bldg 884 Rm 1100 Gunter Annex, Maxwell AFB, AL 36114 [Confirmed] — ARIN RDAP autnum/432, 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 resources, NANOG archives, or general web/threat-intel searches; an unrouted ASN would not originate traffic, a plausible explanation for the absence of signal

[Likely] — spamhaus.org/blocklists/do-not-route-or-peer, archive.nanog.org/list/archives.html

Network & routing

Network type
U.S. military / government network (Department of the Air Force, DoD); not a commercial ISP, hosting, or enterprise network; AS432 is legacy/inactive within the block [Confirmed] — ARIN RDAP autnum/432, bgp.he.net/AS432
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 / CAIDA AS Rank (2026-07)
Routing/peering
NOT announced — RIPEstat as-overview announced=false; announced-prefixes query (2000-08-01 to 2026-07-02) returned zero; 0 RIS peers seeing it (0/324 v4, 0/320 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers observed [Confirmed]. No PeeringDB record and no published peering policy (peeringdb.com/asn/432 → 404) [Confirmed]
RPKI
not assessable — AS432 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation requires a prefix parameter and none exists [Confirmed]
Notable usage
no individual public-facing service, website, or peering activity tied specifically to AS432; it appears to be an internal/reserved allocation within the AFCONC-BLOCK1-AS block supporting Air Force / DoD combat-support IT and network systems
[Likely] — ARIN RDAP autnum/432, hanscom.af.mil (754 ELSG coverage), bgp.he.net/AS432
Related ASNs
sits within the flat block AFCONC-BLOCK1-AS spanning AS379–AS508 (RDAP startAutnum 379 / endAutnum 508) [Confirmed] — ARIN RDAP autnum/432
Analyst note
Encountered as a dormant legacy ASN inside a U.S. Air Force bulk block; ARIN's flat-block representation means the RDAP handle reads AS379 and the registration date is a block-level (AS379–508) event rather than an AS432-specific one. The nested REGIS10-ARIN POC registration date (2009-06-24) is a contact-record decoy and was excluded. Clean, unrouted ASN.
[ 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.