Trust

Our goal is to make Handshake resolution easier to use while respecting user privacy as much as reasonably possible.

We prefer simple and honest language over exaggerated privacy claims.

Easy HNS avoids exaggerated privacy language. DNS requests still have to be processed in order to answer them, and the service still runs on real infrastructure.

The useful privacy distinction on the setup pages is simpler: encrypted DNS options such as DoH and DoT are available where the platform supports them, while plain DNS remains a fallback for platforms that only accept IP addresses.

In plain terms:

• DoH and DoT can encrypt the DNS transport to Easy HNS where supported;
• plain DNS is still visible to the network path in the usual way;
• a public resolver is not the same as a VPN;
• a resolver is not the same as full browser-native Handshake trust.

Like any online service, some limited technical data may still exist temporarily in memory, active connections, short-lived operational state, or exceptional fault handling while the service is running.

In limited exceptional cases, some technical information may also need to be handled where reasonably necessary for:

• abuse prevention;
• fault diagnosis;
• service protection;
• security incidents;
• legal compliance.

We do not describe Easy HNS as “zero data” because that would be misleading.

The Easy HNS website is intended to stay minimal.

Our default approach is:

• no behavioural advertising;
• no profiling;
• no non-essential analytics by default;
• no non-essential cookie tracking by default.

For standard internet DNS resolution outside Handshake, Easy HNS still has to use real recursive resolution paths. Those operational choices may change as the service evolves.

The site therefore focuses on the values users need to configure Easy HNS correctly, rather than promising a permanent upstream architecture.

The HNS DoH global pool is operated by the separate HNS DoH project, not by Easy HNS. Easy HNS terms, operational responsibility, support scope, and service commitments apply only to Easy HNS-operated services and do not extend to that external global pool.

Because Easy HNS is a public resolver, some abuse controls may still be necessary to protect the service from overload, malicious traffic, or operational harm.

This page does not promise an absolute “zero data” system, because that would be misleading for a real online service.

Easy HNS is privacy-conscious and transparent about setup, but it still runs on real infrastructure, uses real software, and exists within real legal and operational constraints.

That means privacy is improved by correct protocol choices and clear limits, not by pretending the service operates outside physics, software, or law.

Easy HNS is designed to improve access to Handshake domains, but convenient public resolution is not the same as full browser-native trust validation.

Standard browsers may still warn on some Handshake websites, or show no secure HTTPS-style indicator, because they do not natively understand Handshake trust and DANE/TLSA the way a dedicated Handshake-aware desktop tool can.

For users who want a stronger Handshake-native browsing experience on desktop, Easy HNS recommends Fingertip.

If you have privacy or trust questions, contact:

Reveal contact