Autonomous system
AS13296 INNOR-AS INNOR Ltd.
Unclassified RIPE
Summary
INNOR
isp telecom business
One netname is a registry object handle; the other three are a lowercase city name.
What it's used for
- A Russian regional access network. 2,304 addresses across four IPv4 prefixes, two observed BGP neighbours, and no IPv6 announced.
Notable
91.203.236.0/22carries the netnameORG-IL686-RIPE, which is a registry organisation identifier rather than a name.- The other three blocks are all netname
impuls-perm-ru, in lower case, registered to a different company. - Sampled names take the form
77.236.78.128.innor.ru, the four octets written forward. - First observed in the routing archive in May 2008.
Interesting
- A netname that is an internal database handle is the registry describing itself. Somebody filled the name field with the identifier of the organisation object rather than with a name, and the result identifies the record instead of the network. This happens often enough in this range to count as a pattern rather than a slip.
- The lowercase netname reads like a hostname: a company, a city and a country code joined by hyphens. Netnames are conventionally shouted in capitals, so this one was written by someone thinking in domain names.
- Three quarters of the announced space is registered to a company other than the one holding the AS, and the reverse names on those same blocks belong to the AS holder. Registration and operation part ways here, and the DNS is the side that reflects who runs it.
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.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-31, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 4 prefixes · 2.30K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 4 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS13296- Registry name
- INNOR-AS
- Registrant
- MNT-INNOR
- Abuse contact
- support@innor.ru
- Registered
- 2008-05-19
- Last changed
- 2022-03-23
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 9 with no ROA
- ROAs
- 0 authorising AS13296
- ASPA
- no ASPA record
- IRR
- 100% registered · 9 of 9 announcements
- Route objects
- 9 naming AS13296
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,843 prefixes, as published 2026-11-01. 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