Securebit AG
AF-SECUREBIT-20201212
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 5 blocks across 4 clusters |
| Cluster ID | 206138592 |
| Registry | RIPE |
| Customers | find customers using 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 | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a09:4c0:120a::/48 | AF-SECUREBIT-20201212 | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a09:4c0:12e0::/44 | AF-SECUREBIT-20201212 | RIPE | ALLOCATED-BY-LIR | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “AF SECUREBIT” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- AF-SECUREBIT-20200202 1 blocks
- AF-SECUREBIT-20201111 1 blocks
- AF-SECUREBIT-20210101 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- Securebit 20200202 via Securebit AG sub-allocation
- Securebit 20200202 via Securebit AG sub-allocation
- Securebit 20200202 via Securebit AG sub-allocation
- Securebit 20200202 via Securebit AG sub-allocation
- Securebit 20200202 via Securebit AG sub-allocation
- Securebit 20200202 via Securebit AG sub-allocation
- Securebit 20200202 via Securebit AG sub-allocation
- Securebit 20200202 via Securebit AG sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
SBMT