Custom domain with Cloudflare

If your domain is using Cloudflare's Nameservers and you plan to use it as a custom domain on your status page, you may need some minor steps to ensure the domain will work correctly.

Without Proxy (DNS only)

This is the recommended way to guarantee the speed and reliability of your domain since the DNS resolution will go directly to Vercel (Instatus host) without an intermediary.

You can do this on most registrars by doing the following steps:

• Go to your domain settings page.
• Manage DNS.
• Add a record.
• Choose CNAME record type.
• Choose the HOST. Typically status, but you can choose any host, and it'll be your subdomain.
• Points to will be: cname.instatus.com
• Leave the TTL as the default value

With Proxy

A Cloudflare proxy works as an intermediary between your domain and Vercel, which is Instatus hosting provider. We don't recommend that you enable the Cloudflare proxy unless you have specific constraints for your project since it will introduce a minor performance penalty to your website due to the additional hop.

You need to insert a CNAME or ALIAS record with the value cname.instatus.com If your domain does require the Cloudflare's proxy to be turned on by default, only one requirement is needed: The domain must allow HTTP requests (without HTTPS) to the path /.well-known/*.

To verify if that is possible with your domain, you can run the following command (notice the http:// part in the URL):

curl http://example.com/.well-known/acme-challenge -I

A configuration that does allow Vercel (Instatus host) to run smoothly would return the following:

curl http://example.com/.well-known/acme-challenge -I
HTTP/1.1 404 Not Found

If you run the curl command and receive a 3XX redirect instead, Cloudflare is preventing this route from being accessed, and the domain won't be configured correctly:

curl http://example.com/.well-known/acme-challenge -I
HTTP/1.1 308 Moved Permanently

You need to explore the following configuration in the Cloudflare dashboard:

Page Rules — You can disable HTTPS for the path /.well-known/**.

Always use HTTPS — This configuration is under the "SSL/TLS" tab and it may affect your page rules.

Other Configurations — Cloudflare can offer multiple settings and this will directly affect the ability to generate certificates.

The first visit may take a bit to load, then it'll work perfectly!