AS647

AS647 is a legacy autonomous system number held by the United States Department of Defense, registered under ARIN as part of the DNIC block DNIC-ASBLK-00616-00665, which spans AS616 through AS665. The block's ARIN RDAP autnum object carries a top-level registration event dated 1990-04-19, with a last-changed event of 2025-09-12; this is the first-party registry date for the block covering AS647, corroborated independently by a bgp.tools snippet that also states an April 19, 1990 registration. Administrative and technical points of contact trace to DISA-Columbus (Whitehall, OH), and the registrant organization address is Columbus, OH; operational network management is associated with the Navy Network Information Center (NNIC) in Virginia Beach, VA. The ASN is actively announced today, originating several hundred IPv4 prefixes — third-party BGP observatories disagree on the exact count, ranging from roughly 406 to 509 prefixes — concentrated in the legacy 205.x.x.x DoD-assigned address range, with no IPv6 announcements. No public peering policy or PeeringDB entry exists; the only visible BGP relationships are to other internal DoD ASNs. No abuse-feed or blocklist hits were found, though Hurricane Electric flags the ASN with an automated "announces bogons" routing-hygiene note, which is a data-quality flag rather than a security incident.

Operator

United States Department of Defense (DoD), ARIN org handle USDDD, registrant address 3990 E. Broad Street, Columbus, OH 43218; block DNIC-ASBLK-00616-00665 (AS616–AS665) [Confirmed] — https://rdap.arin.net/registry/autnum/647

Country / RIR

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

Allocated

1990-04-19, read from the autnum TOP-LEVEL registration event for block DNIC-ASBLK-00616-00665 (not the nested entity-level events, which are decoys: MIL-HSTMST-ARIN 1993-05-26, REGIS10-ARIN 2009-06-24, USDDD org 2007-01-12); last changed 2025-09-12

[Confirmed] — https://rdap.arin.net/registry/autnum/647, corroborated https://bgp.tools/as/647

Org status

active [Confirmed] — https://rdap.arin.net/registry/autnum/647

Contacts

abuse/hostmaster disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil; registrations disa.columbus.ns.mbx.arin-registrations@mail.mil; admin/tech HQ 300 North James Road, Whitehall, OH 43213 [Confirmed] — https://rdap.arin.net/registry/autnum/647

Website

Unknown — no public page specifically documenting AS647 or offering peering/IR contact info was located; DISA's general site (https://www.disa.mil/) is the parent-organization homepage only, not AS647-specific [Unknown]

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17 in Spamhaus ASN-DROP, abuse.ch (Feodo Tracker, SSLBL), or NANOG mailing-list archives; Hurricane Electric's bgp.he.net separately flags "AS647 announces bogons," an automated routing-hygiene note (observed origination of one or more bogon/reserved ranges), which is a data-quality flag, not an abuse/threat-feed listing [Confirmed for the bogon flag; Likely for the absence of abuse-feed hits] — https://bgp.he.net/AS647, https://www.spamhaus.org/drop/asndrop.txt

Network & routing

Network type

government/military autonomous system (U.S. DoD infrastructure), non-commercial; not independently registered as a single autnum but served under the DNIC block [Confirmed] — https://rdap.arin.net/registry/autnum/647, https://stat.ripe.net/AS647

Size

IPv4 prefix count reported inconsistently across sources — ~406 per bgp.tools vs. roughly 466–509 per other snapshots; 0 IPv6 prefixes announced (agreed across sources); address-space estimates likewise vary widely (~369,000 to ~1,441,792 IPv4 addresses depending on source) [Likely, stated as a range due to source disagreement] — https://bgp.tools/as/647, https://ipinfo.io/AS647, https://ipregistry.co/AS647

Routing/peering

no published peering policy and no PeeringDB entry for AS647; observed BGP relationships are limited to other internal DoD ASNs (AS27066, AS27064 — both "DoD Network Information Center"); reported as 1 upstream and 1 peer by bgp.tools but the counterparty names were not resolved from that source [Confirmed absence of public policy; Likely for peer/upstream counts] — https://bgp.he.net/AS647, https://bgp.tools/as/647

RPKI

not assessed — the supplied RIPEstat rpki-validation query requires a specific prefix and was skipped; no ROA/RPKI status found via other sources [Unknown] — https://stat.ripe.net/AS647

Notable usage

announces prefixes predominantly in the legacy 205.x.x.x Navy Network Information Center range; ranked approximately #166 for originated IPv4 space in the United States per one source [Likely] — https://ipinfo.io/AS647, https://bgp.he.net/AS647

Related ASNs

block DNIC-ASBLK-00616-00665 spans AS616–AS665; observed BGP peers are the internal DoD ASNs AS27066 and AS27064 [Confirmed for the block range; Likely for the peer ASNs] — https://rdap.arin.net/registry/autnum/647, https://bgp.he.net/AS647

Analyst note

dormant public documentation (no PeeringDB entry, no dedicated operator page) paired with an actively announced, several-hundred-prefix DoD network; the wide variance in third-party prefix/address-count estimates should be read as observatory disagreement, not a data-quality flag on the ASN itself.