asn.dev

Autonomous system

AS207165 OOO5COM

Unclassified RIPE

IPv4 addresses 2.30K 2 prefixes
IPv6 prefixes 0 counted as prefixes, not addresses
Countries 1 mostly RU
Exchanges 0 recorded by PCH
Upstreams 1 0 downstream
Flagged prefixes 0 none

Summary

OOO 05COM

Russian Federation · AI-generated

business russia ipv4

The AS handle OOO5COM is held by OOO 05COM.

What it's used for

  • The address space carries corporate infrastructure, indicated by the netnames OOO05COM and ORG-FIVE2-RIPE associated with the announced prefixes.
  • The network announces 2304 IPv4 addresses across 2 prefixes and maintains 1 observed neighbour, a ratio consistent with a small-scale business or internal corporate estate rather than a transit or large access provider.

Notable

  • Registrants for both announced prefixes align with the AS holder, listing OOO 05COM and CoProSys RIPE Admins for the larger block.
  • The inventory consists of two distinct IPv4 blocks: 5.59.24.0/21 and 83.242.110.0/24, with no IPv6 prefixes announced.

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

Full topology · Graph

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.

ASNetworkPaths seen
AS56634Fly-Tech Ltd.124

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-30, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 2 prefixes · 2.30K addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation2

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS207165
Registry name
OOO5COM
Registrant
COPROSYS-MNT
Abuse contact
sasha-dag@yandex.ru
Registered
2016-08-19
Last changed
2022-11-02
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
0% valid · 0 valid, 2 with no ROA
ROAs
0 authorising AS207165
ASPA
no ASPA record
IRR
100% registered · 2 of 2 announcements
Route objects
10 naming AS207165

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: 447 networks and 1,848 prefixes, as published 2026-10-31. 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

Cross-check