Mikhail Nasonov
Data as of 2026-08-23
BGP inherited
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.
Cluster stats
| Netblocks | 2 · 272 IPv4 addresses |
| Cluster ID | 227172961 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.130.199.0/24 | Mikhail Nasonov | RIPE | SUB-ALLOCATED PA | ● high |
| 148.251.63.112/28 | MIKHAIL-NASONOV | RIPE | LEGACY | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
Possible discrepancies (1)
These blocks are registered to Mikhail Nasonov 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.
| 37.130.199.0/24 /24 | authorized for AS218937 — MMN33-MNT |
NIC Handles
DUMY-RIPE
DUMY-RIPE
HOS-GUN
MMN33-MNT
ORG-MN230-RIPE