Rexton-Proxy
Data as of 2026-09-27
BGP inherited
This organisation
| Netblocks | 5 · 2,048 IPv4 addresses |
| Record ID | 247193921 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2.56.32.0/23 | Rexton-Proxy | RIPE | ASSIGNED PA | ● low |
| 5.253.186.0/24 | Rexton-Proxy | RIPE | ASSIGNED PA | ● low |
| 88.214.0.0/23 | REXTON-PROXY | RIPE | ASSIGNED PA | ● low |
| 88.214.2.0/23 | REXTON-PROXY | RIPE | ASSIGNED PA | ● low |
| 185.219.162.0/24 | Rexton-Proxy | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
60.0%
of checked blocks have valid RPKI ROA coverage
(3 of 5)
Possible discrepancies (1)
These blocks are registered to Rexton-Proxy 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.
| 2.56.32.0/23 /23 | authorized for AS1239 — Cogent Communications, LLC |
NIC Handles
DUMY-RIPE
DUMY-RIPE
mnt-us-rexton-1