TDB
Cluster stats
Netblocks15
All fragments 17 blocks across 3 clusters
Cluster ID191683822
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (15)

⬇ export CSV
CIDR Org name Registry Status Confidence
46.129.142.224/30 TDB RIPE ASSIGNED PA ● low
83.167.217.48/30 TDB RIPE ASSIGNED PA ● low
83.167.217.52/30 TDB RIPE ASSIGNED PA ● low
85.146.234.212/30 TDB RIPE ASSIGNED PA ● low
85.146.238.120/32 TDB RIPE ASSIGNED PA ● low
85.146.238.121/32 TDB RIPE ASSIGNED PA ● low
85.146.238.122/32 TDB RIPE ASSIGNED PA ● low
85.146.238.123/32 TDB RIPE ASSIGNED PA ● low
93.117.204.176/29 TDB RIPE ASSIGNED PA ● low
93.117.220.56/29 TDB RIPE ASSIGNED PA ● low
93.117.234.239/32 TDB RIPE ASSIGNED PA ● low
159.100.102.246/31 TDB RIPE LEGACY ● low
195.41.132.0/24 TDB-NET RIPE ASSIGNED PA ● low
212.78.194.48/29 TDB RIPE ASSIGNED PA ● low
212.78.201.200/29 TDB RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (15 of 15)
Possible discrepancies (1)

These blocks are registered to TDB 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.

195.41.132.0/24 /24 authorized for AS3292 — TDC Holding A/S

NIC Handles

AS3292-MNT DUMY-RIPE DUMY-RIPE TNF-MNT ZIGGO-AUTOREG1