Abuse contact role object

Data as of 2026-10-18
BGP inherited
Limited data: only 3 ranges 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
Netblocks3 · 512 IPv4 addresses
IPv6 1 prefix (largest 2a0f:6280:61a1::/48)
Record ID250709996
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 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 (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.141.34.0/24 Abuse contact role object BGP ANNOUNCED ● high
185.254.239.0/24 Abuse contact role object BGP ANNOUNCED ● high
2a0f:6280:61a1::/48 Abuse contact role object BGP ANNOUNCED ● low

IPv6 ranges (1)

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 (3 of 3)
Possible discrepancies (3)

These blocks are registered to Abuse contact role object but cryptographically authorized for a different, unrelated network (2 distinct holders) — 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
185.141.34.0/24 /24 authorized for AS43260 — DGN TEKNOLOJI A.S.
185.254.239.0/24 /24 authorized for AS43260 — DGN TEKNOLOJI A.S.

NIC Handles

AS218450 AS219268 AS43260 DGN-MNT HYEHOST-MNT LocalNCC-mnt RGT