Skip to content
Log inDashboard

Account

The Account page (the account menu at the top of the dashboard) shows your sign-in address, role and plan, and links to API tokens and Activity. It also holds Preferences, Error reports and Export your data.

You sign in to opdns with your op account, the account shared by the op products. Your email address, password, passkeys, authenticator app, recovery codes, sessions and the deletion of your account are managed on your op account at account.opauth.net; Manage your op account on the Account page takes you there and back.

Creating an API token, starting an export or enrolling a node needs a sign-in within the last five minutes; if it has been longer, the dashboard sends you to sign in again with your op account, then you repeat what you asked.

Sign in and Create your op account both go to opauth.net. The first time you sign in to opdns, an opdns account is created for your op account (or, if you already had an opdns account with the same verified address, linked to it). During the alpha, signing up for opdns needs an invitation: an address approved in advance, or one invited from the waitlist.

Your op account’s password, its second factors and its recovery are set on account.opauth.net.

Security notices (a new sign-in, a changed password or address) come from your op account, from [email protected].

Recover your op account on opauth.net. Signing out of your op account, or ending one of its sessions, signs you out of opdns too.

Account → Activity is your organisation’s audit log, newest first: sign-ins and failed attempts, failed-sign-in emails, password, passkey, authenticator and recovery-code changes, account recovery, sessions signed out, API tokens created and revoked, profiles, linked IPs, nodes added, enrolled and revoked, devices changed, preference changes, exports and deletion, and the list reports you sent. Failures are recorded too:

Entry Means
Password change refused, wrong current password someone tried to change the password without knowing the current one
Wrong second-factor code a wrong code while resetting the password, or while confirming or removing the authenticator app
Authenticator code reused, refused a code that had already been used was sent again; see Password rules

Each entry shows when, what, who (You, another account, an API token, DDNS update or opdns itself), on what, and its details (such as the address and browser). When an account of your organisation acted, directly or through one of its API tokens, its email address is shown first. A profile change records what changed: each setting with its old and new value, and the rules or lists added and removed (up to 20 of each). Load more fetches older entries.

The filters above the log narrow it: Who takes an email address (that account’s entries and its API tokens’), What a group of actions (sign-in and credentials, API tokens, profiles, nodes and so on), and From and To a range of days, both included. The filters stay in the page’s address, so a filtered view can be bookmarked. Export CSV downloads the entries the filters select, newest first, up to 10,000 at a time: when, the action and its description, the actor and its email, the target and the details as text.

If you see something you do not recognise, change your password and sign out the other sessions on Security. The same log is in the export and at GET /v1/auth/audit (scope account:read, with actor, action, from and to filters).

Email me when a self-hosted node goes offline sends the node offline and back online emails. It is on by default and saves as soon as you flip it. Only owners receive these emails; other members see a note saying so. The switch is read-only while a deletion is pending. With the API: GET and PATCH /v1/auth/me/preferences ({"alerts":{"node_offline":false}}), with a session.

When the dashboard crashes it can tell opdns what broke. Send error reports from this browser turns that off for this browser. A report holds the dashboard version, the page with ids removed, and the error and where in the code it happened: never domain names, IP or email addresses, or profile settings. Only some errors are sent (about half, at most five per page load, no duplicates), and nothing reaches a third party.

Account → API tokens → New token creates tokens for the API, each with a name, the scopes it may use (each box says what the scope allows; Read only and Select all tick several at once) and an optional expiry date. A token outlives the session that made it, so creating one needs a sign-in within the last five minutes: if it has been longer, the dashboard asks you to confirm, then creates the token. The secret (opdns_…) is shown once. The list shows each token’s scopes, when it was last used and when it expires (or expired). See Authentication for what each scope allows, and Rate limits for the requests a minute your tokens share.

Export your data builds a zip of everything opdns holds about you:

File Holds
README.md, manifest.json what each file holds; log row counts per profile, and whether a profile’s logs were cut at the row limit
account.json your account and sign-in methods (passkey names and dates, recovery codes left) and every version of the terms of service you accepted, with the date; never password hashes, seeds or keys
sessions.json your sessions (device, address, sign-in method); never session secrets
tokens.json API token metadata (names, scopes, dates; never the secrets)
audit_log.ndjson your account’s audit log
profiles.csv, rules.csv, devices.csv your profiles, their rules (disabled ones included) and devices, one table each, for spreadsheets
logs_summary.csv per profile, how many log rows the archive holds, the period they cover and whether they were cut
profiles/<id>/profile.json the profile document, in the format a standalone node loads: opdns-node import-export <archive> --profile <id> installs it as the node’s profile file
profiles/<id>/metadata.json, rules.json, linked_ips.json the profile’s name and dates, its rules, its linked IPs
profiles/<id>/devices.json, nodes.json its devices with their display names, and its self-hosted nodes
profiles/<id>/logs.csv its cloud query logs within retention, newest first, a header row then one row per query, up to a row limit per profile. Fields you chose not to log were never stored, so they are not here either

The archive is built in the background. You get an email when it is ready, and the download stays available for 24 hours. You can have one export in progress and start one a day. Logs held only on a self-hosted node are not in it; they are in the node’s own SQLite file.

The same export is available through the API (POST /v1/auth/me/export, with a session only). If you cannot sign in, you can also ask for your data by email; see Your rights in the privacy policy.

Delete your op account on account.opauth.net. When you ask, your opdns account is scheduled for deletion at the same time:

  • every opdns session and API token is revoked, so you are signed out;
  • your profiles stop filtering: devices that still use them get unfiltered, unlogged answers, as if they named no profile;
  • your self-hosted nodes are revoked and disconnected. They keep their local data; erase it on the node;
  • log batches waiting for your nodes are discarded.

Until the date your op account gives, you can cancel the deletion there: your profiles are restored and resolve again. Sessions, API tokens and nodes stay revoked; enrol your nodes again. Download an export first if you want a copy.

Then your opdns account, your profiles’ configuration and their query logs (including the hourly counters) are erased. Entries in the audit log are kept with your identity removed. Backups are not edited; the copies in them expire within 30 days for account data and 120 days for query logs. Profile ids are never reused.

An account whose organisation has other members is not erased this way. For that case, and for anything else about your data that the dashboard does not do, see Your rights in the privacy policy.