Sucuri
waf-jp-tokyo
Data as of 2026-10-18
Registry
Limited data: only 2 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.
This organisation
| Netblocks | 2 · 256 IPv4 addresses |
| IPv6 | 1 prefix (largest 2a02:fe80:16::/48) |
| Record ID | 252630598 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | Registry record |
| 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 · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.93.228.0/24 | waf-jp-tokyo | RIPE | ASSIGNED PA | ● low |
| 2a02:fe80:16::/48 | waf-jp-tokyo | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a02:fe80:16::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (2)
These blocks are registered to waf-jp-tokyo but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a02:fe80:16::/48 /48 | authorized for AS30148 — Sucuri |
| 185.93.228.0/24 /24 | authorized for AS14618 — Amazon.com, Inc. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
sucurisoc