Google Builds HTTPS Directly Into Top Level Domains

1 minute read
| Link

More websites have encrypted their traffic than ever, but there is a loophole. Some use a mixture of HTTPS and unsecure HTTP. Google is closing this by building HTTPS protection directly into certain top level domains.

Which means that today, when you register a site through Google that uses “.app,” “.dev,” or “.page,” that page and any others you build off it are automatically added to a list that all mainstream browsers, including Chrome, Safari, Edge, Firefox, and Opera, check when they’re setting up encrypted web connections. It’s called the HTTPS Strict Transport Security preload list, or HSTS, and browsers use it to know which sites should only load as encrypted HTTPS automatically, rather than falling back to unencrypted HTTP in some circumstances. In short, it fully automates what can otherwise be a tricky scheme to set up.

Check It Out: Google Builds HTTPS Directly Into Top Level Domains

Google Builds HTTPS Directly Into Top Level Domains
Add a Comment

Log in to comment (TMO, Twitter, Facebook) or Register for a TMO Account