AS650
Operated by DNIC-ASBLK-00616-00665 - United States Department of Defense (DoD).
Summary
- // analyst note
- RDAP query for AS650 resolves to the DNIC-ASBLK-00616-00665 block record (handle AS616); ARIN exposes no distinct per-ASN sub-record within this DNIC block, so the block-level top-level registration date is the correct first-party value for AS650's allocated_date. Dormant since at least 2025-02-18 per bgp.he.net; all routing sources (RIPEstat, CAIDA) agree on zero announcements, zero peers, singleton cone.
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17; not in NANOG mailing-list archives or general threat-intel indexes.
About this ASN.
AS650 is a legacy autonomous system number administered by the U.S. Department of Defense (DoD) through the Defense Information Systems Agency's Columbus, Ohio office, and it sits inside the DNIC-ASBLK-00616-00665 block, a flat range covering AS616 through AS665. ARIN's RDAP record for this range gives a top-level registration event of 1990-04-19, with a most recent update on 2025-09-12; the registrant is the United States Department of Defense (DoD) under ARIN organization handle USDDD, with abuse/NOC/technical duties assigned to a contact object named "Network DoD" and administrative duties to a separate "Registration" contact, both routed through DISA-Columbus mail addresses. The RDAP payload also nests three unrelated contact-record dates — 1993-05-26, 2007-01-12, and 2009-06-24 — that belong to individual ARIN entity (contact/org) objects rather than the autnum itself; these are not the ASN's allocation date and are excluded here. Operationally AS650 is dormant: RIPEstat and CAIDA agree it currently originates zero IPv4 and zero IPv6 prefixes, is seen by none of RIPE RIS's 326 IPv4 or 321 IPv6 peers, and has a CAIDA customer cone of exactly one ASN (itself) with zero observed upstreams, peers, or customers. Hurricane Electric's BGP Toolkit additionally reports the ASN has not been visible in the global routing table since February 18, 2025, with one historical peer relationship on record. No public abuse, hijack, or incident reporting specific to AS650 was found; Spamhaus's direct ASN-query endpoint returned an HTTP 403 during this research pass, so its listing status could not be independently confirmed and is recorded as unknown rather than assumed clean.
- Operator
- United States Department of Defense (DoD), administered via DISA-Columbus (Defense Information Systems Agency); ARIN org handle USDDD [Confirmed] — https://rdap.arin.net/registry/autnum/650
- Country / RIR
- US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), https://stat.ripe.net/AS650
- Allocated
- 1990-04-19 (ARIN RDAP top-level autnum registration event for the DNIC-ASBLK-00616-00665 block that contains AS650); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/650 (nested entity-record dates 1993-05-26, 2007-01-12, and 2009-06-24 belong to individual contact/org objects, not the autnum, and are excluded)
- Website
- Unknown — no operator website is listed in the PeeringDB record, and disa.mil does not identify itself as operator of AS650 or the DNIC block specifically [Confirmed absence] — https://www.peeringdb.com/net/17359, https://www.disa.mil
- Org status
- Active. ARIN RDAP shows the block Active, last changed 2025-09-12; PeeringDB org status "ok" as of 2026-04-04 [Confirmed] — https://rdap.arin.net/registry/autnum/650, https://www.peeringdb.com/net/17359
- Contacts
- MIL-HSTMST-ARIN (noc/technical/abuse) disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil, +1-844-347-2457 ext2; REGIS10-ARIN (administrative/technical) disa.columbus.ns.mbx.arin-registrations@mail.mil; both at DISA-Columbus, 300 North James Road, Whitehall, OH 43213[Confirmed] — https://rdap.arin.net/registry/autnum/650
Security/abuse context (NEUTRAL, DATED)
no notable public abuse signal found as of 2026-07-17; not found in NANOG mailing-list archives or general threat-intel report indexes; Spamhaus's direct ASN-query page returned HTTP 403 so its listing status is Unknown, not confirmed clean; no named security incident specific to AS650 found
Network & routing
- Network type
- U.S. federal/military (DoD) network, not a commercial ISP/content/enterprise network; PeeringDB leaves its network-type field blank [Likely] — https://www.peeringdb.com/net/17359
- Size / routing status
- dormant — 0 IPv4 and 0 IPv6 prefixes announced; 0/326 RIPE RIS v4 peers and 0/321 v6 peers see it; 0 observed neighbours; not visible in Hurricane Electric's BGP table since 2025-02-18 [Confirmed] — https://stat.ripe.net/AS650, https://bgp.he.net/AS650
- Routing/peering
- CAIDA AS Rank 79459; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; degree total 0 (customer 0 / peer 0 / provider 0) [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/650. One historical BGP peer relationship with AS263650 (Clicfacil Telecom, Brazil) is reported by Hurricane Electric[Likely, single source] — https://bgp.he.net/AS650
- Peering policy
- PeeringDB lists "Open" but shows no facilities, no public/private peering points, and 0 announced prefixes — read as an unmaintained default rather than an active public policy [Likely] — https://www.peeringdb.com/net/17359
- RPKI
- not evaluated in this pass — AS650 announces no prefixes, so there is no route object to validate against [Unknown] — https://stat.ripe.net/AS650
- Notable usage
- falls within the DoD's DNIC-ASBLK-00616-00665 block (AS616–AS665); no public route announcements or traffic disclosure were found, consistent with internal DoD/military network use rather than public-internet transit[Likely] — https://rdap.arin.net/registry/autnum/650, https://www.peeringdb.com/net/17359
- Registry block
- DNIC-ASBLK-00616-00665 — AS616–AS665 flat block; ARIN handle "AS616" is the block record [Confirmed] — https://rdap.arin.net/registry/autnum/650
- Analyst note
- an RDAP query for AS650 resolves to the DNIC-ASBLK-00616-00665 block record (handle AS616), not a distinct per-ASN sub-record — ARIN does not expose one within this DNIC block — so the block's top-level registration date is the correct first-party value recorded as AS650's allocated_date.