HENKEL
Cluster stats
Netblocks11
All fragments 184 blocks across 40 clusters
Cluster ID191930877
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 13 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
222.66.199.40/30 HENKEL-CO APNIC ASSIGNED NON-PORTABLE ● high
31.169.25.204/30 HENKEL RIPE ASSIGNED PA ● low
77.46.144.176/30 HENKEL RIPE ASSIGNED PA ● low
77.46.144.189/32 HENKEL-NET RIPE ASSIGNED PA ● low
88.204.136.8/29 HENKEL RIPE ASSIGNED PA ● low
89.111.249.152/29 HENKEL-NET RIPE ASSIGNED PA ● low
178.183.3.8/30 HENKEL RIPE ASSIGNED PA ● low
195.117.233.24/29 HENKEL RIPE ASSIGNED PA ● low
212.98.220.128/28 HENKEL-NET RIPE ASSIGNED PA ● low
2a00:2381:8f4::/48 HENKEL-LTD RIPE AGGREGATED-BY-LIR ● low
2a01:1111:3::/48 HENKEL RIPE ASSIGNED ● low

Network trust

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

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

2a00:2381:8f4::/48 /48 authorized for AS2856 — British Telecommunications PLC

NIC Handles

AS12912-AUX-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE KNIC-MNT MAINT-CHINANET-SH MNT-BORUSAN TELEKOM-MNT TELEKOM-SRPSKE-MNT TPNET Telekom-mnt WJ850-AP +1 more