Threatoff

Data as of 2026-08-30
Registry
Cluster stats
Netblocks4,048 · 4,045 IPv4 addresses
IPv6 3 prefixes (largest 2a14:7c0:1000::/48)
Cluster ID231543216
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

10 weekly snapshots · JSON
4,048 +546 netblocks since 2026-07-05
2026-07-05 peak 4,048 2026-08-30

IP Ranges (4,048)

showing 50 of 4,048 — see all⬇ export CSV (free export limited to 500 rows — subscribe for the full export)
CIDR Org name Registry Status Confidence
5.231.117.0/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.1/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.2/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.3/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.4/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.5/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.6/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.7/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.8/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.9/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.10/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.11/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.12/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.13/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.14/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.15/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.16/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.17/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.18/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.19/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.20/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.21/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.22/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.23/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.24/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.25/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.26/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.27/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.28/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.29/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.30/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.31/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.32/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.33/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.34/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.35/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.36/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.37/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.38/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.39/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.40/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.41/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.42/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.43/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.44/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.45/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.46/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.47/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.48/32 Threatoff RIPE ASSIGNED PA ● high
5.231.117.49/32 Threatoff RIPE ASSIGNED PA ● high

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (2,000 of 2,000, sampled from 4,048)
Possible discrepancies (3)

These blocks are registered to Threatoff but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a14:7c0:1009::/48 /48 authorized for AS215365 — Tom Gewiese
2a14:7c0:1000::/48 /48 authorized for AS215365 — Tom Gewiese
2a14:7c0:1001::/48 /48 authorized for AS215365 — Tom Gewiese

NIC Handles

DUMY-RIPE DUMY-RIPE ETG-MNT GHOSTNET-MNT ORG-DA1474-RIPE ORG-TA1862-RIPE