Manual

Advanced Manual Setup

If you already know where your software expects DNS values, this page gives you the exact Easy HNS endpoints without guesswork.

At a glance

Best for

Power users, network admins, and anyone following a platform-specific custom DNS field.

Protocol

DoH, DoT, plain DNS

Coverage

Varies

Setup time

Depends on platform

Main input

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

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

Guide summary

Power users, network admins, and anyone following a platform-specific custom DNS field.DoH, DoT, plain DNSVariesAdvancedDepends on platform

Before you start

Check 01

Know whether your target accepts a hostname, a URL template, or plain IP addresses.

Check 02

Check whether the field is browser-only or system-wide before you save.

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.

DNS over HTTPS

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

Use in browsers and platforms that accept a DoH template URL.

DNS over TLS hostname

dns.easyhns.com

Use in Android Private DNS or other DoT-specific inputs.

IPv4

51.24.7.1

Fallback for routers and plain DNS-only environments.

IPv6

2a05:d01c:b4a:2900:945c:1a85:e537:cf80

Optional IPv6 endpoint.

Resolver location

London

Current public Easy HNS node.

Step-by-Step

Short steps, no filler.

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

Step 01

Match the field to the protocol

Use the URL for DoH, the hostname for DoT, and the IPs only where the software accepts plain DNS addresses.

Step 02

Avoid mixed inputs

Do not paste the DoH URL into a hostname-only field, and do not add https:// to a DoT hostname input.

Step 03

Be honest about fallback

If the client says browser-only, only that app will use Easy HNS. If the device says system-wide, the whole device should use it.

How to verify

Check 01

Test with a Handshake domain and, if available, the platform's own DNS diagnostics.

Check 02

If the platform offers a status line for secure DNS, confirm it says active, encrypted, or connected.

Troubleshooting

Note 01

A surprising number of DNS problems come from pasting a URL into a hostname field or a hostname into a URL field.

Note 02

If a network blocks secure DNS, a plain DNS fallback may be the only option on that connection.

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.