Autonomous system detail

AS736

Not announced

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

Summary

// analyst note
Dormant DoD/USAF ASN inside a shared block (AS727-AS746). The autnum's top-level RDAP events[] carries no registration date, only a 'last changed' event of 2008-06-06; two nested entity-level dates (2008-06-05, 2009-06-24) were deliberately excluded from allocated_date since neither is the autnum's own registration event. ipinfo.io's 1970-01-01 display for this record is an epoch placeholder, not a real date, and was excluded.
// security note
NEUTRAL/DATED: not listed in Spamhaus ASN-DROP as of 2026-07-26; broader web/NANOG abuse search inconclusive due to search-tool budget exhaustion; currently unrouted, so live abuse exposure is structurally low.
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

AS736 is a dormant, currently-unannounced autonomous system number that sits inside a shared U.S. Air Force numbering block. ARIN records it under AFCONC-BLOCK2-AS, a range spanning AS727 through AS746, registered to "Air Force Systems Networking" (org handle 7ESG) and administered by DISA-Columbus. No routing source shows it announcing any prefixes today.

The registrant address is Maxwell Air Force Base's Gunther Annex in Alabama, while day-to-day registration, abuse, and technical contact runs through DISA-Columbus in Whitehall, Ohio. This is consistent with a Department of Defense internal numbering assignment rather than a commercial network with public-facing infrastructure — no operator website could be located.

Routing data from RIPEstat, bgp.he.net, and bgp.tools agree AS736 currently originates 0 IPv4 and 0 IPv6 prefixes, has 0 visible BGP peers among roughly 330 RIPE RIS route collectors, and carries a CAIDA AS rank of 79,459, near the bottom of the global ranking. Its customer cone is a singleton — itself, 0 prefixes, 0 addresses — and it has no PeeringDB listing.

The ARIN RDAP autnum record for this block carries no top-level registration event — only a top-level "last changed" timestamp of 2008-06-06. Two nested entity records inside the same response carry their own registration dates (2008-06-05 for org 7ESG, 2009-06-24 for the DISA-Columbus abuse contact), but neither is the autnum's own registration event, so the allocation date is recorded here as unverifiable rather than guessed.

Operator
Air Force Systems Networking (ARIN org handle 7ESG), administered by DISA-Columbus on behalf of the U.S. Air Force [Confirmed] — ARIN RDAP autnum 736, ARIN WHOIS org 7ESG
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum 736
Allocated
Unknown — the autnum's top-level RDAP events[] carries no "registration" eventAction, only a top-level "last changed" event dated 2008-06-06; two nested entity-level dates exist (7ESG 2008-06-05, REGIS10-ARIN abuse contact 2009-06-24) but neither is the autnum's own registration event, so no allocation date is asserted [Confirmed — re-verified via a second full RDAP fetch] — https://rdap.arin.net/registry/autnum/736
Org status
active per ARIN RDAP autnum record [Confirmed] — ARIN RDAP autnum 736
Contacts
registrant address 501 East Moore Dr., Bldg 884, Rm 1100, Gunther Annex, Maxwell AFB, AL 36114; abuse/admin/tech contact DISA-Columbus, 300 North James Road, Whitehall, OH 43213, disa.columbus.ns.mbx.arin-registrations@mail.mil [Confirmed] — ARIN RDAP autnum 736
Website
Unknown — no website/URL field exists in the ARIN org (7ESG) or autnum record, and no independent official operator site could be located [Unknown]

Security/abuse context (NEUTRAL, DATED)

no listing in Spamhaus ASN-DROP as of 2026-07-26; general web and NANOG-archive abuse search could not be completed this session (search-tool budget exhausted), so absence of other signals is inconclusive rather than confirmed-clean; structurally low risk given the ASN is currently unrouted

[Likely] — spamhaus.org/drop/asndrop

Network & routing

Network type
U.S. Department of Defense / U.S. Air Force internal government numbering block (not a commercial ISP); AS736 falls inside AFCONC-BLOCK2-AS, the shared range AS727–AS746, with no individually distinct autnum record [Confirmed] — ARIN RDAP autnum 736
Size
dormant — 0 IPv4 prefixes / 0 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; CAIDA AS rank 79,459 [Confirmed] — RIPEstat routing-status, bgp.he.net, bgp.tools, CAIDA ASRank (2026-07-26)
Routing/peering
NOT announced — 0 RIS peers seeing it (0/331 IPv4, 0/324 IPv6); CAIDA degree total 0 (customer 0, peer 0, provider 0); not listed in PeeringDB under /asn/736 or by ASN lookup (both 404) [Confirmed]
RPKI
not assessable — AS736 announces no prefixes, so there are no ROAs to validate; consistent zero RPKI-valid / RPKI-invalid origins across sources [Confirmed]
Notable usage
Unknown beyond the registry record — no route origination or traffic history found; the ASN appears currently unused/unannounced in the global routing table [Likely] — bgp.he.net/AS736
Related ASNs
AS727–AS746 (the full AFCONC-BLOCK2-AS block registered to the same org, 7ESG) [Confirmed] — ARIN RDAP autnum 736
Analyst note
A dormant DoD/USAF ASN sharing a block record with AS727–AS746; no individually distinct RDAP registration event exists for AS736 itself, and an earlier research pass conflated a nested entity's registration date with the autnum's own — that date was not carried forward here. ipinfo.io displays a 1970-01-01 epoch placeholder for this record, which was excluded as a database artifact, not a real date.
[ 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.