NCL-TRUST
Unresolved
Cluster stats
| Netblocks | 3 |
| All fragments | 45 blocks across 10 clusters |
| Cluster ID | 192849128 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.63.72.16/28 | NCL-TRUST | RIPE | ASSIGNED PA | ● low |
| 195.195.18.0/24 | NCL-TRUST | RIPE | ASSIGNED PA | ● low |
| 2001:630:6e::/48 | NCL-TRUST | RIPE | ASSIGNED | ● low |
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 (2)
These blocks are registered to NCL-TRUST 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.
| 2001:630:6e::/48 /48 | authorized for AS786 — Jisc Services Limited |
| 195.195.18.0/24 /24 | authorized for AS786 — Jisc Services Limited |
NIC Handles
DUMY-RIPE
DUMY-RIPE
JANET-HOSTMASTER