Autonomous system
AS8274 ONLNK
Unclassified RIPE
Summary
ONLNK (Maksym Naumenko)
legacy unclassified
ONLNK is registered not to a company but to an individual, Maksym Naumenko, with a RIPE address in Khartsyzsk in the occupied Donetsk region. It announces roughly 768 addresses and takes transit from a single upstream, itself an AS held by another private individual.
What it's used for
- Unknown. There is no reverse DNS at all on any sampled address, no website, no downstreams and no service the AS visibly presents.
- Its main block,
91.203.232.0/23, carries the netnameONLNKbut is registered to a different individual in Saratov, Russia, sponsored by a Seychelles LIR. The AS holder appears as the admin and technical contact on that third-party assignment. The remaining /24 is Moscow provider-aggregatable space under yet another maintainer.
Notable
- Left unclassified, and the address space should not be geolocated to the holder. The pattern here is the familiar address-leasing shape in miniature: an individual holding an AS, prefixes registered to nominally unrelated parties who share the same contact handle, an offshore sponsoring LIR, and no reverse DNS to say what anything is actually for.
- Shared admin and technical contacts across "different" registrants is the tell that matters. Different names on the
org:line do not mean different operators. - The number itself is a low legacy allocation that ended up in modern hands; it carries no early-internet pedigree worth reading into.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS56766 | Bahilov Ilya Vitalievich PE | 184 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-21, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 512 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS8274- Registry name
- ONLNK
- Registrant
- ONLNK-MNT
- Abuse contact
- maksim1975@gmail.com
- Registered
- 2015-10-21
- Last changed
- 2026-05-22
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 75% valid · 3 valid, 1 with no ROA
- ROAs
- 5 authorising AS8274
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 4 naming AS8274
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,779 prefixes, as published 2026-10-22. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere