Hi freyre,

Well that particular certificate had expired and all others will expire in 7 days.
Re: https://www.fairssl.se/en/ssltest for cloudflaressl.com
See also: http://toolbar.netcraft.com/site_report?url=http://sni112500.cloudflaressl.com
Now unable to contact that server.
With the certificate see here a a typical error replacement certificate after it has expired, rather than before.

Signature Algorithm: SHA1+RSA is weak and there are University researcher proposals to slowly phase this out,
because now at a cost that stands at $ 75.000 the algorithm can be hacked
(coming into reach for cybercriminals to abuse this for specific targeted attacks).

So when Cloudflare wants you for a cheap ride saving on the penny to earn a pound,
you should be glad you are made aware of that fact now.
Big Corporational “Scrooge” mentality backfiring here.

Secure Cookie Warning: Secure cookies: Warning
Requested URL: https://cloudflaressl.com/ | Response URL: https://cloudflaressl.com/ | Page title: CloudFlare API 4 Documentation | HTTP status code: 200 (OK) | Response size: 1,687,808 bytes (gzip’d) | Duration: 12,058 ms
Overview
Cookies served over HTTPS but not flagged as “secure” may be sent over an insecure connection by the browser. Often this may be a simple request for an asset such as a bitmap file but if it’s on the same domain as the cookie is valid for then it will be sent in an insecure fashion. This poses a risk of interception via a man in the middle attack.

Result
It looks like a cookie is being served over HTTPS without the “secure” flag being set (name : value):

__cfduid : dd54943700b9995d5503cb0fbdccd17e01444436977
Unless the cookie needs to be sent over an insecure connection, the “secure” flag should always be set to ensure it can only be sent with an HTTPS request.

polonus (volunteer website security analist and website error-hunter0