Skip to content
Log inDashboard

Profiles

A profile is one filtering policy with its own id, addresses, rules, settings and logs. An account can have several. Every change you make is saved as a new version of the profile and reaches every PoP (server location) within seconds.

The profile switcher at the top of the dashboard lists your profiles. Choose New profile there to create one; the dashboard assigns its id.

The dashboard's profile switcher open, listing three profiles with their ids and the New profile, Duplicate, Rename and Delete actions.

Each profile’s pages follow the same order:

Page What it holds
Setup the profile’s addresses and linked IPs (Your endpoints), and whether the device you are on uses them (Check it works)
Security protections against malicious domains (Security)
Privacy how much the profile blocks, on one five-step slider, and device telemetry per manufacturer (Privacy blocklists)
Parental Control categories, services, SafeSearch (Parental control)
Denylist, Allowlist, Rewrites your own rules (Rules)
Analytics totals, timelines, top lists (Analytics)
Logs live tail and search (Logs)
Settings block answers, logging, resolution (Settings)
Nodes self-hosted nodes (Nodes)
Devices devices seen on the profile (Devices)

A device is known by the name it puts in its encrypted DNS address (device names). There is nothing to register: the first query with a new name creates it, and logs and analytics group by it. Rename or forget devices on the Devices page.

Every profile resource carries its version as an ETag. If you edit the same profile in two tabs, the second save is refused with a message to reload rather than silently overwriting the first. The API works the same way (If-Match, see Errors and limits).

The opdns operators can suspend a profile, for example for a breach of the terms of service. Until it is reinstated:

  • Queries are refused. Every query sent to the profile (its DoH, DoT and DoQ addresses, its linked IPs, its devices and its enrolled self-hosted nodes) gets a REFUSED answer with an Extended DNS Error 15 (Blocked) saying profile suspended, followed by the operator’s explanation when they gave one: profile suspended: <reason>. Tools such as dig show it as EDE: 15 (Blocked): (profile suspended: …).
  • No logging. No query record and no hourly count is written for it, in the cloud or on an enrolled node. Logs already stored stay readable and expire with their retention as before.
  • No changes. Every page that configures filtering (Security, Privacy, Parental Control, Denylist, Allowlist, Rewrites, Settings) is shown read-only, and the API answers changes to the profile, its devices and new nodes with 409 profile_suspended. The profile cannot be deleted meanwhile. Setup, Analytics, Logs, Nodes and Devices stay available to read; you can still revoke a node and send list reports.

Every page of the profile shows a banner: This profile is suspended by the operator; its queries are refused until it is reinstated, with the operator’s explanation when there is one and a note to contact support if you think it is a mistake. The API returns the same explanation as the profile’s suspended_public_reason. The suspension and the reinstatement each appear in Activity (Profile suspended by the operator, Profile reinstated by the operator). The operator also records an internal note, which is never shown in the dashboard, the API, DNS answers or your data export.

An enrolled self-hosted node receives the suspension like any profile change and refuses the profile’s queries the same way. A node release older than v0.1.19 resolves a suspended profile unfiltered instead; upgrade it to get the behaviour above.

How a suspension reaches the PoPs and nodes: Architecture.