Hostname validation

Before Cloudflare can proxy traffic through a custom hostname, we need to verify your customer's ownership of that hostname.

Note

If a custom hostname is already on Cloudflare, using the pre-validation methods will not shift the traffic to the SaaS zone. That will only happen once the DNS target of the custom hostnames changes to point to the SaaS zone.

Options

If minimizing downtime is more important to you, refer to our pre-validation methods.

If ease of use for your customers is more important, review our real-time validation methods.

Hostname validation and certificate validation

Hostname validation and certificate validation use different tokens and API fields.

• ownership_verification and ownership_verification_http validate hostname ownership and affect the custom hostname status.
• ssl.validation_records validates certificate issuance and affects ssl.status.

For production traffic, the hostname should have status: active, ssl.status: active, and DNS that points to your SaaS target.

Limitations

Custom hostnames using another CDN are not compatible with Cloudflare for SaaS. Since Cloudflare must be able to validate your customer's ownership of the hostname you add, if their usage of another CDN obfuscates their DNS records, hostname validation will fail.

Related resources

• Pre-validation
• Real-time validation
• Backoff schedule
• Validation status
• Error codes