Autonomous system detail

AS767

Not announced

Operated by DNIC-AS-00767 - United States Department of Defense (DoD).

Summary

// analyst note
DoD DNIC-block ASN, effectively dormant in current routing across most sources (bgp.he.net shows 2 IPv4 prefixes at time of check, an unresolved conflict against RIPEstat/bgp.tools's 0). One stale historical announcement (192.84.125.0/24, 2000–2001). No DoD/DISA page identifies a specific purpose; official website left null because a 2026-07-31 fetch of disa.mil returned unrelated content, an inconclusive check rather than evidence about the real site.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-31; not in Spamhaus hijacking/blocklist resources, GreyNoise, NANOG mailing-list archives, or CAIDA ASRank.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
1
1 up · 1 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Medium

AS767 is a Department of Defense-registered ASN (DNIC-AS-00767) that currently announces zero prefixes and shows no active production routing today. RIPEstat and bgp.tools agree on zero announced IPv4 and IPv6 prefixes, and CAIDA's customer cone is a singleton (0 prefixes, 0 addresses) — though bgp.he.net shows 2 IPv4 prefixes at time of check, an unresolved source conflict rather than a confirmed change.

ARIN RDAP's autnum top-level registration event places allocation at 1990-10-31, independently corroborated by bgp.tools ("Registered on 31 Oct 1990"); the RDAP record itself was last updated 2025-09-12. The registrant organization address is 3990 E. Broad Street, Columbus, OH 43218; operational NOC/abuse contact runs through the DoD Network Information Center at DISA-Columbus, 300 North James Road, Whitehall, OH 43213.

The only historically observed announcement is 192.84.125.0/24, seen from 2000-08-18 to 2001-10-22 — stale, not current activity. CAIDA shows zero BGP degree (no customers, peers, or providers visible in topology), while third-party collectors note a single relationship with AS7767 (Encyclopaedia Britannica, an unrelated organization) that bgp.tools frames as upstream and bgp.he.net frames as a peer — a disputed classification, kept here as unverified context.

Operator-official detail is thin: no DoD or DISA page describing AS767's specific purpose, network type, or peering policy was located, and AS767 has no standalone PeeringDB network entry; the PeeringDB organization page for the US DoD (20 listed ASNs) does not include it. RPKI posture cannot be assessed while zero prefixes are currently announced, since validity is evaluated per-prefix.

Operator
United States Department of Defense (DoD); registered under ARIN handle DNIC-AS-00767; administered by the DoD Network Information Center (DoD NIC) / DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/767
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/767, https://stat.ripe.net/AS767
Allocated
1990-10-31 (ARIN RDAP autnum top-level registration event; corroborated by bgp.tools "Registered on 31 Oct 1990"); RDAP record last updated 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/767, https://bgp.tools/as/767
Org status
Active (per ARIN RDAP status field); registrant United States Department of Defense [Confirmed] — https://rdap.arin.net/registry/autnum/767
Contacts
abuse/hostmaster disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil; registrant org address 3990 E. Broad Street, Columbus, OH 43218; NOC/admin contact at DoD NIC, DISA-Columbus, 300 North James Road, Whitehall, OH 43213
[Confirmed] — https://rdap.arin.net/registry/autnum/767, https://stat.ripe.net/AS767

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-31 — not in Spamhaus hijacking/blocklist resources, GreyNoise, NANOG mailing-list archives, or CAIDA ASRank

[Confirmed] — https://www.spamhaus.org/resource-hub/hijacking/, https://bgp.tools/as/767

Network & routing

Network type
Unknown — no DoD/DISA operator-official statement found describing AS767's network type or purpose; third-party (non-operator) BGP data show near-zero current announcements, consistent with a largely dormant/reserved DoD-block ASN [Unknown] — https://bgp.he.net/AS767
Size
dormant — 0 IPv4 prefixes / 0 addresses and 0 IPv6 prefixes per RIPEstat and bgp.tools; bgp.he.net shows 2 IPv4 prefixes at time of check (unresolved conflict); customer cone = 1 ASN (itself), 0 prefixes, 0 addresses
[Likely] — https://stat.ripe.net/AS767, https://asrank.caida.org/asns/767, https://bgp.tools/as/767, https://bgp.he.net/AS767
Routing/peering
not currently announced; CAIDA shows zero BGP degree (0 customers/peers/providers, unseen in topology); RIPEstat shows 1 observed neighbour; third-party collectors note a single relationship with AS7767 (Encyclopaedia Britannica, unrelated organization) — bgp.tools frames it as upstream, bgp.he.net frames it as a peer (disputed)
[Likely] — https://asrank.caida.org/asns/767, https://stat.ripe.net/AS767, https://bgp.tools/as/767, https://bgp.he.net/AS767
RPKI
not assessable — AS767 announces no prefixes currently, so RPKI validity (evaluated per-prefix) cannot be checked [Unknown]
Notable usage
Unknown — no DoD/DISA page found describing a specific purpose for AS767; only historically observed announcement is 192.84.125.0/24 (2000-08-18 to 2001-10-22), long stale [Unknown, with historical route Confirmed] — https://stat.ripe.net/AS767
Related ASNs
AS7767 (Encyclopaedia Britannica) — observed relationship of disputed type, unrelated organization [Likely]; other DoD DNIC-block ASNs for context only, not evidence of AS767's own usage: AS749, AS721, AS668, AS687 [Likely] — https://bgp.tools/as/767, https://bgp.he.net/AS767, https://db-ip.com/as749, https://db-ip.com/as721-dod-network-information-center
Analyst note
AS767 is a DoD DNIC-block ASN, effectively dormant in current routing (0 prefixes per most sources) with one stale historical announcement over two decades old. No official DoD/DISA page describes its specific purpose, and official website is Unknown — a live check of disa.mil on 2026-07-31 returned anomalous, unrelated content, an inconclusive fetch rather than evidence about the real site.
[ 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.

1 observed neighbour
// Notable connectionsTop 1 of 1
ASNOperatorRole
AS7767 upstream
Neighbours observed via public BGP collectors; not a complete peering list.