Abuse contact role object
Data as of 2026-09-13
BGP inherited
Limited data: only 1 range found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
This organisation
| Netblocks | 1 |
| IPv6 | 1 prefix (largest 2a0f:6280:61a1::/48) |
| Record ID | 244374358 |
| Registry | BGP |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 2 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 (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0f:6280:61a1::/48 | Abuse contact role object | BGP | ANNOUNCED | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2a0f:6280:61a1::/48 |
Footprint over time
4 weekly snapshots · JSON
36
+30 netblocks since 2026-07-26
2026-07-26
peak 36
2026-09-06
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
Possible discrepancies (1)
These blocks are registered to Abuse contact role object 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.
| 2a0f:6280:61a1::/48 /48 | authorized for AS219268 — Geodema Group LLC |
NIC Handles
AS219268
HYEHOST-MNT