Country
—
ASN LANDING PAGE
RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH
Last updated · Apr 4, 2026
Country
—
Total prefixes
28
IPv4 prefixes
14
IPv6 prefixes
14
RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH currently shows 28 prefixes and 43 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS6939
AS6939
—
AS20473
AS20473
—
AS5459
AS5459
—
AS44066
AS44066
—
AS49544
AS49544
—
AS29222
AS29222
—
AS7195
AS7195
—
AS42708
AS42708
—
AS42473
AS42473
—
AS30971
AS30971
—
AS36236
AS36236
—
AS199524
AS199524
—
AS55803
AS55803
—
AS8849
AS8849
—
AS22548
AS22548
—
AS25091
AS25091
—
AS20764
AS20764
—
AS42310
AS42310
—
AS29075
AS29075
—
AS33891
AS33891
—
AS35280
AS35280
—
AS50304
AS50304
—
AS34549
AS34549
—
AS3214
AS3214
—
AS29014
AS29014
—
AS34177
AS34177
—
AS34927
AS34927
—
AS41327
AS41327
—
AS48362
AS48362
—
AS1828
AS1828
—
AS3170
AS3170
—
AS3216
AS3216
—
AS6424
AS6424
—
AS6830
AS6830
—
AS12969
AS12969
—
AS14630
AS14630
—
AS15802
AS15802
—
AS24482
AS24482
—
AS25160
AS25160
—
AS25369
AS25369
—
| Prefix | Name | Country |
|---|---|---|
| 176.97.158.0/24 | AS1921 | — |
| 185.102.12.0/24 | AS1921 | — |
| 185.167.176.0/24 | AS1921 | — |
| 185.80.188.0/24 | AS1921 | — |
| 192.174.68.0/24 | AS1921 | — |
| 193.227.117.0/24 | AS1921 | — |
| 193.46.128.0/24 | AS1921 | — |
| 193.46.133.0/24 | AS1921 | — |
| 193.46.134.0/24 | AS1921 | — |
| 193.46.135.0/24 | AS1921 | — |
| 194.0.182.0/24 | AS1921 | — |
| 194.0.25.0/24 | AS1921 | — |
| 194.50.187.0/24 | AS1921 | — |
| 2001:678:20::/48 | AS1921 | — |
| 2001:67c:10b8::/48 | AS1921 | — |
| 2001:67c:1bc::/48 | AS1921 | — |
| 2a02:850:ffe0::/48 | AS1921 | — |
| 2a02:850:ffe5::/48 | AS1921 | — |
| 2a02:850:ffe6::/48 | AS1921 | — |
| 2a02:850:ffe7::/48 | AS1921 | — |
| 2a02:850:ffff::/48 | AS1921 | — |
| 2a04:2b00:14cc::/48 | AS1921 | — |
| 2a04:2b00:14dd::/48 | AS1921 | — |
| 2a04:2b00:14ee::/48 | AS1921 | — |
| 2a05:7f00:188::/48 | AS1921 | — |
| 2a0b:8e00:1::/48 | AS1921 | — |
| 2a0b:8e00::/48 | AS1921 | — |
| 91.237.67.0/24 | AS1921 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Useful when you want to decide whether this ASN behaves like a CDN, Anycast, or edge-delivery network.
Useful for deciding whether this ASN looks more like website CDN frontage or the real hosting origin.
Useful for tracing the real hosting provider behind an edge or CDN layer.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
AS1921 is an autonomous system number used to identify an independently operated network. The current page associates it with RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS1921. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS1921, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Separate public DNS, CDN Anycast, and edge-delivery IP behavior, especially when one IP appears to shift across multiple locations.
Understand how CDN, Anycast, and edge delivery change IP geolocation, latency interpretation, origin tracing, and ASN attribution.
Separate CDN or edge IPs from the real website origin-hosting or server IP behind a domain.
Use DNS, ASN, WHOIS, CNAMEs, HTTP headers, and CDN clues to trace the real hosting or cloud provider behind a website.