Autonomous system detail

AS785

Not announced

Operated by DNIC-AS-00785 - Headquarters, USAISC.

Summary

// analyst note
Dormant DoD/Army administrative ASN administered by the DoD Network Information Center. No live routing, no PeeringDB entry or peering policy, no confirmed related or successor ASN (adjacent DNIC-family ASNs AS765/767/768/769/770 surfaced in search results but no explicit link was confirmed). All routing/registry sources consulted (ARIN RDAP, RIPEstat, CAIDA) agree on zero announcements and zero peers.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-08-01; not in Spamhaus ASN-DROP (2026-07-27 edition); URLhaus check inaccessible (bot-check wall, Unknown not a confirmed negative); unrelated to the 2021 AS8003 dormant-DoD-space announcement incident.
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

AS785 is a dormant U.S. Department of Defense autonomous system, registered under ARIN as DNIC-AS-00785 to "Headquarters, USAISC" (U.S. Army Information Systems Command). As of 2026-08-01 it announces zero IPv4 and zero IPv6 prefixes and is invisible in the global routing table, with 0 of roughly 328 RIS peers observing any IPv4 route and 0 of roughly 322 observing any IPv6 route from it.

The ASN was registered on 1990-11-20 per ARIN RDAP's top-level autnum registration event, with a last-changed event dated 2011-08-02. Registration status is Active, but that reflects the ARIN record's good standing, not live routing — CAIDA's ASRank shows a customer cone of a single ASN (itself), zero prefixes, and zero addresses, with an AS rank of 79,459 near the bottom of the global table.

USAISC, the ASN's original registrant, was inactivated as a U.S. Army command in 1996 with its functions folded into successor Army signal and network organizations; ARIN's organization record has not been renamed to reflect that. Administrative control of the registration now runs through the DoD Network Information Center (DNIC), operated by DISA in Columbus, Ohio, which handles ARIN contact and abuse duties for this and other DNIC-prefixed military ASNs.

No operator-run website, PeeringDB entry, or public peering policy exists for AS785, consistent with a non-commercial DoD administrative allocation rather than a network that solicits transit or peering relationships. No NANOG archive posts or community-forum discussion naming AS785 were found, which is expected for government-administered address space that does not participate in commercial reputation or operator communities.

Operator
Headquarters, USAISC (US Army Information Systems Command); DoD Network Information Center administers the ARIN registration (contact handle REGIS10-ARIN). USAISC itself was inactivated as a command in 1996 with functions transferred to successor Army signal commands, and ARIN's org record has not been renamed [Likely] — ARIN RDAP autnum record (rdap.arin.net/registry/autnum/785), Wikipedia (United States Army Information Systems Engineering Command)
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum record
Allocated
1990-11-20 (ARIN RDAP autnum top-level registration event, not an entity-level date); last changed 2011-08-02 [Confirmed] — ARIN RDAP autnum record
Org status
ARIN registration status Active (record in good standing) but operationally dormant/unrouted (0 announced prefixes); original registrant USAISC was inactivated as a U.S. Army command in 1996 and ARIN's org record has not been renamed to a successor [Likely] — ARIN RDAP autnum record
Contacts
DoD Network Information Center (REGIS10-ARIN), DISA-Columbus, 300 North James Road, Whitehall, OH 43213, US; disa.columbus.ns.mbx.arin-registrations@mail.mil (shared registration mailbox); registrant organization address Fort Huachuca, AZ 85613, US [Confirmed] — ARIN RDAP autnum record

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-08-01; not in Spamhaus ASN-DROP (2026-07-27 edition); URLhaus check inaccessible (bot-check wall, treated as Unknown, not a confirmed negative); unrelated to the 2021 AS8003 dormant-DoD-space announcement incident [Likely] — spamhaus.org/drop/asndrop.txt, urlhaus.abuse.ch/asn/785, kentik.com/blog/the-mystery-of-as8003, seclists.org/nanog/2021/Mar/193

Network & routing

Network type
U.S. Department of Defense / U.S. Army administrative ASN, not a commercial ISP, content network, or transit provider [Likely] — ARIN RDAP autnum record
Size
dormant — 0 IPv4 and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; CAIDA AS rank 79,459 [Confirmed] — RIPEstat announced-prefixes / as-overview, CAIDA ASRank AS785 (2026-07/08)
Routing/peering
NOT announced — 0 of ~328 RIS peers see it in IPv4, 0 of ~322 in IPv6; CAIDA degree total 0 (customer 0, peer 0, provider 0) [Confirmed]. No PeeringDB entry or public peering policy found [Unknown] — RIPEstat routing-status, CAIDA ASRank AS785
RPKI
not assessable — AS785 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation was skipped (no prefix supplied) [Unknown] — RIPEstat
Notable usage
no current routed usage; IPinfo lists AS785 with 0 IPv4 / 0 IPv6 prefixes and describes it as inactive for routing as of the query date [Likely] — ipinfo.io/AS785
Related ASNs
Unknown — no confirmed related or successor ASN found for AS785; other DNIC-prefixed DoD ASNs (AS765, AS767, AS768, AS769, AS770) surfaced as pattern-similar in search results but no explicit organizational link to AS785 was confirmed [Unknown] — db-ip.com/as785-headquarters-usaisc
Analyst note
Encountered as a dormant DoD/Army administrative ASN with no live routing. WHOIS/RDAP resolves to a DoD Network Information Center-administered record for a command (USAISC) inactivated since 1996; no successor ASN or corporate presence was confirmed. Clean, unrouted ASN with no abuse signal.
[ 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.