Autonomous system
AS49696 ROCT
Unclassified ARIN
Summary
ROCT GmbH
business it telecom security
ROCT is operated by ROCT GmbH.
What it's used for
- The address space carries static IP addresses, as indicated by the reverse DNS entries
0-85-94-45.static.rev.roct.deand255-85-94-45.static.rev.roct.de. - The AS announces 1024 IPv4 addresses and 1 IPv6 prefix, with only 2 observed neighbours, indicating a small-scale business or internal corporate network rather than a transit provider.
- Traffic from this AS consists of IT infrastructure, telecommunications, and network security services provided by ROCT GmbH, a company specializing in IT technology and IT security.
Notable
- The registrant
ROCT GmbHmatches the AS holder, with the netnameDE-ROCT-20190705confirming consistent ownership. - ROCT GmbH was incorporated on Feb 16, 2009, and is located in Rosenheim, Germany.
- The address inventory consists of a single IPv4 block
45.94.84.0/22and one IPv6 prefix2a0e:3040::/32, representing a compact and focused address space.
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-17, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 1.02K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS49696- Registry name
- ROCT
- Registrant
- ROCT GmbH
- Abuse contact
- abuse@roct.de
- Registered
- 2019-07-08
- Last changed
- 2023-03-02
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- ROCT
- Scope
- Regional
- Traffic ratio
- Balanced
- Peering policy
- Open
- Website
- https://www.roct.de
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS49696
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 2 naming AS49696
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,783 prefixes, as published 2026-10-17. 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