NO-NTFK

BGP inherited
Cluster stats
Netblocks7 · 630 IPv4 addresses
Cluster ID209023097
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.151.246.0/23 NO-NTFK RIPE ASSIGNED PA ● low
217.168.83.40/29 NO-NTFK RIPE ASSIGNED PA ● low
217.168.83.112/30 NO-NTFK RIPE ASSIGNED PA ● low
217.168.83.128/27 NO-NTFK RIPE ASSIGNED PA ● low
217.168.88.0/26 NO-NTFK RIPE ASSIGNED PA ● low
217.168.94.0/28 NO-NTFK RIPE ASSIGNED PA ● low
2a01:560:301::/48 NO-NTFK RIPE ASSIGNED ● low

Network trust

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

These blocks are registered to NO-NTFK 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:560:301::/48 /48 authorized for AS34087 — NTE TELEKOM AS
89.151.246.0/23 /23 authorized for AS34087 — NTE TELEKOM AS

NIC Handles

DUMY-RIPE DUMY-RIPE NTE-MNT