T-25 days until Chrome starts flagging HTTP sites as "Not Secure"
Jun 28, 2018Patrick R. Donahue
Summary
This post highlights the critical juncture where Chrome began flagging HTTP sites as 'Not Secure', emphasizing the importance of HTTPS adoption. It debunks common myths surrounding HTTPS deployment difficulty, necessity, and performance, showcasing Cloudflare's role in simplifying SSL certificate management and offering free, performant HTTPS through its edge network. It also details Cloudflare's solutions for individual sites and SaaS providers, and encourages users to adopt HTTPS by enabling features like 'Always Use HTTPS' and 'Automatic HTTPS Rewrites'.
More from the Website Security & Threat Management trail
- We tested our own WAF with frontier AI models. Here’s what we found
- When scanners miss the attack: how Cloudflare Client-Side Security protects storefronts
- Introducing automatic remediation policies with Cloudflare CASB
- Introducing context-aware vulnerability discovery and remediation with Cloudflare Managed Defense and OpenAI Daybreak Models
- Introducing Adaptive Intelligence: undermining the economics of every bot attack