RIPE NCC Authoritative DNS
BGP inherited
Cluster stats
| Netblocks | 67 |
| All fragments | 261 blocks across 9 clusters |
| Cluster ID | 193381913 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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
67
0 netblocks since 2026-07-05
2026-07-05
peak 67
2026-07-06
IP Ranges (67)
showing 50 of 67 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.57.80.9/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 37.49.232.162/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 37.49.236.176/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 43.254.83.1/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 45.68.88.12/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 45.68.89.13/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 45.170.101.15/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 77.95.71.120/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 80.249.209.132/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 86.104.125.193/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 91.213.236.18/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 91.218.7.103/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 103.101.136.58/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 103.142.153.16/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 103.158.187.163/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 123.108.11.185/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 185.1.43.43/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 185.1.110.87/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 185.1.133.63/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 185.1.144.19/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 185.1.225.55/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 193.201.28.30/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 193.239.116.223/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 194.42.47.17/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 194.68.123.174/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 195.66.225.160/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 195.66.237.160/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 195.130.211.36/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 196.60.9.32/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 196.60.97.119/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 200.23.206.188/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 202.249.2.197/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 203.159.68.33/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 210.173.177.125/32 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:200:0:fe00:0:3:188:1/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1:0:a500:19:7000:1/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::3:188:1/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4:1:0:3:188:1/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:ff::174/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:10::19:7000/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:11::43/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a519:7000:1/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:17::3:188:1/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:47:47::120/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:48::36/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::176/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54:5::162/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54:7::18/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54:8::19/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:64:225:0:19:7000:1/128 | RIPE NCC Authoritative DNS | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.6%
of checked blocks have valid RPKI ROA coverage
(54 of 67)
No discrepancies found among checked blocks.
NIC Handles
AS197000