Skip to content
Log inDashboard

Operator blocks and takedowns

An operator block is a block that opdns imposes, not one you chose. It applies before any of your profile’s rules, your allowlist included, and also on the unfiltered public path. Because it overrides your choices, the policy is narrow, written down, counted and published. This page summarises it; the policy itself is still a draft, and this page changes with it.

An operator block is always answered NXDOMAIN, whatever your block mode, with Extended DNS Error 15 (Blocked). Blocks from your own profile carry 17 (Filtered), so the two never look alike. The error’s extra text is a reason code, legal_order, abuse or csam, followed for the first two by a public reference such as legal_order LEGAL-2026-014. It never contains the blocked name. See Block answers for how to read it.

Reason Reason code When Where it applies
Legal order legal_order a court or authority order that binds opdns, has been checked as valid, and names opdns or public resolvers as a class the PoPs (server locations) in the country that issued it, unless the order binds us everywhere
Malware abusing our service abuse confirmed command-and-control or similar infrastructure whose traffic through our resolvers harms the service or others, when no profile list can cover it everywhere
Phishing at operator level abuse live phishing of opdns itself, or a mass campaign reported with evidence by a recognised security team everywhere
Operational safety abuse names that break the resolver itself, such as names used in floods against it everywhere, for 30 days at most
Child sexual abuse material csam a name on a designated list from a recognised hotline; no such list is in use today everywhere
  • Copyright or trademark notices without a court order that binds opdns. We host no content, and we forward or block nothing on such a notice.
  • Government or police requests outside formal legal process, including “voluntary” block requests.
  • Commercial disputes between third parties, reputation management, or requests to block a competitor.
  • Blocks that the host, the registrar or the registry could apply more effectively. We send such requests there.
  • Anything you can already choose to block with a profile list, such as ads, trackers, adult content or gambling. That choice is yours, not ours.

A block limited to a country applies on the PoPs in that country. Scoping is by the PoP that answers, not by where you are: a device in that country is normally answered by a PoP there, and one routed to a PoP elsewhere is not blocked. We say so in the transparency report rather than pretend otherwise.

Enrolled self-hosted nodes apply the same blocks, except those limited to a single PoP. Standalone nodes receive none.

Anyone may appeal: the domain’s owner, a user or a researcher. Write to [email protected] with the reference from the error’s extra text.

  • Abuse blocks are checked again within 5 business days. If the evidence no longer holds (the site is clean, the infrastructure is gone), the block is removed.
  • Legal blocks are removed when the order is lifted, expires or is overturned, or when we find on review that it does not bind us. We tell you which authority to address.
  • CSAM entries are not debated by us: appeals go to the list provider, whose address we give.

Every block that is added, changed or removed is recorded with its reason, reference and scope. The transparency report publishes the number of blocks by reason and country, and the number of appeals and their outcome. To report abuse or ask for a takedown, see Reporting abuse.