Skip to content

Commit fe9e26c

Browse files
Add refresh validation option to status page
1 parent 5d64e27 commit fe9e26c

File tree

1 file changed

+6
-0
lines changed
  • src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation

1 file changed

+6
-0
lines changed

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/validation-status.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,3 +19,9 @@ When you [validate a custom hostname](/cloudflare-for-platforms/cloudflare-for-s
1919
| Blocked | Custom hostname cannot be added to Cloudflare at this time. Custom hostname was likely associated with Cloudflare previously and flagged for abuse.<br/><br/>If you are an Enterprise customer, contact your Customer Success Manager. Otherwise, email `[email protected]` with the name of the web property and a detailed explanation of your association with this web property. |
2020
| Moved | Custom hostname is not active after **Pending** for the entirety of the [Validation Backoff Schedule](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/backoff-schedule/) or it no longer points to the fallback origin. |
2121
| Deleted | Custom hostname was deleted from the zone. Occurs when status is **Moved** for more than seven days. |
22+
23+
## Refresh validation
24+
25+
To run the custom hostname validation check again, select **Refresh** on the dashboard or send a `PATCH` request to the [Edit custom hostname endpoint](/api/resources/custom_hostnames/methods/edit/) with an empty body.
26+
27+
If the hostname is in a **Moved** or **Deleted** state, the refresh will set the custom hostname back to **Pending validation**.

0 commit comments

Comments
 (0)