DNS resolver registry · Yandex

Yandex DNS DNS servers

Yandex DNS offers 3 service variants with different filtering, reachable over DNS (53), DoT. Every address and endpoint below is taken from the operator's documentation; the behaviour is what we measured on 2026-09-24.
77.88.8.8
primary address
12
addresses in 3 variants
Does not validate
DNSSEC in our test
None sent
client subnet (ECS)
Addresses Check your resolver

Addresses

Yandex DNS DNS addresses by variant

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

Yandex DNS Basic

Not specified by the operator

IPv4
77.88.8.8
77.88.8.1
IPv6
2a02:6b8::feed:0ff
2a02:6b8:0:1::feed:0ff
DoT
common.dot.dns.yandex.net

Yandex DNS Safe

Dangerous websites

IPv4
77.88.8.88
77.88.8.2
IPv6
2a02:6b8::feed:bad
2a02:6b8:0:1::feed:bad
DoT
safe.dot.dns.yandex.net

Yandex DNS Family

Dangerous websites and adult content

IPv4
77.88.8.7
77.88.8.3
IPv6
2a02:6b8::feed:a11
2a02:6b8:0:1::feed:a11
DoT
family.dot.dns.yandex.net

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

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

  • DoT common.dot.dns.yandex.netAnswered
  • DoT safe.dot.dns.yandex.netAnswered
  • DoT family.dot.dns.yandex.netAnswered

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

  • AS13238 YANDEX YANDEX LLC
  • AS208398 TELETECH Edge Technology Plus d.o.o. Beograd

Queried from, in our probe

  • AS13238 YANDEX YANDEX LLC
  • AS208398 TELETECH Edge Technology Plus d.o.o. Beograd

Check it

Confirm your device is using Yandex 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 @77.88.8.8

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

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

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

Yandex DNS questions

What are Yandex DNS's DNS server addresses?

Yandex DNS Basic: 77.88.8.8, 77.88.8.1, 2a02:6b8::feed:0ff, 2a02:6b8:0:1::feed:0ff. Yandex DNS Safe: 77.88.8.88, 77.88.8.2, 2a02:6b8::feed:bad, 2a02:6b8:0:1::feed:bad. Yandex DNS Family: 77.88.8.7, 77.88.8.3, 2a02:6b8::feed:a11, 2a02:6b8:0:1::feed:a11.

Does Yandex DNS validate DNSSEC?

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

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

DoT: common.dot.dns.yandex.net, safe.dot.dns.yandex.net, family.dot.dns.yandex.net. 3 of 3 answered our test query on 2026-09-24.

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

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

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

SafeDNS

195.46.39.39 · 195.46.39.40

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