Autonomous system detail

AS735

Not announced

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

Summary

// analyst note
Dormant, unrouted DoD-held ASN. Autnum top-level RDAP events carry only a 'last changed' date (2008-06-06); no top-level registration eventAction exists, so allocated_date is recorded Unknown rather than borrowed from nested entity dates. Community-corroboration angle (A5) could not run this cycle due to exhausted WebSearch budget.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-25; not on Spamhaus ASN-DROP or NANOG mailing-list 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: Medium

AS735 is a dormant, unrouted autonomous system number registered under ARIN to Air Force Systems Networking (U.S. Department of Defense / Air Force), administered through DISA-Columbus, and it currently announces zero prefixes anywhere on the public Internet.

The ASN sits inside the ARIN block AS727AS746, named "AFCONC-BLOCK2-AS," which is assigned to the Air Force. RIPEstat, CAIDA AS Rank, and Hurricane Electric's BGP toolkit independently agree AS735 has no IPv4 or IPv6 announcements, no observed neighbours, and no upstream or peer relationships in current global routing tables. Its CAIDA customer cone is a singleton (itself only, 0 prefixes, 0 addresses), and its AS Rank of 79,459 places it near the bottom of the global ranking — consistent with an inactive government-held block rather than an operating network.

No standalone public operator website or PeeringDB profile exists for this ASN; peeringdb.com/asn/735 returns a 404, which is expected for an internal DoD network rather than a commercial ISP. Registered contacts route through DISA-Columbus (300 North James Road, Whitehall, OH), with a validated abuse/administrative/technical POC. RPKI posture is not assessable because no prefixes are announced, so there are no ROAs to validate.

Registration-date sourcing is genuinely ambiguous in this cycle: the autnum object's top-level events[] array carries only a "last changed" entry (2008-06-06T10:03:45-04:00), with no top-level "registration" eventAction; the 2008-06-05 and 2009-06-24 dates found elsewhere in the RDAP response belong to nested entity records (registrant org 7ESG and ARIN registrar entity), not the autnum object itself. Per the no-fabrication rule, allocated_date is recorded as Unknown rather than borrowed from an entity-level date.

Operator
Air Force Systems Networking (ARIN org handle 7ESG; U.S. Department of Defense / Air Force), administered via DISA-Columbus [Confirmed] — ARIN RDAP autnum/entity 7ESG
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum
Allocated
Unknown — autnum top-level events[] contains only a "last changed" entry (2008-06-06T10:03:45-04:00), no top-level "registration" eventAction; 2008-06-05 and 2009-06-24 dates found in the response belong to nested entity records (registrant 7ESG, registrar REGIS10-ARIN), not the autnum object, so they are not used per the no-fabrication rule
[Confirmed absence at top level] — rdap.arin.net/registry/autnum/735
Org status
active per ARIN RDAP status field [Confirmed] — rdap.arin.net/registry/autnum/735
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil; DISA-Columbus, 300 North James Road, Whitehall, OH 43213; registrant address 501 East Moore Dr Bldg 884 Rm 1100 Gunther Annex, Maxwell AFB, AL 36114 [Confirmed] — ARIN RDAP entity 7ESG

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 — not on Spamhaus ASN-DROP or NANOG archives; several secondary sources (Talos, Spamhaus interactive checker, bgpview.io) were unreachable this session and are disclosed as unverified rather than assumed clean

[Likely] — spamhaus.org/drop/asndrop.json, marc.info NANOG archive

Network & routing

Network type
U.S. military/DoD (Air Force) network infrastructure, not a commercial ISP [Likely] — ARIN RDAP autnum
Size
dormant — 0 IPv4 prefixes / 0 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / announced-prefixes, CAIDA AS Rank (2026-07)
Routing/peering
NOT announced — 0 of 331 IPv4 RIS peers and 0 of 324 IPv6 RIS peers see this ASN; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB network profile exists (404) [Confirmed] — stat.ripe.net, asrank.caida.org, peeringdb.com/asn/735
RPKI
not assessable — AS735 announces no prefixes, so there are no ROAs to validate [Confirmed] — stat.ripe.net
Notable usage
falls inside ARIN block AS727–AS746 ("AFCONC-BLOCK2-AS"), assigned to Air Force Systems Networking; bgp.he.net shows 0 originated prefixes and 0 peers as of 2026-07-25 [Confirmed] — bgp.he.net/AS735
Related ASNs
sibling ASNs within the AS727–AS746 "AFCONC-BLOCK2-AS" block, all assigned to Air Force Systems Networking [Likely] — rdap.arin.net/registry/autnum/735
Analyst note
Dormant DoD-held ASN with no public web presence and no PeeringDB profile; WebSearch was exhausted for this session (200/200) before community corroboration (angle A5) could run, so NANOG/Reddit-style third-party mentions remain unresearched this cycle.
[ 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.