What is UncensoredDNS and what does its blog cover?

UncensoredDNS is a free, uncensored DNS service run by Thomas Steen Rasmussen as a private project funded with his own money. It provides two public DNS servers — an anycast node and a unicast node — and its blog is where the operator posts project news: new protocol support, server shutdowns, outages, and milestones. If you want a DNS resolver that doesn't filter queries, or you want to track the operational history of this specific service, the blog is the primary source.

What the service actually provides

The homepage lists two resolvers, each reachable over several protocols:

Two things follow from this table:

• The service is encrypted-DNS oriented. Cleartext port 53 lookups (TCP and UDP) were turned off in September 2022, after being announced in February 2022. So if you're configuring a device, use DoT or DoH, not a plain resolver address.
• The anycast node is the one to prefer for general use, since it answers from multiple locations. The unicast node is a single host in Copenhagen, which makes it a reasonable secondary or a choice if you specifically want a Danish endpoint.

The service is described as available to anyone, free of charge. The site does not publish pricing tiers or account requirements, and nothing in the material suggests a paid plan exists.

What the blog covers

The blog is an operator's changelog, not a tutorial site. Its posts fall into a few recurring categories:

Protocol and feature support. The most recent post (October 23, 2025) announces full support for QUIC-based DNS lookups over UDP/853 — DNS-over-QUIC (DoQ, RFC 9250) and DNS-over-HTTPS over HTTP/3 (DoH3). If you're choosing a resolver for a client that supports DoQ or DoH3, this is the post that tells you the service is ready for it.

Infrastructure changes. "Kracon Anycast Node Shut Down" (October 24, 2024) notes a sponsored anycast node was permanently retired. "Moving Day Coming Up" (January 23, 2022) warned that the unicast server was relocating within one to two weeks, with expected downtime. These posts matter if you hard-coded an IP address rather than a hostname.

Outages and incidents. "IPv6 Issues for Unicast / Telia" (February 15, 2021) documents IPv6 failing for the unicast server starting at 01:57 CET that day. This is the kind of post to check when a resolver stops answering and you want to know whether it's you or the service.

Milestones and service policy. "Celebrating 15 Years of UncensoredDNS" (October 23, 2024) marks the project's anniversary. "Cleartext DNS Turned Off" (September 1, 2022) and its February 2022 precursor explain the decision to drop port 53 — the reasoning given is the unfriendly state of the internet, i.e. moving users toward encrypted transports.

How to use this in practice

• Setting up a device: use the DoT or DoH hostname rather than the bare IP, so that if a node moves you aren't left pointing at a dead address. The 2022 relocation post is the concrete reason for this habit.
• Checking whether an outage is yours: look at the most recent blog posts before debugging your own configuration. The IPv6/Telia post is an example of a problem that was on the service side.
• Deciding whether the service fits: it is a one-person, self-funded project with no filtering. That means no commercial SLA and no support contract — the blog is effectively the status channel. If you need guaranteed uptime or vendor support, that's a reason to look elsewhere; if you want an unfiltered resolver with published operational transparency, the blog gives you the history to judge it.
• Following updates: the site points to the @censurfridns account on Twitter for project updates, in addition to the blog itself.

One caveat worth stating plainly: the blog records changes after the fact, so it is a historical record and an announcement channel, not a real-time status page. For a live check, query the resolver directly.