ENMOE LTD

BGP inherited
Cluster stats
Netblocks6
All fragments 8 blocks across 3 clusters
Cluster ID211534888
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:7f8:33::a113:9249:1/128 ENMOE LTD PEERINGDB ASSIGNED ● high
2406:840:fe71::/48 ENMOE-NET APNIC ASSIGNED NON-PORTABLE ● high
2406:840:fe72::/48 ENMOE-NET APNIC ASSIGNED NON-PORTABLE ● high
2a0e:8f01:1000:22::126/128 ENMOE LTD PEERINGDB ASSIGNED ● high
2a0e:b107:1f1::/48 ENMOE BGP ANNOUNCED ● high
2a0e:aa07:f050::/44 ENMOE-AS RIPE ALLOCATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ENMOE” — 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: D how networks compare →
33.3% of checked blocks have valid RPKI ROA coverage (2 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS139249 AS139249 DUMY-RIPE DUMY-RIPE KIRINO-MNT MAINT-AS138632 MAINT-NBDHM-CN ORG-EA1244-RIPE WL3086-AP WL3086-AP