From our 2018 archive. This is a historical announcement. Context and links reviewed on 18 September 2026; the information below relates to the original publication period.
In July 2018, Chrome 68 began marking HTTP pages as “Not secure”. This was a browser milestone, not a new deadline that is still approaching.
What the warning did—and did not—mean
HTTP does not provide the encrypted connection that HTTPS supplies. A browser warning about that connection is not proof that a website has suddenly been hacked. Equally, an HTTPS connection does not certify that a business is trustworthy or that all of its software is secure.
Google’s July 2018 announcement records the wider move to warn about HTTP pages.
What to do today
Use our current HTTPS guide to review certificates, redirects, mixed content and ongoing maintenance. Test the whole enquiry or purchasing journey after making changes.
The original article’s package prices, blanket GDPR-compliance assurances and promises of improved rankings are no longer part of this advice. A certificate is one component of website care.
See current hosting and support options or ask our team for help.
