Country
—
ASN LANDING PAGE
E-DNS-JP - WIDE Project
Last updated · Jul 20, 2026
Country
—
Total prefixes
2
IPv4 prefixes
1
IPv6 prefixes
1
E-DNS-JP - WIDE Project currently reports 2 prefixes and 5 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
E-DNS-JP - WIDE Project is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
Detailed data for this ASN is not available right now.
| Prefix | Name | Country |
|---|---|---|
| 192.50.43.0/24 | AS23634 | — |
| 2001:200:c000::/35 | AS23634 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS23634 is an autonomous system number. The current source associates it with E-DNS-JP - WIDE Project and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS23634. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS23634, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Explain the role differences in Public DNS vs CDN and Anycast and show exactly how far public IP, ASN, and BGP evidence can support the comparison.
Compare common public resolvers by IP, Geo estimate, ISP, ASN, and BGP prefix, with clear limits for each public field.
Explain the role differences in Public DNS vs Security DNS and show exactly how far public IP, ASN, and BGP evidence can support the comparison.
Compare the public resolver addresses, ASN, and BGP prefixes associated with Primary and Secondary Public DNS Resolver, then confirm address roles in current operator documentation.