AS730

AS730 is a dormant, unannounced autonomous system registered under ARIN to Air Force Systems Networking, a U.S. Air Force/DoD network, currently originating zero IPv4 and zero IPv6 prefixes in the global routing table.

The ASN belongs to the ARIN block AS727–AS746 (AFCONC-BLOCK2-AS), whose registrant handle 7ESG lists an address at Maxwell AFB, Alabama, and whose administrative contact routes through DISA Columbus (Defense Information Systems Agency). Two independent live RDAP fetches agree on this block membership.

AS730 has no individual RDAP record with a "registration" event: the autnum's top-level RDAP events list carries only a "last changed" entry dated 2008-06-06, confirmed by a live re-fetch rather than a truncation artifact. An entity-level date exists nearby — a registrant "registration" event dated 2008-06-05 — but that is not AS730's own allocation record, so allocated_date is reported as a sourced Unknown rather than borrowed from that decoy.

Routing sources are unanimous: CAIDA AS Rank places AS730 at 79,459 with a singleton customer cone (itself only, 0 prefixes, 0 addresses), and bgp.he.net/bgp.tools independently confirm zero announced prefixes and zero visible peers. No PeeringDB profile exists for AS730 or its parent block, and no operator-official website could be located — afsystemsnetworking.af.mil fails to resolve, and maxwell.af.mil/afmc.af.mil both returned HTTP 403.

Operator

Air Force Systems Networking (U.S. Air Force/DoD network; ARIN registrant handle 7ESG, Maxwell AFB, AL) [Confirmed] — https://rdap.arin.net/registry/autnum/730

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/730

Allocated

Unknown — the autnum's top-level RDAP events[] contains no "registration" eventAction, only a "last changed" event dated 2008-06-06; a registrant-entity date (2008-06-05) exists but is not AS730's own top-level allocation record [Confirmed absence, verified via live re-fetch] — https://rdap.arin.net/registry/autnum/730

Org status

active per ARIN RDAP [Confirmed] — https://rdap.arin.net/registry/autnum/730

Contacts

disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA Columbus); registrant address 501 East Moore Dr. Bldg 884 Rm 1100, Gunther Annex, Maxwell AFB, AL 36114 [Confirmed] — https://rdap.arin.net/registry/autnum/730

Website

Unknown — no operator-official website located [Unknown]

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25; one lower-authority third-party aggregator reports no honeypot observations for AS730; Spamhaus ASN-lookup, NANOG archives, and Qrator Radar bogon/hijack detail could not be directly verified this session (404 / CAPTCHA-blocked / JS-rendered)

Network & routing

Network type

not publicly routed; consistent with a non-publicly-routed internal U.S. Air Force/DoD network (0 announced prefixes observed), not confirmed by an operator statement [Likely] — https://bgp.he.net/AS730

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS730, https://asrank.caida.org/, https://bgp.he.net/AS730, https://bgp.tools/as/730

Routing/peering

NOT announced — 0 upstreams / 0 peers / 0 downstreams per CAIDA asnDegree and 0 BGP peers per bgp.he.net/bgp.tools; no PeeringDB entry for AS730 or the parent block [Confirmed] — https://asrank.caida.org/, https://www.peeringdb.com/api/net?asn=730

RPKI

not assessable — AS730 announces no prefixes, so there are no ROAs to validate [Confirmed] — https://stat.ripe.net/AS730

Notable usage

Unknown — no operator-official page describing mission/usage was reachable; candidate .mil domains failed DNS (afsystemsnetworking.af.mil) or returned HTTP 403 (maxwell.af.mil, afmc.af.mil) [Unknown]

Related ASNs

block AS727–AS746 (AFCONC-BLOCK2-AS, handle AS727), confirmed via two independent live RDAP fetches [Confirmed] — https://rdap.arin.net/registry/autnum/730

Analyst note

Dormant, unannounced DoD/Air Force ASN with no individual RDAP allocation event; live routing is entirely absent (0 prefixes, 0 peers across RIPEstat, CAIDA, bgp.he.net, bgp.tools). Website and mission-usage unreachable; abuse-feed coverage bounded by session access limits rather than confirmed clean.