KH0001
Cluster stats
Netblocks13
Cluster ID192619178
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.132.4.224/27 KH0001 RIPE ASSIGNED PA ● low
37.9.56.96/30 KH0001 RIPE ASSIGNED PA ● low
37.9.57.64/30 KH0001 RIPE ASSIGNED PA ● low
77.74.194.192/26 KH0001 RIPE ASSIGNED PA ● low
77.75.122.136/30 KH0001 RIPE ASSIGNED PA ● low
78.110.160.28/30 KH0001 RIPE ASSIGNED PA ● low
78.110.169.88/29 KH0001 RIPE ASSIGNED PA ● low
81.92.193.128/26 KH0001 RIPE ASSIGNED PA ● low
178.159.1.64/26 KH0001 RIPE ASSIGNED PA ● low
178.159.1.128/26 KH0001 RIPE ASSIGNED PA ● low
178.159.11.160/30 KH0001 RIPE ASSIGNED PA ● low
178.159.14.64/30 KH0001 RIPE ASSIGNED PA ● low
2a01:a500:2348::/48 KH0001 RIPE AGGREGATED-BY-LIR ● low

Network trust

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

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

2a01:a500:2348::/48 /48 authorized for AS42831 — UK Dedicated Servers Limited

NIC Handles

DUMY-RIPE DUMY-RIPE UKSERVERS-MNT