FINECOM
Cluster stats
Netblocks11
All fragments 13 blocks across 3 clusters
Cluster ID192275447
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
95.174.224.240/29 FINECOM RIPE ASSIGNED PA ● low
212.60.46.0/24 FINECOM RIPE ASSIGNED PA ● low
212.60.47.48/29 FINECOM-NET RIPE ASSIGNED PA ● low
212.60.47.56/29 FINECOM-NET RIPE ASSIGNED PA ● low
212.60.47.88/29 FINECOM RIPE ASSIGNED PA ● low
212.60.62.132/30 FINECOM RIPE ASSIGNED PA ● low
212.60.62.180/30 FINECOM RIPE ASSIGNED PA ● low
212.60.62.212/30 FINECOM RIPE ASSIGNED PA ● low
213.221.198.0/28 FINECOM RIPE ASSIGNED PA ● low
213.221.198.16/28 FINECOM RIPE ASSIGNED PA ● low
213.221.198.96/28 FINECOM RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
Possible discrepancies (1)

These blocks are registered to FINECOM 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.

212.60.46.0/24 /24 authorized for AS15600 — Quickline AG

NIC Handles

CH-LAN-MNT DUMY-RIPE DUMY-RIPE