<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DOH on LEl_FENG Blog</title><link>https://blog.xpdbk.com/en/tags/doh/</link><description>Recent content in DOH on LEl_FENG Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>LEl_FENG Copyright</copyright><lastBuildDate>Wed, 29 May 2024 06:46:10 +0700</lastBuildDate><atom:link href="https://blog.xpdbk.com/en/tags/doh/index.xml" rel="self" type="application/rss+xml"/><item><title>Enabling DOH and ECH Encryption in Chrome</title><link>https://blog.xpdbk.com/en/posts/chrome-doh-ech/</link><pubDate>Wed, 29 May 2024 06:46:10 +0700</pubDate><guid>https://blog.xpdbk.com/en/posts/chrome-doh-ech/</guid><description>&lt;img src="https://blog.xpdbk.com/en/posts/chrome-doh-ech/1_-_Cover.width-1200.format-webp.webp" alt="Featured image of post Enabling DOH and ECH Encryption in Chrome" />&lt;blockquote>
&lt;p>&lt;strong>TL;DR / [Geek Summary]:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Privacy Hardening: Enable DoH (DNS over HTTPS) to bypass DNS hijacking and snooping.&lt;/li>
&lt;li>Deep Encryption: Force-enable ECH via &lt;code>chrome://flags&lt;/code> to encrypt the SNI handshake.&lt;/li>
&lt;li>Pro Tip: Pair with TUN mode proxies to prevent traffic leaks and ensure full-stack privacy.&lt;/li>
&lt;/ul>
&lt;/blockquote>
&lt;h2 id="materials-needed">
&lt;a href="#materials-needed" class="heading-anchor" aria-label="Anchor for Materials Needed">#&lt;/a>
Materials Needed
&lt;/h2>
&lt;ul>
&lt;li>Chrome Browser&lt;/li>
&lt;/ul>
&lt;h2 id="steps">
&lt;a href="#steps" class="heading-anchor" aria-label="Anchor for Steps">#&lt;/a>
Steps
&lt;/h2>
&lt;p>&lt;strong>Enabling DOH&lt;/strong>&lt;/p>
&lt;ol>
&lt;li>Open Chrome 1. In your browser settings, click &amp;ldquo;Privacy and Security&amp;rdquo; → &amp;ldquo;Security&amp;rdquo; in sequence.&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://blog.xpdbk.com/en/posts/chrome-doh-ech/351529.webp"
width="2560"
height="1350"
srcset="https://blog.xpdbk.com/en/posts/chrome-doh-ech/351529_hu7e6e7d46d3b050831b6aa9d6f1e963d8_77786_480x0_resize_q75_h2_box_2.webp 480w, https://blog.xpdbk.com/en/posts/chrome-doh-ech/351529_hu7e6e7d46d3b050831b6aa9d6f1e963d8_77786_1024x0_resize_q75_h2_box_2.webp 1024w"
loading="lazy"
alt="Corresponding page"
class="gallery-image"
data-flex-grow="189"
data-flex-basis="455px"
>&lt;/p>
&lt;ol start="2">
&lt;li>Go to &amp;ldquo;Advanced&amp;rdquo; and enable &amp;ldquo;Use secure DNS&amp;rdquo;. Then select a DNS provider (if you don&amp;rsquo;t know, just choose Cloudflare).&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://blog.xpdbk.com/en/posts/chrome-doh-ech/30.webp"
width="1360"
height="701"
srcset="https://blog.xpdbk.com/en/posts/chrome-doh-ech/30_huc97ffc31200369619ff96e252c761e45_35484_480x0_resize_q75_h2_box_2.webp 480w, https://blog.xpdbk.com/en/posts/chrome-doh-ech/30_huc97ffc31200369619ff96e252c761e45_35484_1024x0_resize_q75_h2_box_2.webp 1024w"
loading="lazy"
alt="Options"
class="gallery-image"
data-flex-grow="194"
data-flex-basis="465px"
>&lt;/p>
&lt;p>&lt;strong>Enable ECH&lt;/strong>&lt;/p>
&lt;p>Open this address in your Chrome browser: chrome://flags/#encrypted-client-hello, and change the Encrypted ClientHello option to Enabled.&lt;/p>
&lt;p>&lt;img src="https://blog.xpdbk.com/en/posts/chrome-doh-ech/34.webp"
width="1462"
height="357"
srcset="https://blog.xpdbk.com/en/posts/chrome-doh-ech/34_hud5e0fc10138b38c778c8c0e0543d6504_23246_480x0_resize_q75_h2_box_2.webp 480w, https://blog.xpdbk.com/en/posts/chrome-doh-ech/34_hud5e0fc10138b38c778c8c0e0543d6504_23246_1024x0_resize_q75_h2_box_2.webp 1024w"
loading="lazy"
alt="Enable it"
class="gallery-image"
data-flex-grow="409"
data-flex-basis="982px"
>&lt;/p>
&lt;h2 id="detection">
&lt;a href="#detection" class="heading-anchor" aria-label="Anchor for Detection">#&lt;/a>
Detection
&lt;/h2>
&lt;ol>
&lt;li>Open this CF website: &lt;a class="link" href="https://www.cloudflare.com/zh-cn/ssl/encrypted-sni/" target="_blank" rel="noopener"
>https://www.cloudflare.com/zh-cn/ssl/encrypted-sni/&lt;/a>
&lt;span style="white-space: nowrap;">&lt;svg width=".7em"
height=".7em" viewBox="0 0 21 21" xmlns="http://www.w3.org/2000/svg">
&lt;path d="m13 3l3.293 3.293l-7 7l1.414 1.414l7-7L21 11V3z" fill="currentColor" />
&lt;path d="M19 19H5V5h7l-2-2H5c-1.103 0-2 .897-2 2v14c0 1.103.897 2 2 2h14c1.103 0 2-.897 2-2v-5l-2-2v7z"
fill="currentColor">
&lt;/svg>&lt;/span>
, and click the &amp;ldquo;Check my browser&amp;rdquo; button.&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://blog.xpdbk.com/en/posts/chrome-doh-ech/3.webp"
width="2560"
height="1350"
srcset="https://blog.xpdbk.com/en/posts/chrome-doh-ech/3_hu884360b3ea970400f07c377d41d717e8_93220_480x0_resize_q75_h2_box_2.webp 480w, https://blog.xpdbk.com/en/posts/chrome-doh-ech/3_hu884360b3ea970400f07c377d41d717e8_93220_1024x0_resize_q75_h2_box_2.webp 1024w"
loading="lazy"
alt="Corresponding detection page"
class="gallery-image"
data-flex-grow="189"
data-flex-basis="455px"
>&lt;/p>
&lt;ol start="2">
&lt;li>If you see a checkmark under &amp;ldquo;Secure DNS&amp;rdquo;, it means DOH is enabled. If you see a checkmark under &amp;ldquo;Secure SNI&amp;rdquo;, it means ECH is enabled.&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://blog.xpdbk.com/en/posts/chrome-doh-ech/21354.webp"
width="2560"
height="1350"
srcset="https://blog.xpdbk.com/en/posts/chrome-doh-ech/21354_hub82b80f9be646eb15a93b18b783fff8a_86978_480x0_resize_q75_h2_box_2.webp 480w, https://blog.xpdbk.com/en/posts/chrome-doh-ech/21354_hub82b80f9be646eb15a93b18b783fff8a_86978_1024x0_resize_q75_h2_box_2.webp 1024w"
loading="lazy"
alt="Checking all the boxes is powerful"
class="gallery-image"
data-flex-grow="189"
data-flex-basis="455px"
>&lt;/p>
&lt;h2 id="notes">
&lt;a href="#notes" class="heading-anchor" aria-label="Anchor for Notes">#&lt;/a>
Notes
&lt;/h2>
&lt;p>If you are using a software router, this doesn&amp;rsquo;t matter and you don&amp;rsquo;t need to worry about it. If you are using other clients, you need to enable TUN. The mode allows it to take over all traffic; otherwise, the browser will not use its own DOH service but will instead hand it over to the proxy software for resolution, which in turn will be sent to the node server for DNS resolution, resulting in invalid traffic.&lt;/p></description></item></channel></rss>