TBSH-CLIENT-DATAGUARD-SECURITY
Data as of 2026-09-13
BGP inherited
This organisation
| Netblocks | 2 |
| IPv6 | 1 prefix (largest 2a00:1430:1106::/48) |
| Also registered under this name | 3 netblocks across 2 separate records |
| Record ID | 242779862 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 213.129.68.48/28 | TBSH-CLIENT-DATAGUARD-SECURITY | RIPE | ASSIGNED PA | ● low |
| 2a00:1430:1106::/48 | TBSH-CLIENT-DATAGUARD-SECURITY | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a00:1430:1106::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to TBSH-CLIENT-DATAGUARD-SECURITY 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:1430:1106::/48 /48 | authorized for AS24958 — CYBERFORT LIMITED |
NIC Handles
BUNKER-MNT
DUMY-RIPE
DUMY-RIPE