DNS resolver registry · Surfshark B.V.

Surfshark DNS DNS servers

Surfshark DNS is run by Surfshark B.V. and offers one service, reachable over DNS (53), DoH. Every address and endpoint below is taken from the operator's documentation; the behaviour is what we measured on 2026-09-24.
194.169.169.169
primary address
2
addresses in 1 variant
Does not validate
DNSSEC in our test
None sent
client subnet (ECS)
Addresses Check your resolver

Addresses

Surfshark DNS DNS addresses by variant

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

Surfshark DNS

Not specified by the operator

IPv4
194.169.169.169
IPv6
2a09:a707:169::
DoH
https://dns.surfsharkdns.com/dns-query

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

1/1 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

  • DoH https://dns.surfsharkdns.com/dns-queryAnswered

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

  • AS209854 Cyberzonehub Cyberzone S.A.

Queried from, in our probe

  • AS60068 CDN77 Datacamp Limited

In the operator's words

Operator statements

Quoted from the operator's pages and checked word for word. We have not audited these practices.
“Surfshark B.V., KvK number: 81967985, address: Kabelweg 57, 1014BA Amsterdam, the Netherlands”
surfshark.com

Check it

Confirm your device is using Surfshark DNS

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 @194.169.169.169

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

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

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

Surfshark DNS questions

What are Surfshark DNS's DNS server addresses?

Surfshark DNS: 194.169.169.169, 2a09:a707:169::.

Does Surfshark DNS validate DNSSEC?

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

Does Surfshark DNS support DNS over HTTPS or DNS over TLS?

DoH: https://dns.surfsharkdns.com/dns-query. 1 of 1 answered our test query on 2026-09-24.

Does Surfshark DNS 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 Surfshark DNS?

Run a DNS leak test and compare the network it reports with the one Surfshark DNS queried from in our probe (AS60068). On the command line, dig +short whoami.akamai.net @194.169.169.169 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.

Compare

Other resolvers where DNSSEC does not validate

Comodo Secure DNS

8.26.56.26 · 8.20.247.20

DNSSEC: does not validate

Yandex DNS

77.88.8.8 · 77.88.8.1

DNSSEC: does not validate

AliDNS (Alibaba Cloud Public DNS)

223.5.5.5 · 223.6.6.6

DNSSEC: does not validate

DNSPod Public DNS

119.29.29.29

DNSSEC: does not validate

114DNS

114.114.114.114 · 114.114.115.115

DNSSEC: does not validate

CIRA Canadian Shield

149.112.121.10 · 149.112.122.10

DNSSEC: does not validate
All 20 resolvers

Research library

Network registries & open data

Find the reference behind a network decision. Browse the records, follow their sources and download the available datasets.

Explore research