Skip to content
Log inDashboard

Block page and its certificate

By default opdns answers a blocked name as if it did not exist, and the browser shows its own “site can’t be reached” error. With the block page, the browser shows a page that says the site is blocked and which setting blocked it, in the same words as your logs, for example Privacy › Ads & trackers (step 3 and up). It names your profile only if you turn that on, and shows nothing else: no list names, no addresses, no other details.

  1. In the dashboard, open the profile’s Settings page.

  2. Under Blocked answers, choose Show a block page and save.

  3. Optionally turn on Show the profile name on the block page. Anyone who opens a blocked site on a device using this profile then sees its name.

That is enough for http:// addresses. Most sites use https://, and there the browser expects a certificate for the site’s own name, which opdns does not have. Without the step below, a blocked https:// site shows the browser’s certificate warning instead of the page. Nothing is loaded from the site either way; the warning is only less informative.

To show the page on https:// sites too, a device has to trust a certificate authority made for your profile. It is opt-in, one per profile, and generated by opdns when you ask for it.

How opdns limits that risk:

  • The key is generated by opdns, stored encrypted, and never shown or downloadable. You download the certificate only.
  • The resolvers use it only to issue certificates that last one hour, only for names this profile blocked in the last minute for the device that asked. A name that resolves normally never gets one, so your real connections are never intercepted.
  • You can revoke it at any time. opdns then deletes the key, and blocked https:// sites show the certificate warning again within minutes.
  • It expires two years after you generate it.

Revoking does not remove the certificate from your devices: remove it yourself with the steps below.

  1. On Settings, with Show a block page chosen, click Generate certificate. The dashboard may ask you to confirm your sign-in.

  2. Check the SHA-256 fingerprint shown: it is what your devices show for the certificate.

  3. Download the file for each device: .mobileconfig for iPhone, iPad and Mac, .crt for Windows and Android, .pem for Linux and Firefox.

  1. Open the .mobileconfig file on the device (AirDrop, Files or Safari). iOS says Profile Downloaded.

  2. Open Settings › General › VPN & Device Management, tap the opdns block page profile and tap Install.

  3. Open Settings › General › About › Certificate Trust Settings and turn on full trust for opdns block page (your profile id). Without this step iOS installs the certificate but does not trust it for websites.

  1. Double-click the .mobileconfig file. macOS says the profile is ready to review.

  2. Open System Settings › General › Device Management (on macOS 14 and earlier, System Settings › Privacy & Security › Profiles), select the opdns block page profile and click Install.

  3. If Safari or Chrome still shows a warning, open Keychain Access, find opdns block page in the System keychain, open it, and under Trust set When using this certificate to Always Trust.

Firefox on macOS uses its own certificate list: see Firefox below.

  1. Double-click the .crt file and click Install Certificate.

  2. Choose Current User (only you) or Local Machine (every user of the computer; needs an administrator).

  3. Choose Place all certificates in the following store, click Browse and select Trusted Root Certification Authorities. Finish and confirm the security warning, after checking that the fingerprint matches the one on the dashboard.

Edge and Chrome use it at once. For Firefox, see below.

  1. Open Settings › Security › Encryption & credentials › Install a certificate › CA certificate (the menu names vary by maker; search Settings for “CA certificate”).

  2. Confirm the warning and pick the .crt file you downloaded.

Chrome honours certificates you install this way. Many apps ignore them on purpose (Android does not let apps trust user-installed certificates by default): in those apps a blocked name simply fails to load, as it would without the block page.

Copy the .pem file into the system store and refresh it, for example on Debian and Ubuntu:

Terminal window
sudo cp opdns-block-page-<profile-id>.pem /usr/local/share/ca-certificates/opdns-block-page.crt
sudo update-ca-certificates

On Fedora, copy it to /etc/pki/ca-trust/source/anchors/ and run sudo update-ca-trust. Chrome on Linux uses its own store: import the .pem under Settings › Privacy and security › Security › Manage certificates › Authorities.

Firefox keeps its own list of authorities. Open Settings › Privacy & Security › Certificates › View Certificates › Authorities, click Import, choose the .pem (or .crt) file and tick Trust this CA to identify websites. On Windows and macOS you can instead let Firefox use the system’s certificates: set security.enterprise_roots.enabled to true in about:config.

Remove the certificate from a device whenever you stop using the block page, revoke the certificate, or give the device away.

  • iPhone and iPad: Settings › General › VPN & Device Management, tap the opdns block page profile, Remove Profile.
  • Mac: System Settings › General › Device Management (on macOS 14 and earlier, Privacy & Security › Profiles), select it and click −. If you trusted it in Keychain Access, delete it there too.
  • Windows: run certmgr.msc (or certlm.msc for Local Machine), open Trusted Root Certification Authorities › Certificates, delete opdns block page.
  • Android: Settings › Security › Encryption & credentials › User credentials (or Trusted credentials › User), select it and remove it.
  • Linux: delete the file you copied and run update-ca-certificates --fresh (or update-ca-trust).
  • Firefox: Certificates › View Certificates › Authorities, select it, Delete or Distrust.

To stop opdns using the certificate everywhere at once, click Revoke certificate on the Settings page.

  • Sites with HSTS. Browsers never let you click through a certificate warning on sites that require HTTPS (HSTS), so without the certificate those sites show a warning you cannot bypass. With it installed they show the block page like any other site.
  • The device, not the name. The page appears for the device whose DNS query was blocked, within a minute. If a device’s DNS and web traffic leave from different addresses (for example DNS over IPv6 and the page over IPv4), the page may only say the name is blocked, without the setting.
  • Apps are not browsers. Apps that are not browsers usually show their own connection error rather than the page.
  • Nothing is logged by the page. Opening the block page records nothing; the blocked query itself appears in your logs as usual.