I am managing the development of my client’s website “Écrivain Funéraire.” I’m currently facing an issue with the domain www.ecrivain-funeraire.com: there appears to be a problem with the SSL certificate.
My client has already contacted the hosting provider (Combell.com), who confirmed that everything is functioning correctly on their side. It has already been 48 hours since I updated the CNAME DNS record. Here is a link to check the DNS records: https://dnsquery.org/dnsquery/www.ecrivain-funeraire.com/CNAME.
Could you please advise on what steps should be taken to resolve this issue?
To get your SSL certificate working properly, you’ll need to update your DNS records to correctly point to Webflow’s servers. Here are the required DNS records:
Create an A record with hostname @ pointing to 198.202.211.1
Create a CNAME record with hostname www pointing to cdn.webflow.com
Create a TXT record with hostname _webflow and the verification value from your Site settings
If your domain uses CAA records, you’ll also need to add these two records to authorize SSL certificate issuance:
The A record ‘s name must be set to @. so that it identifies the base domain of ecrivain-funeraire.com . In your DNS console that will generally look like @ or just a blank name field.
It looks like you’ve set it to cdn.webflow.com , which is the value of the CNAME record.
That’s creating some unworkable routing.
Once it’s set correctly and propagated, the highlighted field should appear as ecrivain-funeraire.com .
Had this happen on a client’s site,SSL didn’t kick in until both A records pointed to Webflow’s IPs and the www CNAME went to proxy-ssl.webflow.com (not the root). Double-check propagation at whatsmydns.net and clear any extra AAAA records that might conflict.
