Leendert van Hoorn

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks2
IPv6 2 prefixes (largest 2a06:9801:f7f::/48)
Also registered under this name 4 netblocks across 2 separate records
Record ID239182484
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (2)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a06:9801:f7f::/48 Leendert van Hoorn RIPE ASSIGNED ● high
2a06:9801:fca::/48 Leendert van Hoorn RIPE ASSIGNED ● high

IPv6 ranges (2)

Network trust

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

These blocks are registered to Leendert van Hoorn 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.

2a06:9801:f7f::/48 /48 authorized for AS218882 — LAGRANGE-AUTO-MNT
2a06:9801:fca::/48 /48 authorized for AS218882 — LAGRANGE-AUTO-MNT

NIC Handles

DUMY-RIPE DUMY-RIPE LAGRANGE-AUTO-MNT LSRA2-RIPE ORG-LVH2-RIPE