AS447

AS447 is a legacy autonomous system number administered under ARIN for the U.S. Department of Defense. It does not carry its own per-ASN registration record: RDAP for AS447 resolves to a shared block object with handle AS379, name AFCONC-BLOCK1-AS, spanning the contiguous range AS379–AS508, which ARIN allocated to the Air Force as a single administrative block. The registrant organization is Air Force Systems Networking (ARIN org handle 7ESG, Maxwell AFB, AL), with the abuse, administrative, and technical point of contact delegated to DISA's Columbus field office. The defining triage point for AS447 is that it is operationally dormant. Every routing source consulted agrees it announces zero IPv4 and zero IPv6 prefixes and has no visible BGP presence: RIPEstat reports announced=false with 0 of 325 IPv4 RIS peers and 0 of 321 IPv6 RIS peers seeing it, 0 observed neighbours, and no announced-prefix history at all across its lookback window. CAIDA AS Rank corroborates this — seen=false, cliqueMember=false, a customer cone of just the ASN itself (1 ASN, 0 prefixes, 0 addresses), and an AS degree of zero across customer, peer, and provider. Its CAIDA rank of 79,459 sits near the bottom of the global ranking, reflecting complete routing inactivity. RPKI posture cannot be assessed because there are no active originations and therefore no ROAs. No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus SBL/DROP/ASN-DROP, AbuseIPDB, or NANOG archives — consistent with a clean, dormant government ASN with no live attack surface. No PeeringDB network object exists for AS447 (HTTP 404), and no per-ASN peering policy is published.

Operator

Air Force Systems Networking (U.S. DoD / U.S. Air Force; ARIN org handle 7ESG, 501 East Moore Dr., Maxwell AFB, AL 36114; admin/abuse contact delegated to DISA-Columbus) [Confirmed] — ARIN RDAP autnum/447

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)

Allocated

1989-08-04 (ARIN registry date for the AFCONC-BLOCK1-AS block covering AS447, from the RDAP autnum TOP-LEVEL registration event — first-party RIR fact, NOT an IEEE date); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events

Org status

registry status active (per ARIN RDAP status[]); routing status operationally dormant — not currently announced and no observed announcement history [Confirmed] — ARIN RDAP, bgp.he.net

Contacts

abuse disa.columbus.ns.mbx.arin-registrations@mail.mil; +1-844-347-2457 ext.2; DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — RIPEstat abuse-contact-finder, ARIN RDAP

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus SBL/DROP/ASN-DROP, AbuseIPDB, or NANOG archives; no hijack, malware, botnet, or spoofing association for AS447 or the parent block; dormancy means no live attack surface

Network & routing

Network type

government/military autonomous system block (U.S. Air Force / DoD), administered by DISA; not a commercial ISP, hosting provider, or IXP participant. Specific operational use of AS447 within the block is Unknown [Confirmed for type; Unknown for specific use] — ARIN RDAP, ipinfo.io/AS447

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / CAIDA AS Rank / bgp.he.net (2026-07)

Routing/peering

NOT announced — announced=false; 0 RIS peers seeing it (0/325 v4, 0/321 v6); 0 observed neighbours; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible. RIPEstat shows no announced-prefix history at all across its lookback

[Confirmed] — RIPEstat routing-status, CAIDA AS Rank, bgp.he.net

Peering policy

Unknown / not publicly documented — no PeeringDB network object exists (peeringdb.com/api/net?asn=447 → HTTP 404); DISA publishes general DISN connection process info but no per-ASN policy [Confirmed sourced null] — peeringdb.com/api/net?asn=447

RPKI

not assessable — AS447 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation requires a prefix and was skipped [Confirmed] — RIPEstat

Notable usage

None found. AS447 is not currently announced in global BGP and has no originated-prefix or historical-peer record on file [Likely] — bgp.he.net/AS447, ipinfo.io/AS447

Related ASNs

AS379–AS508 (all members of the same AFCONC-BLOCK1-AS DoD/Air Force block); sibling enriched entries include AS385, AS386, AS390, AS391, AS393, AS397–AS401 [Confirmed for block; Likely for the sibling list] — ARIN RDAP

Registry handle / block

AS379 (block AS379–AS508); as_name AFCONC-BLOCK1-AS. AS447 has no separate per-ASN RDAP record — the block object is the authoritative registry source [Confirmed] — ARIN RDAP autnum/447

Analyst note

Encountered as a dormant legacy government ASN whose RDAP record is a block registration (AS379–AS508), not a per-ASN object. Clean, inactive ASN; the 1989-08-04 block registration date is recorded as the authoritative first-party ARIN allocated_date.