IFOP

BGP inherited
Cluster stats
Netblocks8
Cluster ID208850958
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name 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
84.96.13.84/30 IFOP RIPE ASSIGNED PA ● low
84.96.13.96/27 IFOP RIPE ASSIGNED PA ● low
86.66.23.160/27 IFOP RIPE ASSIGNED PA ● low
93.17.47.200/29 IFOP RIPE ASSIGNED PA ● low
194.183.212.52/30 IFOP RIPE ASSIGNED PA ● low
194.183.212.188/30 IFOP RIPE ASSIGNED PA ● low
194.183.213.15/32 IFOP RIPE ASSIGNED PA ● low
194.183.213.16/32 IFOP RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT SIRIS-MNT