IP-Max SA
HORNETSECURITY-IPv6NET
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 3 blocks across 2 clusters |
| Cluster ID | 206113113 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 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 |
|---|---|---|---|---|
| 2a01:6780:7::/48 | HORNETSECURITY-IPv6NET | RIPE | ASSIGNED | ● low |
| 2a01:6780:12::/48 | HORNETSECURITY-IPv6NET | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “HORNETSECURITY IPv6NET” — 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.
- HORNETSECURITY-IPv6NET-HZ1b 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.
- Ipv6Net via GHOSTnet GmbH sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
RPKI-inferred operator
IP-Max SA
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
ANTISPAMEUROPE-MNT
DUMY-RIPE
DUMY-RIPE
HORNETSECURITY-EU-MNT
HORNETSECURITY-US-MNT