Autonomous system detail

AS741

Not announced

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

Summary

// analyst note
Dormant DoD/Air Force ASN inside shared ARIN block AFCONC-BLOCK2-AS (727-746). allocated_date left null: the autnum's top-level events[] carries only a 'last changed' entry (2008-06-06), no top-level 'registration' event; a 2008-06-05 date found by two other research angles belongs to a nested registrant entity (handle 7ESG), not the autnum itself, confirmed via direct raw RDAP JSON parse.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-27; Spamhaus ASN-DROP could not be directly queried (404) and NANOG archive search returned no hits naming AS741 — a coverage gap, not a confirmed-clean record.
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: Likely

AS741 is a dormant autonomous system registered to Air Force Systems Networking (AFSN), a Department of the Air Force program, and it currently announces zero IPv4 or IPv6 prefixes in the public routing table. Every routing source checked — RIPEstat, CAIDA AS Rank, bgp.he.net, and bgp.tools — agrees the ASN carries no live BGP activity.

The ARIN RDAP record for AS741 resolves to a shared block object, AFCONC-BLOCK2-AS, covering the ASN range 727–746 and held by Air Force Systems Networking. That record's top-level events list only a "last changed" entry dated 2008-06-06; it carries no top-level "registration" event. A nearby date, 2008-06-05, belongs instead to a nested registrant entity (handle 7ESG) inside the same record and is not the autnum's own registration date — a decoy worth flagging explicitly since it superficially resembles the block's registration date.

AFSN supports the Air Force's classified and unclassified data communications, from base level up through the Air Force Enterprise Network (AFNET), the Joint Regional Security Stack (JRSS), and USAF components of the Joint Information Environment, both CONUS and OCONUS, per a description from IT subcontractor Solutions71. No dedicated public-facing website or PeeringDB network object exists for AS741 specifically.

CAIDA ranks AS741 at 79,459 — near the bottom of the global table — with a customer cone limited to the ASN itself (0 prefixes, 0 addresses) and an AS degree of zero across customer, peer, and provider relationships. RPKI validation does not apply, since there are no announced prefixes to hold a ROA.

Operator
Air Force Systems Networking (ARIN registrant org, handle 7ESG) — US Air Force, Business and Enterprise Systems Directorate [Confirmed] — ARIN RDAP; solutions71.com/air-force-systems-networking-afsn
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum record
Allocated / registered
Unknown — the autnum's top-level events[] carries only a "last changed" entry (2008-06-06); no top-level "registration" event is published. A 2008-06-05 date exists but belongs to the nested registrant entity (handle 7ESG), not the autnum record itself, and is excluded per no-fabrication rules [Confirmed (confirmed absent, verified via direct raw RDAP JSON fetch)] — https://rdap.arin.net/registry/autnum/741. Note: two other angles (A2, A4) read this same record and reported the entity-level date as the block's registration date (2008-06-05) — flagged here as the likelier misread given A3's explicit top-level/nested-entity event parse.
Org status
active (ARIN RDAP status: active) [Confirmed] — ARIN RDAP
Contacts
DISA-Columbus (Registration group), 300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil; +1-844-347-2457 ext2; registrant address 501 East Moore Dr., Bldg 884, Rm 1100, Gunther Annex, Maxwell AFB, AL 36114 [Confirmed] — ARIN RDAP
Website
Unknown — no dedicated operator-branded website found for AS741; the related-but-distinct entity AFNIC has afnic.af.mil [Unknown] — afnic.af.mil

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-27; Spamhaus ASN-DROP could not be directly queried (404) and NANOG archive search returned no hits — coverage gap, not confirmed-clean

[Likely] — spamhaus.org/blocklists/botnet-controller-list, nanog.org

Network & routing

Network type
US federal/military (Department of the Air Force) enterprise network; non-commercial, not a transit/eyeball ISP [Likely] — solutions71.com; ARIN RDAP
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; CAIDA AS rank 79,459 [Confirmed] — RIPEstat routing-status, CAIDA AS Rank, bgp.he.net, bgp.tools (2026-07)
Routing/peering
NOT announced — 0/329 RIS peers seeing v4, 0/324 seeing v6; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB network object for AS741 (api/net?asn=741 returned 404) [Confirmed]
RPKI
not assessable — AS741 announces no prefixes, so there are no ROAs to validate [Confirmed]
Notable usage
AFSN supports design, install, and sustainment of Air Force classified/unclassified data communications from base level through AFNET, JRSS, and USAF components of the JIE, CONUS and OCONUS [Likely, single third-party subcontractor source] — solutions71.com/air-force-systems-networking-afsn
Related ASNs
part of the shared ARIN block AFCONC-BLOCK2-AS, ASN range AS727AS746 [Confirmed] — ARIN RDAP autnum record
ASN
AS741 [Confirmed] — https://rdap.arin.net/registry/autnum/741
Last changed (registry record)
2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events
Analyst note
Dormant US DoD/Air Force ASN inside a shared ARIN block (AFCONC-BLOCK2-AS, 727–746). WHOIS/RDAP is block-level, not per-ASN. The allocated_date is left null rather than fabricated from an entity-level decoy date one day off from the block's true "last changed" event — flagging the discrepancy against two other research angles that read it differently.
[ 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.