UncensoredDNS Server Addresses and Supported Protocols

UncensoredDNS provides two public DNS resolvers — an anycast service and a unicast node — reachable over DNS-over-TLS, DNS-over-HTTPS, and (since October 2025) QUIC-based DNS. The service is run by Thomas Steen Rasmussen as a private project and is described on the site as available for anyone to use, free of charge. Below are the exact endpoints and what each one supports.

Server endpoints

The anycast address is served from multiple locations. The unicast node is hosted at AS9167 in Copenhagen, Denmark, so latency from outside Europe will generally be higher on that endpoint.

Supported protocols

DNS-over-TLS (DoT)

• Anycast: anycast.uncensoreddns.org:853
• Unicast: unicast.uncensoreddns.org:853

DNS-over-HTTPS (DoH)

• Anycast: https://anycast.uncensoreddns.org/dns-query
• Unicast: https://unicast.uncensoreddns.org/dns-query

DNS-over-QUIC (DoQ) and DoH3

A blog post dated October 23, 2025 states that UncensoredDNS fully supports QUIC-based lookups over UDP/853 — DoQ (RFC 9250) and DoH3. The same hostnames and IP addresses above apply; only the transport changes.

Cleartext DNS

Cleartext port 53 lookups (TCP and UDP) were turned off on September 1, 2022, following an earlier announcement in February 2022. Port 5353 cleartext was also discontinued. If you are configuring a device that only speaks plain DNS on port 53, these servers will not answer — you need a client that supports DoT, DoH, DoQ, or DoH3.

Choosing between anycast and unicast

• Use anycast if you want the resolver closest to you and the most resilient routing. It is the better default for most users.
• Use unicast if you specifically want the Copenhagen node, for example to compare behavior or to test a single fixed location. Expect downtime notices around host moves; the blog recorded a relocation in early 2022 and an IPv6 outage on the unicast node in February 2021.

Configuration notes and common snags

1. Pick a protocol your client supports. Modern browsers and operating systems handle DoH; routers and stub resolvers more often handle DoT. DoQ/DoH3 needs a client built against those RFCs.
2. Use the hostname, not just the IP, for TLS-based protocols. DoT and DoH rely on certificate validation against the hostname, so entering a bare IP will typically fail.
3. Expect no fallback to port 53. If your DoT/DoH configuration is wrong, resolution fails outright rather than silently downgrading to cleartext.
4. Check the blog for status. Node shutdowns and outages are announced there — for example, the Kracon anycast node was shut down permanently on October 24, 2024, and the unicast node had IPv6 problems in February 2021.

What the blog covers

The UncensoredDNS blog is the project's status and announcement channel. Recurring topics include protocol support changes (DoQ/DoH3, the cleartext shutdown), infrastructure changes (anycast node shutdowns, unicast relocations), outages, and project milestones such as the 15-year anniversary post in October 2024. For updates between posts, the site points to the @censurfridns account on Twitter.