Country
—
ASN LANDING PAGE
L7GUARD-AS - ZAO Web Hosting
Last updated · Apr 4, 2026
Country
—
Total prefixes
11
IPv4 prefixes
11
IPv6 prefixes
0
L7GUARD-AS - ZAO Web Hosting currently shows 11 prefixes and 41 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.
L7GUARD-AS - ZAO Web Hosting 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.
AS20485
AS20485
—
AS30943
AS30943
—
AS3216
AS3216
—
AS12389
AS12389
—
AS6939
AS6939
—
AS8218
AS8218
—
AS25091
AS25091
—
AS39351
AS39351
—
AS41327
AS41327
—
AS49434
AS49434
—
AS50673
AS50673
—
AS56911
AS56911
—
AS61049
AS61049
—
AS3170
AS3170
—
AS6204
AS6204
—
AS6663
AS6663
—
AS9198
AS9198
—
AS13004
AS13004
—
AS15958
AS15958
—
AS24482
AS24482
—
AS28910
AS28910
—
AS28917
AS28917
—
AS29049
AS29049
—
AS34927
AS34927
—
AS36236
AS36236
—
AS37721
AS37721
—
AS41722
AS41722
—
AS42295
AS42295
—
AS44901
AS44901
—
AS48678
AS48678
—
AS49673
AS49673
—
AS56655
AS56655
—
AS60171
AS60171
—
AS137409
AS137409
—
AS200612
AS200612
—
AS205112
AS205112
—
AS208972
AS208972
—
AS209823
AS209823
—
AS215638
AS215638
—
| Prefix | Name | Country |
|---|---|---|
| 185.67.164.0/22 | AS40966 | — |
| 185.67.164.0/24 | AS40966 | — |
| 185.67.165.0/24 | AS40966 | — |
| 185.67.166.0/24 | AS40966 | — |
| 185.67.167.0/24 | AS40966 | — |
| 217.112.32.0/20 | AS40966 | — |
| 217.112.36.0/23 | AS40966 | — |
| 217.112.42.0/23 | AS40966 | — |
| 217.112.44.0/24 | AS40966 | — |
| 217.112.45.0/24 | AS40966 | — |
| 217.112.46.0/24 | AS40966 | — |
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 for deciding whether this ASN behaves more like traditional website hosting, shared hosting, or WordPress infrastructure.
Useful for separating shared-IP behavior from dedicated-IP usage on this ASN.
Useful for separating registrar or WHOIS clues from the real hosting provider.
Useful for understanding shared-IP density, hosting quality, and possible business impact.
Useful for understanding why many websites may share one IP on this hosting ASN.
Useful for deciding whether this ASN behaves more like shared hosting or another shared website platform.
AS40966 is an autonomous system number used to identify an independently operated network. The current page associates it with L7GUARD-AS - ZAO Web Hosting 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 AS40966. 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 AS40966, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Use resolved website IPs, ASN, WHOIS, and prefixes to determine which hosting or cloud provider is most likely behind a website.
Use DNS, ASN, WHOIS, CNAMEs, HTTP headers, and CDN clues to trace the real hosting or cloud provider behind a website.
Separate the domain registrar, DNS vendor, and the real hosting provider behind a website, especially when WHOIS and network ownership do not match.
Use same-IP density, ASN ownership, WHOIS data, cPanel or WordPress traces, and network-role clues to decide whether a site looks like shared hosting.