Country
—
ASN LANDING PAGE
IMRS - ICANN
Last updated · Apr 4, 2026
Country
—
Total prefixes
19
IPv4 prefixes
9
IPv6 prefixes
10
IMRS - ICANN currently shows 19 prefixes and 40 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.
IMRS - ICANN 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.
Detailed data for this ASN is not available right now.
AS8452
AS8452
—
AS33544
AS33544
—
AS6939
AS6939
—
AS1299
AS1299
—
AS37100
AS37100
—
AS2914
AS2914
—
AS3491
AS3491
—
AS3257
AS3257
—
AS12731
AS12731
—
AS8220
AS8220
—
AS38880
AS38880
—
AS1820
AS1820
—
AS29049
AS29049
—
AS6697
AS6697
—
AS20912
AS20912
—
AS33920
AS33920
—
AS37721
AS37721
—
AS2018
AS2018
—
AS8522
AS8522
—
AS31287
AS31287
—
AS21497
AS21497
—
AS24990
AS24990
—
AS2495
AS2495
—
AS4826
AS4826
—
AS6968
AS6968
—
AS8265
AS8265
—
AS21282
AS21282
—
AS3462
AS3462
—
AS10084
AS10084
—
AS15954
AS15954
—
AS23028
AS23028
—
AS53062
AS53062
—
AS7004
AS7004
—
AS7575
AS7575
—
AS8473
AS8473
—
AS16735
AS16735
—
AS31713
AS31713
—
AS1797
AS1797
—
AS9790
AS9790
—
AS48716
AS48716
—
| Prefix | Name | Country |
|---|---|---|
| 192.0.37.0/24 | AS20144 | — |
| 192.0.38.0/24 | AS20144 | — |
| 192.0.40.0/24 | AS20144 | — |
| 192.0.41.0/24 | AS20144 | — |
| 199.43.132.0/24 | AS20144 | — |
| 199.7.82.0/23 | AS20144 | — |
| 199.7.83.0/24 | AS20144 | — |
| 199.7.94.0/24 | AS20144 | — |
| 199.7.95.0/24 | AS20144 | — |
| 2001:500:3::/48 | AS20144 | — |
| 2001:500:8c::/48 | AS20144 | — |
| 2001:500:9c::/48 | AS20144 | — |
| 2001:500:9d::/48 | AS20144 | — |
| 2001:500:9e::/47 | AS20144 | — |
| 2001:500:9f::/48 | AS20144 | — |
| 2602:800:9004::/48 | AS20144 | — |
| 2602:800:9005::/48 | AS20144 | — |
| 2620:0:22b0::/48 | AS20144 | — |
| 2620:0:2ee0::/48 | AS20144 | — |
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.
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.
Continue from the ASN page into WHOIS and ownership verification.
AS20144 is an autonomous system number used to identify an independently operated network. The current page associates it with IMRS - ICANN 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 AS20144. 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 AS20144, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.