Skip to content
iplogs.com

AS199118 Heinlein-Support GmbH

Content host · based in Germany · IPLogs default verdict: Content network

Content hostlive registry dataCSV
ASN
AS199118
Name
Heinlein-Support GmbH
Category
Content host
Country
Germany
IPLogs verdict
Content network
Registry
RIPE NCC
Allocated
2012-08-15
PeeringDB
Yes · 2 fac.
Proxy backbone
No

About Heinlein-Support GmbH

Heinlein-Support GmbH (AS199118) is registered with RIPE NCC in Germany and was allocated on 2012-08-15. A content / hosting network. IPLogs raises asn_peeringdb_content_host at a low weight — mildly elevated, not a hard VPN signal on its own. PeeringDB lists it in 2 facilities.

How IPLogs classifies AS199118

When the detection engine sees an IP that routes through AS199118, it checks three lists: (1) the curated VPN-provider ASN list, (2) the datacenter / hosting ASN list, and (3) the trusted CDN allowlist. Matches produce one of vpn_asn, dc_ip, or no flag respectively. Keywords in the org name (e.g. "vpn", "proxy", "anonym") may also trigger vpn_org_keyword even for unknown ASNs.

Use the ASN as a shortcut when you want to block a whole hosting provider at the edge rather than maintaining a per-IP list.

Authoritative sources for AS199118

Third-party registries where you can verify the announcements, peer relationships, and WHOIS registration for this ASN.

Related ASNs

Other datacenter ASNs in Germany catalogued by IPLogs.

Frequently asked questions about AS199118

+Is AS199118 (Heinlein-Support GmbH) a VPN, datacenter, or residential network?

IPLogs classifies Heinlein-Support GmbH (AS199118) as a datacenter / hosting network based in Germany. The default verdict for any IP that routes through this ASN is "Content network".

+Who operates AS199118 and where is it registered?

Heinlein-Support GmbH (AS199118) is registered with RIPE NCC, operates in Germany, was allocated on 2012-08-15. It is listed in PeeringDB across 2 facilities.

+How do I check or block AS199118 traffic?

Send any suspect IP to the IPLogs API — POST https://iplogs.com/v1/check with body {"ip":"<ip>"} — and the response reports the originating ASN plus whether it matched the VPN, datacenter, or CDN lists. To block a whole hosting network at the edge, filter on AS199118 instead of maintaining a per-IP list. Copy-paste recipes for Cloudflare WAF, Nginx, and Stripe Radar are at /guides/block-vpn-traffic.

Related pages