I think this is a good movement and a decent timeline goal. In my personal opinion, as a suggestion I believe the Site Operators section could use a link to a

I think this is a good movement and a decent timeline goal. In my personal opinion, as a suggestion I believe the Site Operators section could use a link to a detail page that offers additional tips such as ensuring that equivalent firewall rules and kernel settings are applied to ipv6 settings to match ipv4. e.g. sysctl, iptables, firewalld, nftables, ipsets, dns blocklists Site operators should also ensure that whatever protections they have added to ipv4 have a corresponding protection on ipv6. Always test your migration on a test/staging/beta version of your sites first and keep DNS TTL low prior to and just after testing. Or in the case of datacenters, add a new ipv6 vip on your load balancers for testing using a unique endpoint name to avoid your production clients finding it by mistake before you are ready. Additionally there are DNS propagation validators [1] to verify DNS settings for ones test/staging sites. Qualys [2] has a tester for checking that both ipv4/ipv6 https settings match. Qualys also have a test [3] for clients. [Edit] As others noted the sites that are purported to support this movement should have a corresponding page on their site linking back to this domain otherwise they should be removed. The CTO of Cloudflare [4] frequents HackerNews so that should be easy to bring to closure. [1] - https://www.whatsmydns.net/ https://www.whatsmydns.net/ # Note: their web client does not wait long enough at times and may fail until you hit refresh on some probes. [2] - https://www.ssllabs.com/ssltest/ https://www.ssllabs.com/ssltest/ [3] - https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.htm... [4] - https://news.ycombinator.com/user?id=jgrahamc https://news.ycombinator.com/user?id=jgrahamc @jgrahamc