HTTP

import { Details, Render } from "~/components";

When you choose HTTP DCV, Cloudflare automatically adds a verification HTTP token to your domain.

Only use this method if your domain can tolerate a few minutes of downtime.

:::note

If you encounter issues with HTTP DCV, refer to the troubleshooting guide.

:::

Limitations

HTTP DCV is only available for proxied domains. It is possible to manually add the DCV token to the .well-known/pki-validation/ directory on your origin web server to pre-validate your certificates.

HTTP DCV validation does not work for wildcard certificates. If you want to use wildcard certificates, use TXT validation.

Based on your chosen certificate authority (CA), you may also not be able to use HTTP verification with advanced certificates.

Setup

Specify DCV method

In either case, you would need to set a "validation_method":"http" parameter.

Review other Cloudflare settings

To make sure your domain does not accidentally block HTTP DCV, review your Cloudflare settings for common setup issues.

Complete DCV

Your HTTP token will be available for the certificate authority as soon as you finish your partial domain setup.

This means that you need to add a CNAME record to Cloudflare in your authoritative DNS and create proxied DNS records for your hostname within Cloudflare.

This process may involve a few minutes of downtime.

Renewal

If the conditions are met but HTTP DCV fails successively, the process will fall back to TXT. This schedule varies according to the certificate validity period.