Autonomous system detail

AS434

Not announced

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

Summary

// analyst note
Dormant/legacy DoD/USAF ASN. ARIN RDAP for autnum/434 returns the block record (handle AS379, AFCONC-BLOCK1-AS, range 379-508) that covers AS434 — standard ARIN block behavior. Identity cross-verified via CAIDA ASRank and IPinfo. allocated_date read from the autnum top-level registration event (1989-08-04); entity-level dates excluded as decoys. Admin/abuse routed through DISA-Columbus.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; Spamhaus, abuse.ch, AbuseIPDB, and NANOG archives searched with no AS434 listings or incidents.
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

AS434 is a legacy autonomous system number registered under ARIN to Air Force Systems Networking (AFSN), a U.S. Air Force / Department of Defense network entity. It is not a standalone RDAP object: ARIN resolves autnum/434 to the block record AFCONC-BLOCK1-AS (handle AS379, startAutnum 379, endAutnum 508), a contiguous DoD delegation that legitimately covers AS434 — standard ARIN behavior for military block allocations, not a data error. The registrant org is Air Force Systems Networking (ARIN handle 7ESG, Maxwell AFB, AL), with administrative, technical, and abuse contact routed through DISA-Columbus (Defense Information Systems Agency, Whitehall, OH). The key triage point is that AS434 is effectively dormant today: every routing source consulted (RIPEstat, CAIDA AS Rank, bgp.he.net, IPinfo) agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, zero customers, and no IXP memberships. RIPEstat reports announced=false with 0 of 324 RIS peers seeing v4 and 0 of 320 seeing v6; CAIDA places it at AS rank 79,459 with a singleton customer cone (itself only, 0 prefixes, 0 addresses). RPKI posture cannot be assessed 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, abuse.ch, AbuseIPDB, or NANOG archives searched — consistent with a clean, dormant government/military allocation. Note AS434 is not listed under the PeeringDB org for Air Force Systems Networking (org 20118), which enumerates AS65/AS123/AS175/AS221/AS301 but not AS434.

Operator
Air Force Systems Networking (U.S. Air Force / DoD; ARIN org handle 7ESG, 501 East Moore Dr. Bldg 884 Rm 1100 Gunther Annex, Maxwell AFB, AL 36114) [Confirmed] — ARIN RDAP, ipinfo.io/AS434
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1989-08-04 (ARIN registry date for the AFCONC-BLOCK1-AS / AS379–AS508 block covering AS434, NOT an IEEE date — IEEE publishes no ASN registration dates); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events
Org status
active registration at ARIN (block record last changed 2008-06-06; registrant/abuse contact entity REGIS10-ARIN last changed 2026-02-12, indicating the record is still maintained) while operational routing status is inactive/dormant [Confirmed] — ARIN RDAP
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil (abuse/admin/tech via DISA-Columbus); +1-844-347-2457 ext2 [Confirmed] — ARIN RDAP, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — Spamhaus, abuse.ch, AbuseIPDB, and NANOG archives searched; no AS434 listings, hijack/route-leak incidents, or blocklist entries; ASN currently announces zero prefixes so has no live routing footprint to hijack

[Likely] — spamhaus.org, abuse.ch, bgp.he.net/AS434

Network & routing

Network type
U.S. military / government network (DoD, Department of the Air Force); legacy allocation within a 1989 DoD block (AS379–AS508), not a commercial ISP/hosting/content network [Confirmed] — ARIN RDAP, asrank.caida.org/asns/434
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 / bgp.he.net (2026-07)
Routing/peering
NOT announced — RIPEstat announced=false, 0 RIS peers seeing it (0/324 v4, 0/320 v6), 0 observed neighbours; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source [Confirmed]. No public peering policy found; not listed in PeeringDB
[Confirmed] — peeringdb.com/org/20118
RPKI
not assessable — AS434 announces no prefixes, so there are no ROAs to validate (rpki-validation requires a prefix, none exist) [Confirmed]
Notable usage
none currently identified — zero announced prefixes and zero BGP peers across CAIDA and bgp.he.net; consistent with a legacy/administrative allocation within the AFSN block rather than an operationally active AS [Confirmed] — asrank.caida.org/asns/434, bgp.he.net/AS434, ipinfo.io/AS434
Related ASNs
AS379–AS508 (the AFCONC-BLOCK1-AS block containing AS434); PeeringDB lists AS65/AS123/AS175/AS221/AS301 under the same org, but not AS434 [Confirmed] — ARIN RDAP, peeringdb.com/org/20118
Analyst note
Encountered as a dormant legacy DoD/USAF ASN. ARIN RDAP for autnum/434 returns the block record (AS379, AFCONC-BLOCK1-AS, 379–508); identity cross-verified via CAIDA ASRank and IPinfo, both confirming AS434 = Air Force Systems Networking. Entity-level dates (REGIS10-ARIN 2009-06-24, org 7ESG 2008-06-05) were correctly excluded as decoys; allocated_date taken strictly from the autnum top-level registration event (1989-08-04).
[ 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.