A DNS filter blocks ads, trackers and malware for every device on a network. The hosted ones have years of forum threads and feature requests behind them, and MoatDNS starts from reading those. It’s aimed at people who already use NextDNS, with an import for their existing setup.
Before building the filter, I’m finding out whether anyone wants it.
The page
Static HTML. No framework, no web fonts, no analytics. A privacy product shouldn’t open by phoning home. The hero is a mock query log, with Allow and Block buttons on each line, which shows what the product does faster than a paragraph would.

The waitlist
A Cloudflare Worker of about 150 lines handles one route, POST /api/waitlist, and writes to D1.
Everything else is served straight from static files.
- The form works without JavaScript: a plain POST, then a redirect back to the page.
- Signing up again updates your answers, and the response is identical either way, so nobody can use the form to check whether an address is already on the list.
- A hidden “website” field catches bots and tells them they succeeded.
- Step two asks two optional questions: what you use now (six choices) and which of eight features you’d want. The second is really a vote on what to build first.
- The country column comes from Cloudflare. It’s there to decide where the first servers go.
Next
A launch email, which doesn’t exist yet. Turnstile, if bots get past the hidden field. A privacy policy before EU signups pile up. Then, depending on the list, the filter.