Hey all, I’m on a Cloudflare Pro plan using Advanced Certificate Manager.
I’ve disabled TLS 1.0/1.1 and all legacy ciphers including 3DES — and I’ve confirmed the correct config is showing in my dashboard.~
However, SSL Labs and Vanta are still seeing 3DES on some edge nodes, causing SWEET32 warnings.
I’ve purged cache and waited several hours, but it seems the config hasn’t propagated fully to all Cloudflare edge servers.
Posting my config summary and scan results below — would love confirmation or escalation help.
Was the site working with SSL prior to adding it to Cloudflare?
Quick update — I’m on a Pro Plan with Advanced Certificate Manager enabled , and the issue seems to be that legacy Universal and Backup certificates are still being served on some edge nodes , exposing TLS 1.0 and 3DES , which triggers SWEET32 warnings in SSL Labs and Vanta.
Support ticket has been submitted — but any insight from the Community or moderators would be appreciated. This is blocking SOC 2 audit compliance.
Pinging @cscharff or @MoreHelp — is there any way to have legacy Universal certs fully removed at the edge when an Advanced ACM cert is active?
And I’d assume the SSLlabs tool is probably checking the wrong things unless it could demonstrate the specifics of your cert being served with TLS 1.0 assuming you have set another minimum SSL version odds are higher the tool is wrong.