Autonomous system
AS34452 SCHECK-AS
Unclassified RIPE
Summary
Robert Scheck
individual linux hosting germany
The AS handle SCHECK-AS is held by Robert Scheck.
What it's used for
- The space carries a single IPv6 prefix,
2a09:e187::/32, with no IPv4 addresses announced. - With 1 observed neighbour and 1 announced prefix, the inventory suggests a small-scale individual or personal hosting setup rather than a commercial transit or access network.
Notable
- The registry holder and PeeringDB entry both identify the operator as Robert Scheck, a German IT specialist known for Linux and open-source work.
- The address inventory consists solely of one /32 IPv6 block, indicating a minimal footprint typical of a personal or small professional infrastructure.
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 |
|---|---|---|
| AS41051 | Openfactory GmbH | 36 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 0 prefixes · 0 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS34452- Registry name
- SCHECK-AS
- Registrant
- Robert Scheck
- Abuse contact
- abuse@robert-scheck.de
- Registered
- 2019-12-17
- Last changed
- 2026-06-23
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Robert Scheck
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- https://www.scheck.net
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 · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS34452
- ASPA
- 1 declared providers
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS34452
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: 446 networks and 1,852 prefixes, as published 2026-10-27. 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