AS273953
Handle
Cluster stats
| Netblocks | 7 |
| Cluster ID | 204726307 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 38.10.240.0/22 | AS273953 | BGP | ANNOUNCED | ● high |
| 38.199.65.0/24 | AS273953 | BGP | ANNOUNCED | ● high |
| 38.199.66.0/24 | AS273953 | BGP | ANNOUNCED | ● high |
| 38.199.67.0/24 | AS273953 | BGP | ANNOUNCED | ● high |
| 131.72.138.0/24 | AS273953 | BGP | ANNOUNCED | ● high |
| 187.102.194.0/24 | AS273953 | BGP | ANNOUNCED | ● high |
| 2803:df50::/32 | AS273953 | BGP | ANNOUNCED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
85.7%
of checked blocks have valid RPKI ROA coverage
(6 of 7)
Possible discrepancies (2)
These blocks are registered to AS273953 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.
| 2803:df50::/32 /32 | authorized for AS264827 — AS264827 |
| 187.102.194.0/24 /24 | authorized for AS264827 — AS264827 |
NIC Handles
AS273953