Google Sets Deadline for HTTPS and Warns Publishers to Upgrade Soon

Google Sets Deadline for HTTPS and Warns Publishers to Upgrade Soon

Google Sets Deadline for HTTPS and Warns Publishers to Upgrade Soon

How Will Chrome Warn Users of Insecure Pages?

A prominent warning will be shown in Chrome’s address bar (also known as the Omnibox), indicating that an insecure website is “Not secure.” This warning will show for all http websites.

Google’s announcement was firm about their goal to warn users of insecure sites, with the intent of  further shepherding more web publishers into upgrading to HTTPS.

“Chrome’s new interface will help users understand that all HTTP sites are not secure, and continue to move the web towards a secure HTTPS web by default.”

Image showing an example of what the security warning will look like in Chrome's browser address bar.Google’s announcement provided an example of how the “omnibox” address bar security warning will appear.

 

Will Chrome Display a Warning on Mixed Content Pages?

Google’s announcement did not explicitly address whether mixed secure/insecure webpages will trigger the warning. But it may be safe to assume that these kinds of pages that display a mix of secure and insecure content will trigger a warning.

According to Google, Chrome’s Lighthouse web page auditing tool can identify what web page elements are triggering a mixed content warning:

“Mixed content audits are now available  to help developers migrate their sites to HTTPS in the *latest Node CLI*  version of Lighthouse, an automated tool for improving web pages. The new audit in Lighthouse helps developers find which resources a site loads using HTTP, and which of those are ready to be upgraded to HTTPS simply by changing the subresource reference to the HTTPS version.”

Worldwide Impact of Chrome HTTPS Security Warning

The impact will be felt more keenly in some countries than in others. But even in countries where the use of Chrome is low, this still represents 39 percent of Internet browsers.

The need to update to HTTPS is especially important in regions such as South America, where Chrome use is as high as 74.04 percent and Israel, where 66.77 percent of Internet traffic is on Chrome.

 More free SSL Resources coming.
Our site is under update. If you want to list your SSL Service (Free or Commercial) to our directory contact us at contact@branddomains.org
 
  • Forever Free SSL Certificates

    100% Free Forever

    Never pay for SSL again. Thanks to Letsencrypt the first non-profit CA.

  • Forever Free SSL Certificates

    Widely Trusted

    Our free SSL certificates are trusted in 99.9% of all major browsers.

  • Forever Free SSL Certificates

    Enjoy SSL Benefits

    • Protect user data & gain trust
    • Improve Search Engine Ranking
    • Prevent forms of website hacking

How It Works

  1. Let’s Encrypt is the first free and open CAWe generate certificates using their ACME server by using domain validation.
  2. Private Keys are generated in your browser and never transmitted.For modern browsers we generate a private key in your browser using the Web Cryptography API and the private key is never transmitted. The private key also gets deleted off your browser after the certificate is generated. If your browser does not support the Web Cryptography API then the keys will be generated on the server using the latest version of OpenSSL and outputted over SSL and never stored. For the best security you are recommended to use a supported browser for client generation. You can also provide your own CSR when using manual verification in which case the private key is handled completely on your end.

Advanced Options

  1. Free Wildcard CertificatesWildcard certificates allow you to secure a domain and any subdomains under that domain. If you wanted to secure any subdomains of example.org that you have now or in the future you can make a wildcard certificate. To generate wildcard certificates add an asterisk to the beginning of the domain(s) followed by a period. Wildcard domains do not secure the root domain so you must re-enter the root domain if you want it also secured under one certificate. For example to create a wildcard domain for example.org enter *.example.org example.org. To create a wildcard certificate for multiple domains such as example.org and example.com enter *.example.org example.org *.example.com example.com. Manual DNS verification will be required.
  2. Multiple Domains or Subdomains or WildcardsMultiple domains or subdomains are allowed and should be separated by spaces (e.g. “subdomain.domain.com domain.com otherdomain.org *.wildcarddomain.com“). If the multiple domains or subdomains pertain to multiple directories then you must use manual HTTP verification and upload verification files to the correct directories or use DNS verification.
  3. Prevent WWW from being AddedWe automatically add the www version of the domain if not already added as most users want that implicitly. To remove the www just submit the domains you want to verify then on the verification page near the top click on “Add / Edit Domains” and remove it and submit again.

Read more at https://www.sslforfree.com/