Richard Franks
Data as of 2026-07-26
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.
Cluster stats
| Netblocks | 3 |
| IPv6 | 3 prefixes (largest 2001:678:1028::/48) |
| Cluster ID | 214593938 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0a:6044:a1ff::31/128 | richard-franks | PEERINGDB | ASSIGNED | ● high |
| 2001:678:1028::/48 | Richard Franks | RIPE | ASSIGNED PI | ● low |
| 2a11:f2c0:ffce::/48 | Richard Franks | RIPE | ALLOCATED-BY-LIR | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
No discrepancies found among checked blocks.
NIC Handles
AS207960-MNT
AS207960-RF-1-MNT
AS215499
DUMY-RIPE
DUMY-RIPE
ORG-RF106-RIPE
RIPE-NCC-END-MNT