white2net Srl
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 30 · 1,034 IPv4 addresses |
| IPv6 | 16 prefixes (largest 2a12:5840::/29) |
| Registered in | Netherlands (4) · United Arab Emirates (4) · Germany (3) · Belgium (2) · France (1) · United Kingdom (1) |
| All fragments | 33 blocks across 2 clusters |
| Cluster ID | 214452575 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 13 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
32
0 netblocks since 2026-07-05
2026-07-05
peak 32
2026-07-26
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.58.161.0/24 | white2net Srl | BGP | ANNOUNCED | ● high |
| 80.81.192.190/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 80.249.213.236/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 176.105.246.0/24 | white2net Srl | BGP | ANNOUNCED | ● high |
| 179.61.174.0/24 | White2net | RIPE | ASSIGNED PA | ● high |
| 185.1.14.124/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 185.1.63.145/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 185.1.160.53/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 185.1.166.152/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 185.1.222.245/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 191.96.176.0/24 | white2net Srl | BGP | ANNOUNCED | ● high |
| 193.189.83.130/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 193.239.119.112/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 195.66.231.97/32 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::3:336:0:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1:0:a500:20:9768:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::3:3368:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a520:9768:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:33::a120:9768:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:6c::400/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b7::a520:9768:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f2:e1:0:a520:9768:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:10f::3:3368:53/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:12e::20:9768:1/128 | white2net | PEERINGDB | ASSIGNED | ● high |
| 2a12:5840:1f0::/48 | white2net Srl | BGP | ANNOUNCED | ● high |
| 2a12:5840:1f1::/48 | white2net Srl | BGP | ANNOUNCED | ● high |
| 2a12:5840:1f2::/48 | white2net Srl | BGP | ANNOUNCED | ● high |
| 2a12:5844:100::/48 | white2net Srl | BGP | ANNOUNCED | ● high |
| 2a12:5844:1212::/48 | white2net Srl | BGP | ANNOUNCED | ● high |
| 2a12:5840::/29 | white2net Srl | RIPE | ALLOCATED-BY-RIR | ● low |
IPv6 ranges (16)
showing the 15 largest allocationsNetwork trust
what's this?
RPKI hygiene: B
how networks compare →
81.2%
of checked blocks have valid RPKI ROA coverage
(26 of 32)
Possible discrepancies (1)
These blocks are registered to white2net Srl 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.
| 179.61.174.0/24 /24 | authorized for AS214326 — PERGAUD Erwan |
NIC Handles
AS209768
AS209768
DUMY-RIPE
DUMY-RIPE
ORG-WA790-RIPE
ORG-WS288-RIPE
RIPE-NCC-HM-MNT
WA2542-RIPE
lir-be-white2net-1-MNT
lir-be-white2net-1-MNT
netutils-mnt
netutils-mnt
+1 more