EKCO CLOUD AND SECURITY LIMITED

GLEIF verified
Complete entity footprint
3 linked clusters · 16 netblocks · 13,815 IPv4 addresses
This organisation's clusters combined by evidence — shared GLEIF corporate family — not name similarity, so genuinely different organisations that share a name are excluded.
View the full entity page →
LEI
9845007AK8542BHC0385
Registered name
EKCO CLOUD AND SECURITY LIMITED
Jurisdiction
Ultimate parent
PLUTUS TOPCO LIMITED
98450049PB555AA08C65
Cluster stats
Netblocks8 · 4,093 IPv4 addresses
All fragments 9 blocks across 2 clusters
Cluster ID208786068
RegistryBGP
Owner jurisdictionGB
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 9845007AK8542BHC0385
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.43.40.0/22 EKCO CLOUD AND SECURITY LIMITED BGP ANNOUNCED ● high
2a01:6ae0::/29 EKCO CLOUD AND SECURITY LIMITED BGP ANNOUNCED ● high
185.43.40.0/22 EKCO CLOUD AND SECURITY LIMITED RIPE ALLOCATED PA ● low
185.43.216.0/22 EKCO CLOUD AND SECURITY LIMITED RIPE ALLOCATED PA ● low
185.98.148.0/22 EKCO CLOUD AND SECURITY LIMITED RIPE ALLOCATED PA ● low
213.161.94.236/31 Net-Ekco-Cloud-and-Security-Limited RIPE ASSIGNED PA ● low
2a01:6ae0::/29 EKCO CLOUD AND SECURITY LIMITED RIPE ALLOCATED-BY-RIR ● low
2a04:9700::/29 EKCO CLOUD AND SECURITY LIMITED RIPE ALLOCATED-BY-RIR ● low

Corporate group (3 confirmed entities)

+3 additional unconfirmed candidates not shown — full list (JSON)

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “EKCO CLOUD AND SECURITY” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: F how networks compare →
12.5% of checked blocks have valid RPKI ROA coverage (1 of 8)
No discrepancies found among checked blocks.

NIC Handles

ABOVENET-MNT AS62227 CLOUDHELIX-MNT CLOUDHELIX-MNT DUMY-RIPE DUMY-RIPE ORG-CL249-RIPE RIPE-NCC-HM-MNT