Certificate and hostname priority
When a new certificate is created, Cloudflare first deploys the certificate and then serves it.
For any given hostname, Cloudflare uses the following order to determine which certificate (and associated TLS settings) to apply to that hostname:
Hostname specificity: A specific subdomain certificate (
www.example.com) would take precedence over a wildcard certificate (
*.example.com) for requests to
Zone specificity: A specific subdomain certificate (
www.example.com) would take precedence over a custom hostname certificate if the domain is active as a zone on Cloudflare.
Certificate priority: If the hostname is the same, certain types of certificates take precedence over others.
Priority Certificate Type 1 2 3 4 5 6 7
Certificate recency: If the hostname and certificate type are the same, Cloudflare deploys the most recently issued or renewed certificate.
Cloudflare uses the following order to determine the certificate and settings used during a TLS handshake:
- SNI match: Certificates and settings that match the SNI hostname exactly take precedence.
- SNI wildcard match: If there is not an exact match between the hostname and SNI hostname, Cloudflare uses certificates and settings that match an SNI wildcard.
- IP address: If no SNI is presented, Cloudflare uses certificate based on the IP address (the hostname can support TLS handshakes made without SNI).
Hostname priority (SSL for SaaS)
When multiple proxied DNS records exist for a zone — usually with SSL for SaaS — only one record can control the zone settings and associated origin server.
Cloudflare determines this priority in the following order (assuming each record exists and is proxied (orange-clouded)):
Exact hostname match:
Wildcard hostname match:
- DNS (Belonging to the logical DNS zone)
- New Custom Hostname (Belonging to a SaaS Provider)
If a hostname resource record is not proxied (gray-clouded) for a zone on Cloudflare, that zone’s settings are not applied and any settings configured at the associated origin are applied instead. This origin could be another zone on Cloudflare or any other server.
Customer1 uses Cloudflare for authoritative DNS for the zone
shop.example.com. Customer2 is a SaaS provider that creates and successfully
shop.*example.com*. Afterward, traffic starts routing over Customer2’s zone:
- If Customer1 wants to regain control of their zone, Customer 1 contacts Customer2 and requests them to delete the Custom Hostname record. Another possibility is to stop proxying (gray-cloud) the record.
- If Customer1 is already proxying a new Custom Hostname for
www.example.com, Customer2 creates and verifies
www.example.comso traffic starts routing over Customer2’s zone. Since this new Custom Hostname is the last one validated, the new custom hostname on Customer1’s zone enters a moved status.
- If Customer1 is already proxying a legacy Custom Hostname for
www.example.comand Customer2 creates and verifies a new wildcard Custom Hostname for
*.example.com, traffic is routed to Customer1’s zone while the
www.example.comCNAME points to Customer1.
This customer is also using a SaaS provider that utilizes Cloudflare for SaaS. The SaaS provider is using a Cloudflare Enterprise plan.
If the SaaS provider is using a wildcard custom hostname, then the original customer’s plan limits will take precedence over the SaaS provider’s plan limits (Cloudflare will treat the zone as a Free zone). To apply the Enterprise limits through Cloudflare for SaaS, the original customer’s zone would need to either use a record or the SaaS provider would need to use an exact hostname match.