DNS resolver registry · SafeDNS

SafeDNS DNS servers

SafeDNS offers one service, reachable over DNS (53). Every address and endpoint below is taken from the operator's documentation; the behaviour is what we measured on 2026-09-24.
195.46.39.39
primary address
4
addresses in 1 variant
Does not validate
DNSSEC in our test
None sent
client subnet (ECS)

Addresses

SafeDNS DNS addresses by variant

Set the IPv4 or IPv6 addresses as your DNS servers, or use an encrypted endpoint where one is listed.

SafeDNS

Not specified by the operator

IPv4
195.46.39.39
195.46.39.40
IPv6
2001:67c:2778::3939
2001:67c:2778::3940

Measured

What we observed

Measured 2026-09-24 from one vantage point, three rounds per address, majority result. Anycast resolvers can behave differently from other networks. How we test

DNSSEC validation Does not validate

Returned addresses for dnssec-failed.org, rhybar.cz and badsig.go.dnscheck.tools, which a validating resolver would refuse.

Client subnet (ECS)

No client subnet reached the authoritative server from any address we probed.

Plain DNS and NXDOMAIN

2/2 documented IPv4 addresses answered on port 53. Random non-existent names came back as NXDOMAIN, so errors are not rewritten into ads or search pages.

Encrypted endpoints

None documented on the page we checked.

Networks

Which networks carry it

The announcing network comes from RIPEstat routing data for each documented address. The query network is where the resolver sent its own lookups during our probe, which a DNS leak test reports.

Announcing the service addresses

  • AS57926 SAFEDNS-AS SafeDNS, Inc.

Queried from, in our probe

  • AS36236 NETACTUATE - NetActuate, Inc

Check it

Confirm your device is using SafeDNS

Changing a DNS setting does not guarantee your lookups reach that resolver: a VPN, a browser's own secure DNS or a proxy can send them elsewhere. Our DNS leak test shows which resolvers actually received your queries.

From a terminal

# Which address did the resolver query from?
dig +short whoami.akamai.net @195.46.39.39

# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @195.46.39.39

# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @195.46.39.39

Behind a proxy

With an HTTP proxy, or a client set to socks5h://, the proxy side resolves hostnames, so your own resolver setting does not apply to that traffic. With socks5:// in curl or Python requests, your device resolves names first. The SOCKS5 vs SOCKS5h guide shows how to check which one you have.

Questions

SafeDNS questions

What are SafeDNS's DNS server addresses?

SafeDNS: 195.46.39.39, 195.46.39.40, 2001:67c:2778::3939, 2001:67c:2778::3940.

Does SafeDNS validate DNSSEC?

Not in our 2026-09-24 test: it returned addresses for all three deliberately mis-signed domains.

Does SafeDNS support DNS over HTTPS or DNS over TLS?

The SafeDNS page we checked documents plain DNS addresses only.

Does SafeDNS send my IP subnet to other servers (ECS)?

We observed no client subnet on any address we probed.

How can I check that I am using SafeDNS?

Run a DNS leak test and compare the network it reports with the one SafeDNS queried from in our probe (AS36236). On the command line, dig +short whoami.akamai.net @195.46.39.39 returns the address the resolver used to query Akamai.

Sources

Sources and dates

Documentation checked 2026-09-24. Measured 2026-09-24. Registry reviewed 2026-09-24.