olladns is a multi-tenant DNS filtering platform built API-first and MCP-native. Block phishing, malware C2, DGA, and brand typosquats at the resolver. Configure every policy from your terminal, your CI pipeline, or Claude. The dashboard is read-only on purpose.
olladns shipped v0.34 in May 2026 and is looking for 3–5 design-partner teams — AI-native B2B startups (3–50 engineers) and Indian mid-market security teams — who'll trade aggressive product feedback for free Pro tier through 2026 and influence over the roadmap. Apply →
Every serious DNS filter does ~80% of the same things. The 20% that differs is whether your team configures it through a console, through code, or through an AI agent. olladns is the third one. Every policy, every device, every audit event is a REST endpoint and an MCP tool. The dashboard shows you what's happening; it doesn't let you change anything. Configuration goes through versionable, auditable, scriptable APIs — gated by scoped tokens per workload. The classifier that decides whether to block a domain is ~280 lines of feature-based Rust you can read.
NextDNS, ControlD, Cisco Umbrella all treat the dashboard as the source of truth. We inverted that at v0.19. The console is read-only by design. Config changes are commits, not clicks. Every change carries an actor (user_id or specific api_key_id) in the audit log. Zero drift, every change attributable.
REST API docsmcp.olladns.com exposes 49 Model Context Protocol tools auto-generated from our OpenAPI spec. Connect Claude, Cursor, Cline, Continue, Goose — your AI agent operates olladns under the same scoped tokens your humans use. Every tool call lands in the audit log. Nobody else in DNS-filtering ships this today.
Our DGA classifier is ~280 lines of feature-based Rust (entropy + n-gram + vowel ratio). Our typosquat detector is ~230 lines of Damerau-Levenshtein with Cyrillic homoglyph normalization. Both run inline at ingest with zero per-query vendor cost. Stacked on 86 community blocklists across 15 categories.
Threat Intel docsEvery number below verifiable in git log or by hitting an endpoint. No claims we can't back.
Keep your custom rules in git. On merge, your CI runs curl -X PUT api.olladns.com/api/v1/policies/custom-rules. Diff between staging and prod. Roll back via revert. Same scoped token per environment.
Connect once in mcp.json. Ask your editor: "Show me every DGA-flagged domain in the last 24h with score ≥ 0.85 and block them." Three tool calls; one approval; landed in the audit log under your agent token.
Every audit event posts to your endpoint with HMAC-SHA256 signature, timestamp header, and event-name header. Subscribe to policy.* for change-tracking, threat.* for live detection alerts, * for everything.
Read this before you evaluate us. We'd rather lose the deal at the top of the funnel than waste your procurement team's time at the bottom.
api.olladns.com/version returns the git SHA of what's actually running.ctrld Go agent (3 weeks of work, decision locked). Until then, point any DoH-capable client at your tenant's DoH URL.No demo theatre. A real evaluation: we set up your tenant, you point a single laptop or router at your DoH URL, and you tell us what's missing. Bring real DNS traffic if you can; the analytics populate within the hour. The first three teams who commit to weekly feedback get unlimited usage through end of 2026 plus quarterly roadmap input.
Or just try the API yourself: curl https://api.olladns.com/version