Country
—
ASN LANDING PAGE
SCANSAFE - Cisco OpenDNS
Last updated · Apr 4, 2026
Country
—
Total prefixes
4
IPv4 prefixes
4
IPv6 prefixes
0
SCANSAFE - Cisco OpenDNS currently shows 4 prefixes and 3 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.
SCANSAFE - Cisco OpenDNS 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.
| Prefix | Name | Country |
|---|---|---|
| 155.190.249.0/24 | AS25605 | — |
| 198.41.11.0/24 | AS25605 | — |
| 198.41.13.0/24 | AS25605 | — |
| 67.215.95.0/24 | AS25605 | — |
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 comparing OpenDNS primary and secondary nodes inside the same ASN footprint.
Useful for deciding whether this ASN behaves more like public DNS, enterprise security DNS, or another managed resolver service.
Useful for comparing OpenDNS with DNS services that lean more heavily into security policy, filtering, or threat-blocking behavior.
Useful for comparing OpenDNS against broader public-resolver patterns.
Useful for separating general public DNS from more enterprise-managed resolver services.
Useful for comparing OpenDNS with local ISP or carrier DNS behavior.
AS25605 is an autonomous system number used to identify an independently operated network. The current page associates it with SCANSAFE - Cisco OpenDNS 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 AS25605. 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 AS25605, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Separate OpenDNS from enterprise-security DNS and internal resolver workflows, and understand what addresses like 208.67.222.222 really represent.
Compare OpenDNS with security DNS across enterprise-security resolver framing, filtering and threat-blocking behavior, policy control, and service positioning.
Compare 208.67.222.222 and 208.67.220.220 across ASN ownership, prefixes, enterprise-security DNS context, and resolver role to understand OpenDNS primary and secondary nodes.
Compare OpenDNS with Google DNS, Cloudflare DNS, Quad9, and other public resolvers to understand what kind of DNS service 208.67.222.222 represents.