AS483
Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.
Summary
- // analyst note
- Dormant legacy DoD block-member ASN with no individually dated RDAP record of its own (shares the AS379–AS508 AFCONC-BLOCK1-AS block record). No PeeringDB presence, no public abuse signal, no operator-official website found.
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-10; absent from Spamhaus ASN-DROP; not found in NANOG archives; dormant/unrouted (0 v4/v6 prefixes, 0 RIS peers).
About this ASN.
AS483 is not a standalone RDAP object; ARIN's autnum lookup for 483 resolves to a large legacy block registration, handle AS379, named AFCONC-BLOCK1-AS, spanning AS379 through AS508. The block is registered to Air Force Systems Networking, a U.S. Air Force / Department of Defense numbering resource administered via DISA Columbus (Organization ID 7ESG), with a registrant address at Maxwell AFB, Alabama and abuse/administrative/technical contact routed through DISA Columbus in Whitehall, Ohio. The block's top-level RDAP registration event is dated 1989-08-04, with a last-changed event of 2008-06-06 — these are the correct, non-decoy autnum-level dates; the nested entity records (org 7ESG registered 2008-06-05, POC REGIS10-ARIN registered 2009-06-24) are unrelated entity metadata and were not used as the allocation date. AS483 itself is currently dormant: RIPEstat shows zero announced IPv4 and IPv6 prefixes and zero of roughly 320+ RIS peers seeing it, while CAIDA ASRank places it at rank 79,459 with an empty customer cone (1 ASN, 0 prefixes, 0 addresses) and zero AS-graph degree in any direction. No PeeringDB entry exists for AS483, either directly or under the Air Force Systems Networking org profile (which lists five other unrelated ASNs), and no abuse, hijack, or community-discussion signal was found in Spamhaus ASN-DROP, NANOG archives, or elsewhere — consistent with a quiet, registry-only member of a large DoD ASN block rather than an actively routed network.
- Operator
- Air Force Systems Networking (U.S. Air Force / DoD; ARIN OrgID 7ESG), administered via DISA Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/483
- Country / RIR
- US, ARIN [Confirmed] — https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=483
- Allocated
- 1989-08-04 (block-level ARIN RDAP top-level registration event, NOT an IEEE date); last changed 2008-06-06 [Confirmed] — https://rdap.arin.net/registry/autnum/483
- Org status
- block record status "active" per RDAP; says nothing about AS483's own operational use, since no operator page addresses that [Confirmed] — https://rdap.arin.net/registry/autnum/483
- Contacts
- disa.columbus.ns.mbx.arin-registrations@mail.mil, +1-844-347-2457 ext 2 (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] — https://rdap.arin.net/registry/autnum/483
Security/abuse context (NEUTRAL, DATED)
no notable public abuse signal as of 2026-07-10; absent from current Spamhaus ASN-DROP list; no NANOG-archive discussion located; dormant/unrouted
Network & routing
- Network type
- legacy ARIN direct allocation to a DoD entity, member of block AFCONC-BLOCK1-AS (AS379–AS508); not a commercial ISP/hosting network [Confirmed] — https://rdap.arin.net/registry/autnum/483
- Size / routing
- dormant — 0 IPv4 prefixes, 0 IPv6 prefixes, 0/326 RIS peers seeing it (v4), 0/321 (v6); customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=483, https://api.asrank.caida.org/v2/restful/asns/483
- Routing/peering
- not announced; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB entry for AS483 directly (API 404) or under org "Air Force Systems Networking" (org id 20118, which lists AS123/AS65/AS175/AS221/AS301 instead)[Confirmed] — https://www.peeringdb.com/org/20118, https://www.peeringdb.com/api/net?asn=483
- RPKI
- not assessable — no announced prefixes, so RIPEstat rpki-validation could not run (requires a prefix) [Confirmed] — https://stat.ripe.net/data/rpki-validation/data.json?resource=483
- Notable usage
- none documented from operator-official sources; a separately-researched sibling ASN in the same block (AS482) found only a brief historical 2001 route announcement via third-party routing telemetry, offered as context only, not verified for AS483 itself [Unknown for AS483 specifically] — no citation
- Related ASNs
- member of block AS379–AS508 (AFCONC-BLOCK1-AS); other block members previously enriched include AS479 and AS482 [Likely] — https://rdap.arin.net/registry/autnum/483
- Analyst note
- dormant legacy DoD block-member ASN; no individually dated RDAP record of its own (shares the AS379–AS508 block record); no PeeringDB presence; no website (af.mil returned 403 and is not ASN-specific).