l.root-servers.net
Handle
Cluster stats
Netblocks36
Cluster ID191828875
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (36)

⬇ export CSV
CIDR Org name Registry Status Confidence
27.111.229.253/32 l.root-servers.net PEERINGDB ASSIGNED ● high
45.68.72.12/32 l.root-servers.net PEERINGDB ASSIGNED ● high
45.68.80.21/32 l.root-servers.net PEERINGDB ASSIGNED ● high
45.184.144.80/32 l.root-servers.net PEERINGDB ASSIGNED ● high
45.184.146.35/32 l.root-servers.net PEERINGDB ASSIGNED ● high
91.210.16.213/32 l.root-servers.net PEERINGDB ASSIGNED ● high
177.52.38.40/32 l.root-servers.net PEERINGDB ASSIGNED ● high
185.1.27.47/32 l.root-servers.net PEERINGDB ASSIGNED ● high
187.16.195.9/32 l.root-servers.net PEERINGDB ASSIGNED ● high
187.16.196.8/32 l.root-servers.net PEERINGDB ASSIGNED ● high
187.16.216.175/32 l.root-servers.net PEERINGDB ASSIGNED ● high
195.42.144.88/32 l.root-servers.net PEERINGDB ASSIGNED ● high
196.60.86.229/32 l.root-servers.net PEERINGDB ASSIGNED ● high
196.223.21.210/32 l.root-servers.net PEERINGDB ASSIGNED ● high
200.1.6.23/32 l.root-servers.net PEERINGDB ASSIGNED ● high
200.192.108.27/32 l.root-servers.net PEERINGDB ASSIGNED ● high
200.219.139.121/32 l.root-servers.net PEERINGDB ASSIGNED ● high
200.219.141.11/32 l.root-servers.net PEERINGDB ASSIGNED ● high
200.219.144.23/32 l.root-servers.net PEERINGDB ASSIGNED ● high
200.219.145.21/32 l.root-servers.net PEERINGDB ASSIGNED ● high
206.51.40.32/32 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:504:13:1::32/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:7f8:14::26:1/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:7f8:1e::47/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:7f8:43::2:144:1/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:de8:4::2:144:1/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:12f8::175/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:12f8:0:2::21/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:12f8:0:3::121/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:12f8:0:4::35/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:12f8:0:5::11/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:12f8:0:6::2:144/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:12f8:0:8::21/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:13c7:6006::2:144:1/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:43f8:41::a502:144:1/128 l.root-servers.net PEERINGDB ASSIGNED ● high
2001:43f8:60:1::210/128 l.root-servers.net PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
94.4% of checked blocks have valid RPKI ROA coverage (34 of 36)
No discrepancies found among checked blocks.

NIC Handles

AS20144