---
title: Gateway block page · Cloudflare Learning Paths
description: With Cloudflare Zero Trust, you can deliver actionable feedback to users when they are blocked by a Gateway policy. Custom block messages can reduce user confusion and decrease your IT ticket load.
lastUpdated: 2025-04-11T17:37:50.000Z
source_url:
  html: https://a74404c8.preview.developers.cloudflare.com/learning-paths/replace-vpn/build-policies/block-page/index.md
  md: https://a74404c8.preview.developers.cloudflare.com/learning-paths/replace-vpn/build-policies/block-page/
---

With Cloudflare Zero Trust, you can deliver actionable feedback to users when they are blocked by a Gateway policy. Custom block messages can reduce user confusion and decrease your IT ticket load.

There are two different ways to surface block messages:

* [Custom block page](#custom-block-page)
* [WARP client block notifications](#warp-client-block-notifications)

## Custom block page

You can display a custom block page in the browser when users are blocked by a Gateway DNS or HTTP policy. This is a static page that educates users on why they were blocked and how to contact IT.

The custom block page has a few drawbacks:

* To display the block page, you must install a [user-side certificate](https://developers.cloudflare.com/learning-paths/replace-vpn/configure-device-agent/enable-tls-decryption/#configure-user-side-certificates) on the end user device.
* The block page does not appear when users are blocked by a Gateway network policy.
* The custom block page only displays when the user loads a site in a browser. If, for instance, the user is allowed to visit a site but not allowed to upload a file, the file upload would fail silently and the user would not get a block page.

To work around these limitations, we recommend using [WARP client block notifications](#warp-client-block-notifications).

Note

The Gateway custom block page is a different concept from [Access custom block pages](https://developers.cloudflare.com/cloudflare-one/applications/block-page/), which are used in conjunction with Cloudflare Access policies.

### Enable the block page for DNS policies

For DNS policies, you will need to enable the block page on a per-policy basis.

1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Gateway** > **Firewall policies** > **DNS**.

2. Select **Add a policy** to create a new policy, or choose the policy you want to customize and select **Edit**. You can only edit the block page for policies with a Block action.

3. Under **Configure policy settings**, turn on **Modify Gateway block behavior**.

4. Choose your block behavior:

   * **Use account-level block setting**: Use the global block page setting configured in your account settings. The global setting can be the default Gateway block page, an [HTTP redirect](https://developers.cloudflare.com/cloudflare-one/policies/gateway/block-page/#redirect-to-a-block-page), or a [custom Gateway block page](https://developers.cloudflare.com/cloudflare-one/policies/gateway/block-page/#customize-the-block-page).
   * **Override account setting with URL redirect**: Redirect users with a `307` HTTP redirect to a URL you specify on a policy level.

5. (Optional) If your account-level block page setting uses a custom Gateway block page, you can turn on **Add an additional message to your custom block page when traffic matches this policy** to add a custom message to your custom block page when traffic is blocked by this policy. This option will replace the **Message** field.

6. Select **Save policy**.

Depending on your settings, Gateway will display a block page in your users' browsers or redirect them to a specified URL when they are blocked by this policy.

### Customize the block page

You can customize the Cloudflare-hosted block page by making global changes that Gateway will display every time a user reaches your block page. Customizations will apply regardless of the type of policy (DNS or HTTP) that blocks the traffic.

To customize your block page:

1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Custom Pages**.

2. Under **Account Gateway block page**, select **Customize**.

3. Choose **Custom Gateway block page**. Gateway will display a preview of your custom block page. Available customizations include:

   * Your organization's name
   * [Logo](https://developers.cloudflare.com/cloudflare-one/policies/gateway/block-page/#add-a-logo-image)
   * Header text
   * Global block message, which will be displayed above the policy-specific block message
   * [Mailto link](https://developers.cloudflare.com/cloudflare-one/policies/gateway/block-page/#allow-users-to-email-an-administrator)
   * Background color

4. Select **Save**.

Gateway will now display a custom Gateway block page when your users visit a blocked website.

## WARP client block notifications

Note

Only available on Enterprise plans.

For more granular user feedback, you can enable WARP client block notifications on any Gateway DNS or Network *Block* policy. Blocked users will receive an operating system notification from the WARP client with a custom message you set.

Client notifications provide additional functionality over the [custom block page](#custom-block-page):

* Client notifications work with network policies, which means you can surface feedback for all partial actions on user traffic including blocking a specific port, file upload, or protocol.

* Client notifications allow you to direct users to a unique link per individual policy. For example, you could link users to your organization's acceptable use policy, data protection policy, or any existing IT troubleshooting infrastructure. If no infrastructure for this exists within your organization, you can quickly deploy an HTML site on [Cloudflare Pages](https://developers.cloudflare.com/pages/), put the site behind a [Cloudflare Access policy](https://developers.cloudflare.com/cloudflare-one/policies/access/), and provide dynamic feedback based on the identity and device posture values found in the user's [Access JWT](https://developers.cloudflare.com/cloudflare-one/identity/authorization-cookie/application-token/).
