SNI
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 105 blocks across 17 clusters |
| Cluster ID | 192904088 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 101.203.104.13/32 | SNI | PEERINGDB | ASSIGNED | ● high |
| 210.173.176.36/32 | SNI | PEERINGDB | ASSIGNED | ● high |
| 210.173.188.9/32 | SNI | PEERINGDB | ASSIGNED | ● high |
| 218.100.9.116/32 | SNI | PEERINGDB | ASSIGNED | ● high |
| 195.41.66.0/24 | SNI-NET | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(4 of 5)
Possible discrepancies (1)
These blocks are registered to SNI 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.
| 195.41.66.0/24 /24 | authorized for AS3292 — TDC Holding A/S |
NIC Handles
AS18150
AS3292-MNT
DUMY-RIPE
DUMY-RIPE