Skip to content
Log inDashboard

Your endpoints

Every profile has its own addresses. The dashboard’s Setup page shows them for your profile, computed by the API (endpoints on the profile resource).

The guides are written once for everyone, so they use two placeholders. The dashboard’s Setup page fills them in for you.

Placeholder Means Example
<profile-id> Your profile’s 6-character id: lowercase letters and digits abc123
<device> A name you choose for the device Pixel-8, living-room-tv

Device names are optional. The resolver keeps ASCII letters (lowercased) and digits, turns spaces, dots, underscores and hyphens into a single hyphen, drops everything else, and keeps at most 32 characters. Anna's iPad becomes annas-ipad. Use the same name on the same device every time: the name is what logs and analytics group by.

Transport Address Identifies
DNS-over-HTTPS (HTTP/2 and HTTP/3) https://dns.opdns.net/<profile-id>/<device> profile and device
DNS-over-TLS (port 853) <device>-<profile-id>.dns.opdns.net profile and device
DNS-over-QUIC (port 853) <device>-<profile-id>.dns.opdns.net profile and device
Plain DNS over IPv6 the profile’s own IPv6 address in 2602:81f:6000::/48, shown on the Setup page profile only
Plain DNS over IPv4 the shared addresses 23.166.164.53 and 23.166.164.35, with your network’s IPv4 linked profile only

Without a device name, drop the last path segment (https://dns.opdns.net/<profile-id>) or the <device>- prefix (<profile-id>.dns.opdns.net).

These are the same for everyone. dns.opdns.net points to the first address of each family, so encrypted DNS connects to them, and they are what you enter where a setting asks for a DNS server address:

First Second
IPv4 23.166.164.53 23.166.164.35
IPv6 2602:81f:6000::53 2602:81f:6000::35

Use the second address where a setting asks for two DNS servers; both reach the same resolver. With encrypted DNS, the host name or path still selects your profile, whichever address the device connects to.

For plain DNS (no encryption), the addresses work differently:

  • IPv4: 23.166.164.53 and 23.166.164.35 use your profile only from a linked network.
  • IPv6: 2602:81f:6000::53 and 2602:81f:6000::35 name no profile, so plain DNS to them is answered unfiltered (the public path). Use your profile’s own IPv6 address from the Setup page instead.

All of these addresses, and every profile’s IPv6 address, are in opdns’s own address space: see Our network.

Prefer encrypted DNS: DNS-over-HTTPS in browsers and on Windows, iOS and macOS; DNS-over-TLS for Android’s Private DNS and for Linux and routers. Both carry a device name and work on any network.

Use plain DNS only where nothing else is possible, typically a router’s DHCP settings for devices you cannot configure one by one. Plain DNS is not encrypted and cannot name devices. See Identification for the full rules.

Some apps take a DNS stamp instead of an address: one sdns:// string that holds the server’s address, its host name, the path for DNS-over-HTTPS and a few properties. The dashboard’s Setup page shows one stamp per encrypted transport, next to the addresses above, each with a copy button. Name a device on that page first and the stamps carry it, exactly like the device addresses.

App Stamps it takes
dnscrypt-proxy, Simple DNSCrypt (Windows) DNS-over-HTTPS (they have no DNS-over-TLS or DNS-over-QUIC)
AdGuard apps, AdGuard Home DNS-over-HTTPS, DNS-over-TLS, DNS-over-QUIC
YogaDNS stamps are accepted; check which transports your version supports

With dnscrypt-proxy, put the stamp in a static entry and name it in server_names:

server_names = ['opdns']
[static.'opdns']
stamp = 'sdns://...' # the DNS-over-HTTPS stamp from the Setup page

What a stamp holds:

  • Host name and path: the same values as the addresses above (dns.opdns.net with the path /<profile-id>/<device> for DNS-over-HTTPS, <device>-<profile-id>.dns.opdns.net:853 for DNS-over-TLS and DNS-over-QUIC). The port 853 is always written out, because apps disagree on the default.
  • Address: the first shared IPv4 address, 23.166.164.53, so the app connects without first looking up the host name over plain DNS. The host name is still what the certificate is checked against. A stamp copied before opdns moved to these addresses holds the old one: copy it again from the Setup page.
  • Properties: DNSSEC is always set (the resolver validates). No logs is set only while the profile’s logs are off in Privacy. No filter is never set: opdns filters. The properties are taken from the profile when you copy the stamp; an app keeps the stamp it was given, so if you turn logs on later, copy the stamp again.
  • No certificate hashes: the resolver’s certificates are renewed regularly, and a pinned hash would stop the stamp from working at the first renewal.

dnscrypt-proxy’s default require_nolog and require_nofilter apply to servers from its public lists, not to a static entry, so a stamp from the Setup page works with the default configuration.

A wrong id does not fail loudly. These are answered as the unfiltered public path, the same as the bare dns.opdns.net with no id:

  • a well-formed profile id that does not exist;
  • a DNS-over-TLS or DNS-over-QUIC server name that does not hold a well-formed id (five or seven characters, say, or a device name joined without the hyphen).

The device keeps resolving, but nothing is filtered or logged. A DNS-over-HTTPS path that is not a profile id gets HTTP 404 instead. So copy the id from the Setup page rather than typing it, and after any setup, check it works.