Ozy-666
DNS Infrastructure · Independent
Public specification — rev. 2026.06
A personal project · open to everyone

I run a public DNS resolver that keeps you private.

Hi, I'm Ozy-666. Building and running DNSDOH.ART is a personal project — an encrypted DNS resolver that blocks ads & trackers and keeps your lookups private from your internet provider. It costs nothing, the code is open, and there's no company or catch behind it. I'm not selling anything — I just think this should exist.

What is this?
§1

What it actually does

Every time you open a website, your device looks up its address — like a phone book for the internet. DNSDOH.ART does that lookup for you, but privately and cleanly. Here's what it does:

Blocks ads & trackers

Ads, trackers, and known malicious sites are stopped before they ever load — in every app on your device, not just your web browser.

Private by default

Your lookups are encrypted, so your internet provider (or the café Wi-Fi) can't see which websites you visit or sell that history.

Often faster

With less junk to download and answers served in a fraction of a millisecond, pages frequently feel snappier — not slower.

No cost, no logs

No account, no app on most devices, no cost — and nothing about your activity is recorded or stored. It runs entirely in memory.

How do I use it? Pick your device, copy one address into its DNS / "Private DNS" setting, and you're protected everywhere. The guides cover phones, laptops, and routers step by step.

Set it up →
Built to be reliable
§2

Measurements — small, but steady under load

It runs on a single, carefully-tuned server — and stays steady even under heavy traffic, while keeping CPU and memory use low. The numbers below come from synthetic stress testing, well past everyday use.

Lookups per second8,000sustained · ≈600× normal load
Answered correctly100%zero dropped under that load
Logs kept0memory-only, nothing saved
The resolver
§3

DNSDOH.ART

This is the resolver itself: public, no-logs, and open-source. It works with every modern connection type, and you don't need any technical knowledge to point your device at it.

CostNoneno account · no app needed
Logs kept0nothing recorded, ever
TransportsDoH · DoT · DoQ · H3phone · laptop · router
Under the hood
§4

The engine — I built it too

You don't need to read any of this to use the service — but if you're technical, here's the open-source work behind it. I rewrote the core DNS software to be faster and leaner, and every change is proven with real benchmarks (not guesses) before it ships.

4.1AdGuardHome-edge
24.6 MB · −10 MB bloat

The brain of the service. I stripped ~13k lines of anything that leaks data or wastes time (DHCP, cloud lookups, client-subnet), rebuilt the request pipeline to allocate nothing, and made the hot paths lock-free so it holds up under flood. A built-in front cache means most repeat lookups never travel further than this box.

0-alloc pipeline · lock-free serve path · front-cache +60% · −13k LOC
github.com/Ozy-666/AdGuardHome-edge-spec →
4.2dnsproxy
+101% throughput

How requests travel in and out. I rebuilt the UDP and TCP paths to allocate nothing, made upstream timing lock-free, and pooled connections instead of reopening one per query — then spread the listener across every CPU core. It also caps QUIC streams and DoH request sizes so a single client can't exhaust it.

0 allocs/op · lock-free RTT map · SO_REUSEPORT · flood caps
github.com/Ozy-666/dnsproxy →
4.3dnscrypt-proxy
0 vulnerabilities

The part that encrypts your DNS on its way out to the wider internet. I rebuilt its busy paths to allocate nothing, made server-selection lock-free, and stripped everything that phones home — the web UI, auto-updates, and remote list downloads. Then had it security-audited; it now rejects forged upstream replies too.

0 allocs/op · lock-free WP2 · −455 KB · audited
github.com/Ozy-666/dnscrypt-proxy →
4.4urlfilter
248× faster

The list-matcher that decides what's an ad or tracker. I changed how it indexes its trickiest rules (regular expressions) so they're found instantly instead of scanned one by one — closing a path attackers could use to slow it down with floods of fake subdomains. The lookup allocates nothing, and I verified the rebuilt engine returns identical results to the original across 39,983 real domains plus 130,000 fuzz runs.

O(1) regex matching · 0 allocs · 0 divergences verified
github.com/Ozy-666/urlfilter →
4.5Unbound + BoringSSL
−26% latency · +9.6%

The resolver that finds each address and proves it's genuine. Checking those security signatures was eating nearly half the server's effort, so I rebuilt Unbound on Google's faster, formally-verified math library (BoringSSL) — keeping a one-command undo ready in case anything misbehaved.

Statically-linked BoringSSL · full DNSSEC validation
AdGuardHome-edge-spec · §6.6 Unbound×BoringSSL →
The journey of a request
§5

Encrypted from start to finish

When you look up a website, your request stays protected the whole way — each step has one job, and your data never travels in the open.

Your device
asks privately
Secure door
decrypts safely
Filter
blocks the junk
Verify
checks it's genuine
Encrypt out
private to the web
Being honest
§6

How this compares to the big resolvers

Cloudflare's 1.1.1.1 and Quad9 are the public resolvers most people know. They're genuinely excellent — and I'm not pretending to match them. Here's the honest difference.

The big public resolvers

They run on global anycast networks — hundreds of locations worldwide, so a server is always physically close to you. That reach is their real strength, and it's not something one person can replicate.

This one

DNSDOH.ART is one carefully-tuned server. The goal was never to out-scale them — it was to make a single node that's genuinely stable and reliable, with zero tolerance for DDoS and abuse: strict rate-limiting, a hardened firewall, and an engine that stays fast under pressure. And unlike a big company, every line of how it works is open to read.

How I work
§7

The way I build things

7.1Verify on real CPUs

Every speed claim is measured on real production hardware with proper tools — never guessed, never tested on a laptop.

7.2Honest about results

When an idea doesn't actually help, I write that down too. The wins and the dead-ends are both documented in the open.

7.3Privacy first

Anything that could leak what you do is removed by default. No telemetry, no tracking, nothing kept on disk.

7.4Always reversible

Every change can be switched off in one step. If something ever acts up in production, it's undone instantly — no drama.