NFX, z.s.p.o
Cluster stats
Netblocks10
Cluster ID192323668
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.201.48.160/27 NFX, z.s.p.o RIPE ASSIGNED PA ● high
81.201.48.192/26 NFX, z.s.p.o RIPE ASSIGNED PA ● high
81.201.60.32 – 81.201.60.127 NFX, z.s.p.o RIPE ASSIGNED PA ● high
91.210.16.73/32 NFX, z.s.p.o. (FreeTel, s.r.o.) PEERINGDB ASSIGNED ● high
91.210.16.74/32 NFX, z.s.p.o. (FreeTel, s.r.o.) PEERINGDB ASSIGNED ● high
2001:7f8:14::12:1/128 NFX, z.s.p.o. (FreeTel, s.r.o.) PEERINGDB ASSIGNED ● high
2001:7f8:14::12:2/128 NFX, z.s.p.o. (FreeTel, s.r.o.) PEERINGDB ASSIGNED ● high
2a01:490:0:1::/64 NFX, z.s.p.o RIPE ASSIGNED ● high
2a01:490:0:2::/64 NFX, z.s.p.o RIPE ASSIGNED ● high
2a01:490:a::/48 NFX, z.s.p.o RIPE ASSIGNED ● high

Network trust

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

These blocks are registered to NFX, z.s.p.o 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.

2a01:490:a::/48 /48 authorized for AS8251 — FreeTel, s.r.o.

NIC Handles

AS8251 CZNFX-MNT DUMY-RIPE DUMY-RIPE ORG-NFX2-RIPE