Public DNS resolver · SafeDNS
SafeDNS DNS servers
SafeDNS answers on 195.46.39.39 and 195.46.39.40. In our 2026-09-24 test it did not validate DNSSEC and sent no client subnet.
- Addresses
- 4
- Variants
- 1
- Measured
- 2026-09-24
- Operator
- SafeDNS
- Primary IPv4
- 195.46.39.39
- All IPv4
- 195.46.39.39, 195.46.39.40
- All IPv6
- 2001:67c:2778::3939, 2001:67c:2778::3940
- DNS over HTTPS
- not documented
- DNS over TLS
- not documented
- Service variants
- 1 (SafeDNS)
- DNSSEC in our test
- Does not validate
- Client subnet (ECS)
- None sent
- Protocols
- DNS (53)
SafeDNS DNS addresses by variant
Set the IPv4 or IPv6 addresses as your DNS servers, or use an encrypted endpoint where one is listed.
| Variant | Filtering (operator description) | IPv4 | IPv6 | Encrypted |
|---|---|---|---|---|
| SafeDNS | Not specified by the operator | 195.46.39.39195.46.39.40 | 2001:67c:2778::39392001:67c:2778::3940 | Not documented |
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.
- 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.
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.
| ASN | Holder | Role |
|---|---|---|
| AS57926 | SAFEDNS-AS SafeDNS, Inc. | Announces the service addresses |
| AS36236 | NETACTUATE - NetActuate, Inc | Queried from, in our probe |
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.
# 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.39Behind 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.
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
Documentation checked 2026-09-24. Measured 2026-09-24. Registry reviewed 2026-09-24.
Addresses and endpoints come from each operator's documentation; behaviour is what we measured from one location on 2026-09-24. Speed, uptime and how well a filter blocks what it promises were not tested.