On 2017-06-06 SixXS performed a sunset.
This website is a static edition of the SixXS website.
Please read the Sunsetting SixXS page for more details.
SixXS IPv6-IPv4 and IPv4-IPv6 Website Gateway/Proxy
Welcome to the portal for the SixXS SixXS IPv6-IPv4 and IPv4-IPv6 Website Gateway/Proxy.
This portal gives IPv6 capable http-clients access to IPv4-only websites and IPv4 capable http-clients access to IPv6-only websites. It thus acts as a Web Proxy between IPv4-IPv6 and IPv6-IPv4.
Note: This service is governed by an Acceptable Usage Policy
With a few gateway-side tricks all the external hosts on the websites get .sixxs.org or ipv6.sixxs.org (IPv6 to IPv4) or ipv4.sixxs.org (IPv4 to IPv6) added to their hostname thus furter queries will end up going through the gateway.
The visited websites will find the following User-Agent in their logs:
When they get enough hits they might be hinted that IPv6 use is rising and maybe we can pursuade them this way to start making their websites natively IPv6 accessible.
How to use the IPv6Gate
Append ".sixxs.org" or ".ipv6.sixxs.org" to the hostname of the website you want to visit.
How to use the IPv4Gate
Append ".ipv4.sixxs.org" to the hostname of the website you want to visit.
For whom is this service?
The IPv6Gate service is available for all IPv6 capable HTTP/1.1 (+) clients.
What is SixXS?
SixXS is a so called IPv6 Access Provider. We make it possible for ISPs to enable their clients to access the IPv6 internet using IPv4 in IPv6 tunnels, thus avoiding upgrading the infrastructure between the client and the ISP. More detailed information is available from the main SixXS website. The IPv6Gate is an extra service to help IPv6 deployment.
Why does this service exist?
There appears to be a chicken and egg problem in deploying IPv6; ISPs serving endusers don't want to do it yet because there isn't any need for it from their clients, Hosting companies don't do it yet because there isn't any demand yet either from clients. Clients don't need it because there isn't any content and thus there isn't any need for the hosting nor the ISPs to do it. Thus, we made this gateway, which allows users who do have IPv6 to get to all the content in the IPv4 world. If you don't have IPv6 connectivity (yet) you can of course try the SixXS Tunnel Broker.
But my ISP doesn't provide IPv6 yet!
You could either pursuade your ISP to support it or get them to install a SixXS PoP or you could setup a tunnel to one of the public SixXS PoPs as SixXS is a Tunnel Broker.
But my computer doesn't do IPv6 yet!
Check out the SixXS FAQs where there are numerous examples for most common Operating Systems on how to configure IPv6 support. SixXS is a Tunnel Broker which can provide you with IPv6 connectivity even if you only have IPv4 now.
I do not wish to be proxied via IPv6Gate. What now?
It is trivial to remove traffic at your webserver - the proxy uses a custom User-Agent header, and it sets the Via: header, both of which can be used to block the traffic at serverside.
In addition to this, mostly for website operators who do not understand how to filter, we maintain a manual blacklist at our NGINX frontends. Mail firstname.lastname@example.org if you operate a website and wish to be included in the blacklist. Sites that are blocked return a HTTP 451 error page with the title 'Requested site is blacklisted' pointing to this article.
This block list only contains one entry at the moment: Facebook. This as their monitoring tools search for fake Facebook login pages, and they complained that IPv6Gate was trying to MITM Facebook. Hence, on their request, we added them to the block list.
My BitTorrent client does not work through IPv6Gate!
As per our AUP we explicitly block Torrent clients and BitTorrent requests ('/announce' and '/scrape') as these are made by incomplete HTTP clients that have been hammering on our servers overloading them by doing repeatitive useless queries.
We have thus decided to block these requests so that real users can use our IPv6Gate service properly. Requests that are banned this way will receive a 402 HTTP error with an informational page pointing at our AUP.
Note that the websites of various trackers (for instance Debian CD BitTorrent and Ubuntu alternative downloads) are not affected as these are real HTTP websites.
Can I pick the country where my exit point is?
Yes, but only in part, this is because our webfrontends do loadbalancing and failover between themselves. Generally your request will be served from the frontend that you connect to, but there might be failover to other nodes. To use this feature one can use the following construction of URL.
See the SixXS contact pages.
Some additional notes concerning this service:
Gateway Error Codes
The following table shows the custom error codes that the IPv6Gate can return. IPv6Gate error pages have the SixXS styling and a small description about the error. Note that upstream (origin site) errors are returned directly too.