Skip to content
iplogs.com

AS31103 Keyweb AG

Backbone / NSP · based in Germany · IPLogs default verdict: Transit / backbone

Backbone / NSPlive registry data
ASN
AS31103
Name
Keyweb AG
Category
Backbone / NSP
Country
Germany
IPLogs verdict
Transit / backbone
Registry
RIPE NCC
Allocated
2004-02-27
PeeringDB
Yes · 3 fac.
Proxy backbone
No

About Keyweb AG

Keyweb AG (AS31103) is registered with RIPE NCC in Germany and was allocated on 2004-02-27. Self-declared in PeeringDB as a Network Service Provider (transit / backbone). IPLogs treats PeeringDB NSPs as core infrastructure (asn_peeringdb_nsp, zero weight) rather than hosting — large carriers in this bucket also carry residential traffic, so per-IP checks decide the verdict. PeeringDB lists it in 3 facilities.

How IPLogs classifies AS31103

When the detection engine sees an IP that routes through AS31103, 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 AS31103

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

Frequently asked questions about AS31103

+Is AS31103 (Keyweb AG) a VPN, datacenter, or residential network?

IPLogs classifies Keyweb AG (AS31103) as a backbone / nsp network based in Germany. The default verdict for any IP that routes through this ASN is "Transit / backbone".

+Who operates AS31103 and where is it registered?

Keyweb AG (AS31103) is registered with RIPE NCC, operates in Germany, was allocated on 2004-02-27. It is listed in PeeringDB across 3 facilities.

+How do I check or block AS31103 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 AS31103 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