DSB
Cluster stats
| Netblocks | 5 |
| All fragments | 30 blocks across 15 clusters |
| Cluster ID | 192071909 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 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 |
|---|---|---|---|---|
| 87.54.49.8/29 | DSB-NET | RIPE | ASSIGNED PA | ● low |
| 147.29.96.80/28 | DSB | RIPE | LEGACY | ● low |
| 147.29.97.240/28 | DSB | RIPE | LEGACY | ● low |
| 147.29.134.0/26 | DSB | RIPE | LEGACY | ● low |
| 2a00:2381:d291::/48 | DSB | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to DSB 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.
| 2a00:2381:d291::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
BTNET-MNT
CSCDK-MNT
DUMY-RIPE
DUMY-RIPE
TDK-MNT