AF BENELUX BV
AF_BENELUX_BV
Registry
Cluster stats
Netblocks6
All fragments 7 blocks across 2 clusters
Cluster ID193804853
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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

Footprint over time

2 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-06

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
213.125.9.200/29 AF_BENELUX_BV RIPE ASSIGNED PA ● low
213.125.180.56/29 AF_BENELUX_BV RIPE ASSIGNED PA ● low
213.125.217.144/29 AF_BENELUX_BV RIPE ASSIGNED PA ● low
2001:41f0:27d3::/48 AF_BENELUX_BV RIPE ASSIGNED ● low
2001:41f0:3423::/48 AF_BENELUX_BV RIPE ASSIGNED ● low
2001:41f0:8108::/48 AF_BENELUX_BV RIPE ASSIGNED ● low

Network trust

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

These blocks are registered to AF BENELUX BV 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.

2001:41f0:3423::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.
2001:41f0:8108::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.
2001:41f0:27d3::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.

NIC Handles

DUMY-RIPE DUMY-RIPE ZIGGO-AUTOREG1