Autonomous system detail

AS413

Not announced

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

Summary

// analyst note
Dormant/legacy DoD ASN. RDAP /autnum/413 returns the flat block keyed to handle AS379 (AFCONC-BLOCK1-AS, AS379–AS508); all self/alternate links resolve to /autnum/413, confirming the correct response. Dates read from the autnum TOP-LEVEL events[], not nested entity decoys. RIPEstat, CAIDA, and bgp.he.net agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in AbuseIPDB, Spamhaus (SBL/DROP/XBL), abuse.ch, or NANOG archives.
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

AS413 is a legacy autonomous system number registered under ARIN to Air Force Systems Networking, a U.S. Department of the Air Force / Department of Defense network organization headquartered at Maxwell AFB, Alabama, with its ARIN registration administered by DISA-Columbus. The number is not exposed by ARIN as a standalone object: querying rdap.arin.net/registry/autnum/413 returns the covering flat block AFCONC-BLOCK1-AS (handle AS379, startAutnum 379, endAutnum 508) under ARIN's nro_rdap_profile_asn_flat_0 convention, so AS413 is one member of the reserved DoD block AS379–AS508. The registrant vCard is 7ESG / Air Force Systems Networking; the administrative, technical, and abuse point of contact is DISA-Columbus (REGIS10-ARIN, disa.columbus.ns.mbx.arin-registrations@mail.mil). The key triage point is that AS413 is effectively dormant: every routing source consulted — RIPEstat, CAIDA AS Rank, and Hurricane Electric — agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, zero customers, and no IXP presence. 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). 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 AbuseIPDB, Spamhaus, abuse.ch, or NANOG archives — consistent with a clean, unrouted legacy U.S. military ASN. Note that the bare string "AS413" collides heavily with an Alaska Airlines flight number, an automotive MAP-sensor part, and an SAE standard; those are unrelated and excluded.

Operator
Air Force Systems Networking (U.S. Department of the Air Force / DoD network organization; ARIN registrant handle 7ESG, Maxwell AFB, AL; registration administered by DISA-Columbus) [Confirmed] — ARIN RDAP autnum/413 registrant vCard
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin); CAIDA country ISO US
Allocated
1989-08-04 (ARIN registry date read from the autnum top-level registration event on the covering AFCONC-BLOCK1-AS block AS379–AS508; a first-party RIR fact, 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 — ARIN RDAP status "active" on the covering AFCONC-BLOCK1-AS block registration (RDAP exposes no separate per-AS413 record) [Confirmed] — ARIN RDAP autnum/413
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil (admin/tech/abuse POC, DISA-Columbus); registrant address 501 East Moore Dr. Bldg 884 Rm 1100 Gunther Annex, Maxwell AFB, AL 36114, United States [Confirmed] — ARIN RDAP autnum/413, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in AbuseIPDB, Spamhaus (SBL/DROP/XBL), abuse.ch, or NANOG archives; consistent with AS413's confirmed BGP inactivity (0 prefixes, 0 peers). General USAF cyber incidents in public reporting do NOT name AS413 and are excluded

[Confirmed] — abuseipdb.com, spamhaus.org, abuse.ch, archive.nanog.org

Network & routing

Network type
U.S. military / government (DoD, U.S. Air Force), non-commercial; AS413 is legacy/inactive within a reserved DoD block [Confirmed] — ARIN RDAP autnum/413
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-02)
Routing/peering
NOT announced — RIPEstat as-overview announced:false; 0 RIS peers seeing it (0/323 v4, 0/321 v6); 0 observed neighbours; CAIDA degree total 0 (customer 0, peer 0, provider 0); Hurricane Electric shows 0 prefixes / 0 peers. No peering policy published; no PeeringDB network record exists for AS413
[Confirmed] — RIPEstat, CAIDA, bgp.he.net, PeeringDB
RPKI
not assessable — AS413 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation was skipped (requires a prefix) [Confirmed] — RIPEstat rpki-validation
Notable usage
part of the AFCONC-BLOCK1-AS block (AS379–AS508) registered to Air Force Systems Networking; zero prefixes originated in IPv4 or IPv6, consistent with an unrouted/administrative ASN within a reserved DoD block [Likely] — bgp.he.net/AS413, ARIN RDAP
Related ASNs
covered by ARIN block AFCONC-BLOCK1-AS (AS379–AS508); sibling members enriched elsewhere in this pipeline (e.g. AS379, AS404, AS407) [Likely] — ARIN RDAP startAutnum/endAutnum
Analyst note
RDAP autnum for /413 returns the flat block keyed to handle AS379 (name AFCONC-BLOCK1-AS); all rel=self/alternate links resolve to /autnum/413, confirming this IS the authoritative response for AS413, not a wrong-ASN fetch. Allocated/last-changed dates were read strictly from the autnum TOP-LEVEL events[], not the nested entity events (7ESG org reg 2008-06-05; REGIS10-ARIN POC reg 2009-06-24), which are excluded as decoys. Clean, inactive DoD 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.