Thanks for the tip. I didn't ask for support here. I think this issue is interesting because CF's decision(s) are experimental and they do not check if a serv

Thanks for the tip. I didn't ask for support here. I think this issue is interesting because CF's decision(s) are experimental and they do not check if a server supports ECDSA prior to issuing the cert, which resulted in any links to https://mysite.com https://mysite.com erroring out "this site isn't secure" and a 525, until I paused CF, and have since deleted the domain from CF, use a different (compatible) SSL cert, updated DNS records to not point CF's nameservers, etc. Perhaps CF will implement a change to check to see if the customer's server supports an algo before signing a cert with it.