Dmitrii Pimkin
Data as of 2026-09-06
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.
This organisation
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2a06:9801:1520::/44) |
| Record ID | 239187998 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 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 |
|---|---|---|---|---|
| 2a06:9801:fc3::/48 | Dmitrii Pimkin | RIPE | ASSIGNED | ● high |
| 2a06:9801:1520::/44 | Dmitrii Pimkin | RIPE | ASSIGNED | ● high |
IPv6 ranges (2)
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 Dmitrii Pimkin 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.
| 2a06:9801:1520::/44 /44 | authorized for AS218830 — LAGRANGE-AUTO-MNT |
| 2a06:9801:fc3::/48 /48 | authorized for AS218830 — LAGRANGE-AUTO-MNT |
NIC Handles
DUMY-RIPE
DUMY-RIPE
LAGRANGE-AUTO-MNT
LSRA2-RIPE
ORG-DP216-RIPE