Country
—
ASN LANDING PAGE
VERISIGN-INC - VeriSign Global Registry Services
Last updated · Apr 4, 2026
Country
—
Total prefixes
1
IPv4 prefixes
1
IPv6 prefixes
0
VERISIGN-INC - VeriSign Global Registry Services currently shows 1 prefixes and 80 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.
VERISIGN-INC - VeriSign Global Registry Services 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.
AS396661
AS396661
—
AS396654
AS396654
—
AS396761
AS396761
—
AS396688
AS396688
—
AS396707
AS396707
—
AS396690
AS396690
—
AS396675
AS396675
—
AS396659
AS396659
—
AS396686
AS396686
—
AS396748
AS396748
—
AS396658
AS396658
—
AS396729
AS396729
—
AS396704
AS396704
—
AS396747
AS396747
—
AS396625
AS396625
—
AS396735
AS396735
—
AS396737
AS396737
—
AS396738
AS396738
—
AS396739
AS396739
—
AS396666
AS396666
—
AS396694
AS396694
—
AS396619
AS396619
—
AS396629
AS396629
—
AS396689
AS396689
—
AS396692
AS396692
—
AS396712
AS396712
—
AS396714
AS396714
—
AS396721
AS396721
—
AS396653
AS396653
—
AS396662
AS396662
—
AS396691
AS396691
—
AS396702
AS396702
—
AS396711
AS396711
—
AS396749
AS396749
—
AS396766
AS396766
—
AS396620
AS396620
—
AS396621
AS396621
—
AS396624
AS396624
—
AS396641
AS396641
—
AS396674
AS396674
—
AS4766
AS4766
—
AS25091
AS25091
—
AS2381
AS2381
—
AS2107
AS2107
—
AS6939
AS6939
—
AS20764
AS20764
—
AS4826
AS4826
—
AS24482
AS24482
—
AS49544
AS49544
—
AS8218
AS8218
—
AS9002
AS9002
—
AS13004
AS13004
—
AS47734
AS47734
—
AS51185
AS51185
—
AS199524
AS199524
—
AS3214
AS3214
—
AS6057
AS6057
—
AS6424
AS6424
—
AS8298
AS8298
—
AS12637
AS12637
—
AS12779
AS12779
—
AS15547
AS15547
—
AS35280
AS35280
—
AS39351
AS39351
—
AS47692
AS47692
—
AS50304
AS50304
—
AS50629
AS50629
—
AS58115
AS58115
—
AS64073
AS64073
—
AS137409
AS137409
—
AS202032
AS202032
—
AS559
AS559
—
AS917
AS917
—
AS924
AS924
—
AS1003
AS1003
—
AS1257
AS1257
—
AS1828
AS1828
—
AS1836
AS1836
—
AS1853
AS1853
—
AS2027
AS2027
—
| Prefix | Name | Country |
|---|---|---|
| 199.7.63.0/24 | AS26415 | — |
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.
AS26415 is an autonomous system number used to identify an independently operated network. The current page associates it with VERISIGN-INC - VeriSign Global Registry Services 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 AS26415. 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 AS26415, 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.