Ipv6 access to website

I am just wondering if there is a way to access a website via the provided by cloiudflare ipv6 address via a browser.

As long as the client supports IPv6 they use it to connect to the Cloudflare edges. Everything else wouldn’t make sense.

I’ve no v6 enabled host but I guess CF would make use of it preferably as well if it is supported by your origin.

Thank you for your response.
"client supports IPv6 " I am approaching accessing the website from ipv6 enabled client. I haven’t had an ipv6 for the website until I enabled it at the Cloudflare. When I am accessing the website via the ipv6 ip address provided by Cloudflare I am getting a message that direct ip access wont work.
When I check with curl via adding a header like
curl --header “Host: websiteaddress” http://[ipv6addressprovidedbyCloudflare] it will provide a href url link to the websiteaddress.
And yes, it uses ipv6 address saying connected with it when I am approaching with wget website.com, but of two ipv6 addresses provided one fails and only the other works, as it seems to me.

(post withdrawn by author, will be automatically deleted in 1 hour unless flagged)

Works for me. When I visit https://www.your.domain/cdn-cgi/trace from a location with IPv6 support I get the following:

uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

This reminds me of a result in test-ipv6.com when I use Firefox:

Your browser is avoiding IPv6.

What we found What causes a preference for IPv4 Why this worries us 

This document explains why we worry when IPv4 is preferred over IPv6.
What we found
This section applies only when we offered to show you this page from inside the test.

First of all, we detected you had a working IPv6 connection. We also found that your IPv6 connection, was using a “real” IPv6 address; meaning not a Teredo or a 6to4 address.

Second, we detected that when given the choice, your browser decided it would prefer to use IPv4 instead of IPv6. This has some concerns for us.
Causes for preferring IPv4

There are several possible reasons why a browser might prefer IPv4 instead of IPv6.

Google's "Chrome" has a "fast fallback" mechanism. On the first try to a site, it will prefer IPv6. If connections take longer than a third of a second, IPv4 is attempted in parallel; and the better of the two will be used for that site. (more info)
Firefox (recent builds) does the same as Chrome. (more info)
The latest Windows 7 and Windows 8 updates will periodically test to see if IPv6 works. If the health check fails, then many applications (including Internet Explorer) will use IPv4, to insulate you from any local IPv6 misconfiguration. (more info)
Apple's latest Lion and Mountain Lion updates will prefer whichever is "faster" for a given destination. As of OS X 10.11 "El Capitan" and iOS 9, IPv6 is given a slight preference; but will fall back to IPv4 if network conditions warrant it. (more info)

Well technically if this is providing a 301 redirect to the https version then that is expected, your site does the same thing on IPv4 with http.

well, it happens vice versa, actually, as it turned out:
when execute
curl https website address
it will return
<a href='http: website address> Found
basically my end website is at google sites, and it has not ipv6 at google end.
when I do
webaddress cdn-cgi/trace it will just show ipv4 address, perhaps for ipv6 address will be shown support of ipv6 should be enabled at the end side of the website [ google sites in that case]

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.