Indeed.
FF seems to have completely moved over to ECH in their latest beta.
Although, for versions <85.0 they still require to turn on "network.dns.echconfig.enabled" for it to take effect.
I'd still rather be with ESNI until more websites start implementing the new draft. That beta change is highly controversial right now.
From my understanding, enabling ech on websites is quite complicated so no one really does it. So most domain you would hit would be all on Cloudflare where most wouldn't even know that they have such a tech enabled by default on their domains.
CloudFlare essentially introduced ESNI to the web. They enabled it on all domains on their network by default and from my understanding, there is no backend option to disable it. Firefox added support around the same time. Both organizations basically worked together on the rollout from what I remember. There are some guides available online to enable draft version of ESNI if you don't want to use CloudFlare. It's likely 99.9% of ESNI/ECH enabled domains on the web right now are basically Cloudflare powered.
Google is waiting for the standard to reach a stable point before it is added to Chrome. Firefox and Cloudflare's implementations are based on early development stage.
Can't wait for tech like ECH to become mainstream. Would be interesting to see the fireworks with regards to government's and ISP's when they realize that their censorship crap stopped working.
They can straight up block sites with ECH if they want. Even if they don't know whats inside, they can still know if its encrypted or not and block it.
This website uses affiliate links. This means that if you click on a link and make a purchase, we may receive a commission. This does not affect the price you pay for the product.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.