DNS resolver registry · LibreDNS

LibreDNS DNS servers

LibreDNS offers one service, reachable over DoT, DoH. Every address and endpoint below is taken from the operator's documentation; the behaviour is what we measured on 2026-09-24.
116.202.176.26
primary address
2
addresses in 1 variant
Does not validate
DNSSEC in our test
Encrypted only
no public plain DNS
Addresses Check your resolver

Addresses

LibreDNS DNS addresses by variant

The operator documents this service over DNS-over-HTTPS and DNS-over-TLS, and plain DNS on port 53 did not answer our probe. Use the encrypted endpoints; the addresses are what those hostnames point to.

LibreDNS

Not specified by the operator

IPv4
116.202.176.26
IPv6
2a01:4f8:1c0c:8274::1
DoH
https://doh.libredns.gr/dns-query
DoT
dot.libredns.gr

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. Tested over the encrypted endpoint.

Client subnet (ECS)

Not measured: this probe used plain DNS, which the operator does not offer publicly.

Plain DNS and NXDOMAIN

The operator documents encrypted service only.

Encrypted endpoints

  • DoH https://doh.libredns.gr/dns-queryAnswered
  • DoT dot.libredns.grAnswered

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

  • AS24940 HETZNER-AS Hetzner Online GmbH

Queried from, in our probe

Not published: encrypted-only service was not part of this test.

In the operator's words

Operator statements

Quoted from the operator's pages and checked word for word. We have not audited these practices.
“Logs are disabled for our DNS daemon.”
libredns.gr
“We use OpenNIC as our Tier 1.”
libredns.gr

Check it

Confirm your device is using LibreDNS

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

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

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

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

LibreDNS questions

What are LibreDNS's DNS server addresses?

LibreDNS: 116.202.176.26, 2a01:4f8:1c0c:8274::1.

Does LibreDNS validate DNSSEC?

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

Does LibreDNS support DNS over HTTPS or DNS over TLS?

DoH: https://doh.libredns.gr/dns-query. DoT: dot.libredns.gr. 2 of 2 answered our test query on 2026-09-24.

How can I check that I am using LibreDNS?

Run a DNS leak test and compare the network it reports. On the command line, dig +short whoami.akamai.net @116.202.176.26 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