DOT.Comm

Data as of 2026-09-06
Registry
This organisation
Netblocks7 · 1,025 IPv4 addresses
IPv6 2 prefixes (largest 2602:81b:e000::/40)
Record ID239779858
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 12 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
192.234.159.0/24 DOT.Comm BGP ANNOUNCED ● high
192.234.160.0/24 DOT.Comm BGP ANNOUNCED ● high
192.234.161.0/24 DOT.Comm BGP ANNOUNCED ● high
192.234.162.0/24 DOT.Comm BGP ANNOUNCED ● high
206.126.235.51/32 DOT.Comm PEERINGDB ASSIGNED ● high
2001:504:33::45/128 DOT.Comm PEERINGDB ASSIGNED ● high
2602:81b:e000::/40 DOT.Comm ARIN DIRECT ALLOCATION ● high

IPv6 ranges (2)

Footprint over time

11 weekly snapshots · JSON
12 +5 netblocks since 2026-07-05
2026-07-05 peak 12 2026-09-06

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (10 of 12)
No discrepancies found among checked blocks.

NIC Handles

AS40716 AS40716 DOTC-1 JMH33-ARIN JMH33-ARIN JMH33-ARIN JMH33-ARIN JMH33-ARIN NORDB-ARIN NORDB-ARIN NORDB-ARIN NORDB-ARIN