Trifonov
TRIFONOV-AS
Data as of 2026-10-04
Registry
This organisation
| Netblocks | 2 |
| IPv6 | 1 prefix (largest 2a10:ab80:3ed::/48) |
| Also registered under this name | 3 netblocks across 2 separate records |
| Record ID | 246783365 |
| Registry | BGP |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | Registry record |
| 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 |
|---|---|---|---|---|
| 212.248.61.152/30 | Trifonov | RIPE | ASSIGNED PA | ● low |
| 2a10:ab80:3ed::/48 | TRIFONOV-AS | BGP | ANNOUNCED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a10:ab80:3ed::/48 |
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 Trifonov 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.
| 2a10:ab80:3ed::/48 /48 | authorized for AS219498 — Artem Kovalchuk |
NIC Handles
AS219498
COMSTAR-MNT
DUMY-RIPE
DUMY-RIPE
lir-ru-prefixlabs-1-MNT