Threat research, deployment guides, the API, what shipped last week — all the materials your security team will actually use.
A teardown of three active PhaaS kits and how olladns’s phishing model catches them within hours of registration.
The first-principles case for moving phishing and malware controls left, to the resolver. With references.
Live walkthrough of a 14-site enterprise rollout, with the rollback plan, the diff, and the “oh no” moment.
The 24 questions to answer before you touch your first resolver, plus the templates we hand to enterprise customers.
How we caught a coordinated C2 ring across 38 customers in under four minutes, using DGA + timing signals.
Step-by-step of how a 9-clinic medical group deployed olladns without OR disruption.
What we’ve learned about how quickly phishing infrastructure spins up — and how to keep pace.
Manage policies, sites, lists, and integrations as code. With a 12-line example to get you started.
Our anycast network rerouted around two failing roots in 11 seconds. Here’s the post-mortem and what we changed.
We’re hiring engineers who care more about reducing FPs than shipping models. Here’s the work.
Everything you need to deploy, integrate, and build on olladns.
Point your first resolver, deploy your first roaming client, see your first block.
Read guideEvery endpoint. Auth tokens, rate limits, pagination, and SDKs in Go, Python, and TypeScript.
Open API docsManage policies, sites, and lists as code. Drift detection on every plan.
View providerJamf, Intune, Kandji, Workspace ONE — silent deploy guides for every MDM.
Setup guidesStream every query to Splunk, Sentinel, Datadog, or Elastic in minutes.
Read connectorsConnect Entra ID, Okta, or Google. SCIM provisioning, group mapping.
Read identityReal-world policies: CIPA, HIPAA-safe, financial-services hardened, MSP defaults.
Open cookbookQuery DSL, time windows, regex, exports. The reference for our search.
Read searchWhat shipped, when. Subscribe to changelog · RSS
We host the most sensitive layer of your network. Here’s how we earn it.
Observation period in progress. Report expected Q3 2026 under NDA. Until then, our posture page has the unvarnished current state.
Not yet certified. On the roadmap after SOC 2 lands. We don't claim it elsewhere on the site — if you see it, that's a copy bug; tell us.
Not offered today. We only see DNS query names (not payloads), and per-tenant client-IP anonymization is real — but a signed BAA isn't on the table yet. Tell us if it's a hard requirement.
DoH on every resolver. TLS 1.3 minimum, Let's Encrypt cert rotation.
Single US region today. EU and APAC regions on the multi-region roadmap; until they ship, all data lives in our US LXC.
No formal bug-bounty program yet. Reports welcome via security-policy.html — we acknowledge within one business day. Paid program lands after SOC 2.
Our engineering team answers technical questions directly. No SDRs in the middle.