AS506
Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.
Summary
- // analyst note
- AS506 has no standalone ARIN RDAP record; it is one number inside the bulk block AS379-AS508 (AFCONC-BLOCK1-AS, registrant Air Force Systems Networking / DoD). All registry dates are read from the autnum object's TOP-LEVEL events[] (not nested entity events, which are later and belong to REGIS10-ARIN/7ESG contact records). Currently unannounced with zero routing footprint and no PeeringDB presence.
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-10; not in Spamhaus ASN-DROP, no bgp.he.net abuse/bogon annotation, no NANOG archive hits.
About this ASN.
AS506 is a U.S. military autonomous system number registered to Air Force Systems Networking (ARIN organization handle 7ESG), a U.S. Air Force / Department of Defense entity administratively fronted by DISA-Columbus (Defense Information Systems Agency) at Maxwell AFB, AL. It does not carry its own standalone ARIN RDAP record; instead it falls inside a single bulk block registration, "AFCONC-BLOCK1-AS," spanning AS379 through AS508, and its registry-level facts — including the allocation date — are inherited from that covering block record rather than an individually-issued entry. Every routing data source consulted agrees the number is currently dormant: zero announced IPv4 or IPv6 prefixes, zero of 327 IPv4 and zero of 321 IPv6 RIPE RIS peers observing it, a CAIDA customer cone limited to the ASN itself with no prefixes or addresses, and no PeeringDB network object (a direct API query returned HTTP 404). No public abuse, hijack, or bogon-announcement history was found for AS506 specifically, unlike at least one sibling ASN in the same registrant family that carries an older bogon-announcement flag. The overall picture is a long-unrouted government-held number block with no public operator storefront, consistent with closed DoD-internal numbering rather than a commercial or transit network.
- Operator
- Air Force Systems Networking (U.S. Air Force / DoD), ARIN org handle 7ESG; part of the block registration AFCONC-BLOCK1-AS (AS379–AS508); administratively contacted via DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/506
- Country / RIR
- US, ARIN [Confirmed] — ARIN RDAP registrant address (501 East Moore Dr., Maxwell AFB, AL 36114); RIPEstat abuse-contact-finder authoritative_rir: arin
- Allocated
- 1989-08-04 — ARIN RDAP autnum TOP-LEVEL registration event for the covering block AS379–AS508 (which contains AS506); last changed 2008-06-06, also top-level [Confirmed] — https://rdap.arin.net/registry/autnum/506 (note: AS506 has no individual RDAP record; this date is inherited from the block. Nested entity events — REGIS10-ARIN registration 2009-06-24, 7ESG org registration 2008-06-05 — are entity-level decoys and were correctly excluded per two independent research angles)
- Org status
- active, per ARIN RDAP status field on the covering autnum block record [Confirmed] — https://rdap.arin.net/registry/autnum/506
- Website
- Unknown — no operator-specific public page identifying AS506 individually was found (DISA's general site does not name this ASN) [Unknown]
- Contacts
- disa.columbus.ns.mbx.arin-registrations@mail.mil (abuse/administrative/technical, DISA-Columbus, 300 North James Road, Whitehall, OH 43213) [Confirmed] — https://rdap.arin.net/registry/autnum/506, https://stat.ripe.net/AS506
Security/abuse context (NEUTRAL, DATED)
no notable public abuse or hijack signal found for AS506 as of 2026-07-10 — absent from Spamhaus ASN-DROP, no abuse/bogon annotation on bgp.he.net, no matching NANOG mailing-list discussion
Network & routing
- Network type
- closed U.S. military/government network; one number inside a bulk-allocated ARIN block, not an individually provisioned commercial ASN; no PeeringDB network object exists (queried 2026-07-10, HTTP 404) [Confirmed] — https://rdap.arin.net/registry/autnum/506, https://www.peeringdb.com/api/net?asn=506
- Size
- dormant — 0 announced IPv4 prefixes, 0 IPv4 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS506, https://asrank.caida.org/asns/506
- Routing/peering
- NOT announced — 0/327 IPv4 and 0/321 IPv6 RIS peers see it; CAIDA AS degree total 0 (customer/peer/provider all 0); no upstreams or peers visible [Confirmed] — https://stat.ripe.net/AS506, https://asrank.caida.org/asns/506. Peering policy: Unknown / not publicly published — no PeeringDB entry [Unknown]
- RPKI
- not evaluable — AS506 has no announced prefixes to validate against; RIPEstat rpki-validation endpoint returned "skipped: no --prefix supplied" [Unknown] — https://stat.ripe.net/AS506
- Notable usage
- part of the U.S. Air Force's internal systems-networking ASN block (AFCONC-BLOCK1-AS, AS379–AS508); sibling ASNs in the same "Air Force Systems Networking" registrant family (AS65, AS399, AS400, AS730) are similarly DoD/Air Force-held and largely unannounced[Likely] — https://bgp.tools/as/65, https://bgp.tools/as/399, https://bgp.tools/as/400, https://bgp.he.net/AS730
- Analyst note
- AS506 has no standalone RDAP record; all registry-level facts (allocation date, last-changed date, status) are inherited from the covering block registration AS379–AS508 rather than confirmed for AS506 alone. Two independent research angles (A2, A3) converged on the same 1989-08-04 top-level registration date, ruling out decoy entity-level dates.