Skip to main content

Why Is FlyingCDN Stuck at “Pending Validation”?

Updated this week

After adding a new site in FlyingCDN, the status may remain as “Pending validation”. This means we haven’t been able to detect the required DNS record yet.

How validation works

FlyingCDN checks for a specific CNAME record:
_acme-challenge.your-domain.com → your-domain.com.ffb7310192aab5b6.dcv.cloudflare.com

This record is required to issue the SSL certificate. Once it’s detected, the status will automatically change to “Active”—usually within a minute.

If it’s stuck at “Pending validation”

Here are the most common issues:

  • CNAME proxy enabled
    If you're using Cloudflare, make sure the _acme-challenge record is set to DNS only, not proxied.

  • Incorrect record type
    You must add a CNAME record, not a TXT or other type.

  • Old TXT record present
    Delete any existing _acme-challenge TXT records if found—they can interfere with validation.

  • CAA records set
    If your domain has CAA records, remove them. These can block SSL issuance unless properly configured.

  • Universal SSL enabled
    If you're using Cloudflare, you must disable Universal SSL. It conflicts with external certificate validation

How to confirm the record is correct

You can verify that the _acme-challenge CNAME is publicly visible using any DNS lookup tool like whatsmydns.net.


It should return the value ending with your-domain.com.ffb7310192aab5b6.dcv.cloudflare.com exactly as shown in your FlyingCDN dashboard.

Once everything is in place, validation will complete automatically.

Did this answer your question?