Autonomous system
AS8793 THINXX
Unclassified RIPE
Summary
thinxx GmbH
hosting isp legacy
THINXX belongs to thinxx GmbH, a small telecommunications and IT-infrastructure company based in Rodgau near Offenbach, Germany, running its systems out of a Frankfurt data centre. It sells networks, IT infrastructure and VoIP as packaged services to business customers.
What it's used for
The AS announces roughly 2,000 IPv4 addresses across five prefixes plus one IPv6 prefix. The sampled reverse DNS is entirely first-party operator infrastructure:
core11.f.ip.thinxx.net— a core router, thefalmost certainly for Frankfurtns1.thinxx.net,ns2.thinxx.de— the company's own nameservers
There is no subscriber-pool naming anywhere in the sample: no dsl-, pppoe-, dyn or pool labels. What shows up instead is provider infrastructure and hosted customer systems, which fits a B2B connectivity and hosting shop rather than a consumer ISP.
Notable
- 30 observed BGP neighbours against only ~2,000 addresses. That ratio means the network is far better connected than its address count suggests, which is normal for a Frankfurt-based operator sitting on a well-populated exchange.
- One sampled address in
193.109.222.0/24resolves tomatrix.metalab.de— a hosted third-party service, evidence that the space carries customer workloads. - The address footprint is a patchwork of small blocks (
185.58.0.0/22,193.168.6.0/23, single /24s) accumulated over time, which is typical for a long-lived small German LIR.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Address space
Summary
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 21 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS8793- Registry name
- THINXX
- Registrant
- Thinxx GmbH
- Abuse contact
- noc@thinxx.de
- Registered
- 2011-11-09
- Last changed
- 2026-06-26
- Status
- active
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
No IC3 indicators Nothing from the FBI IC3 feed.
Threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere