Browser-only

Chrome Setup

Chrome includes a built-in secure DNS setting. It is a good option when you want Handshake access in the browser without changing your whole device.

At a glance

Best for

Chrome users who only need Handshake domains inside the browser.

Protocol

DoH

Coverage

Browser-only

Setup time

1 minute

Main input

https://dns.easyhns.com/dns-query

Chrome Setup stays focused on the shortest accurate path for this platform.

Guide summary

Chrome users who only need Handshake domains inside the browser.DoHBrowser-onlyEasy1 minute

Before you start

Check 01

Use a current desktop Chrome build.

Check 02

If your browser is managed by work or school policy, Secure DNS may be locked.

Exact Values

Use the right field for the right input.

URL fields need the full DoH URL. Hostname fields need the DoT hostname only. IP fields need the raw address only.

Custom provider URL

https://dns.easyhns.com/dns-query

Paste this into Chrome's custom Secure DNS provider field.

Step-by-Step

Short steps, no filler.

Follow the route in order, then verify the active DNS setting before changing another layer.

Step 01

Open Chrome security settings

Open Chrome, go to Settings, select Privacy and security, then open Security.

Step 02

Turn on Secure DNS

Under Advanced, make sure Use secure DNS is enabled.

Step 03

Choose a custom provider

Open the provider dropdown, choose a custom service provider, and paste https://dns.easyhns.com/dns-query.

How to verify

Check 01

Open a Handshake domain in Chrome after saving the provider.

Check 02

If it still fails, fully close Chrome and open it again so existing tabs do not keep older DNS state.

Troubleshooting

Note 01

If the custom option is missing, your browser may be managed by policy or using an older UI build.

Note 02

If Chrome falls back unexpectedly, recheck the provider field for typos and confirm the full https:// URL is still present.

Important note about Handshake website security warnings

Using Easy HNS gives you convenient access to Handshake domains, but standard browsers may still show security warnings for some Handshake websites.

Why? Because most mainstream browsers do not natively validate Handshake trust and DANE/TLSA in the same way they validate the conventional HTTPS web.

As a result:

  • some Handshake websites may load over HTTP;
  • some may show a browser warning or missing secure indicator;
  • this is often a browser trust-model limitation, not automatically proof that the website is malicious.

If you want a stronger Handshake-native browsing experience with DANE/TLSA support, use Fingertip for desktop.

Using a VPN?

Easy HNS still works well with VPNs, but browser Secure DNS can override router or system DNS, and some VPN apps force their own resolver. Use 51.24.7.1 only in IP fields, use https://dns.easyhns.com/dns-query only in DoH fields, and verify which layer is actually winning.