Skip to main content

Block Page

The page a user sees when they hit a blocked site — your logo, your wording, your IT contact. Far better than a generic "This site can't be reached", which just generates a support ticket.

Set it up

  1. Enable Block page on the policy first — Secure Access → DNS Filtering → Policy → Block page. Without that switch, blocked lookups return a plain DNS error and this page is never shown.
  2. Go to Secure Access → DNS Filtering → Block Page and fill in:
FieldExample
HeadingAccess blocked
MessageThis website is blocked by your organization's security policy.
Logo URLhttps://…/logo.png
IT emailit@company.com
IT phone+1 555 000 0000
  1. Click Save — you get "Block page saved".

Leave a field empty and it is simply not shown. The IT email and phone are the part users actually act on, so fill at least one.

Write a message people can act on

Say what happened, why, and what to do next:

This site is blocked by company policy. If you need it for work, contact IT at it@company.com with the address you were trying to reach.

Avoid accusatory wording — most blocks are ads, trackers and mistyped domains, not deliberate policy breaches.

HTTP vs HTTPS

The branded page renders for plain HTTP requests. For HTTPS, the browser expects a certificate for the site it asked for, so instead of the branded page the user gets a certificate warning and the connection stops. That is deliberate: DashX does not intercept or decrypt HTTPS, and installing a root CA on every device to fake one is not something we ask of you.

Practically: the site is blocked either way. The branded page appears on HTTP and on any link the user opens over plain HTTP; on HTTPS they see a browser security warning.

Remove the HTTPS warning without intercepting anything

The optional Browser Extension opens your block page immediately on HTTPS too, instead of the certificate warning. It works entirely outside TLS — no certificate authority is installed and nothing is decrypted.

tip

Test it after saving: put a harmless domain in a custom deny rule, open it over http:// from a filtered device, and confirm the page shows your logo and contact details.