Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
HTTPS is the way website communication connects safely, encrypted. It carries HTTP communication wrapped in TLS, the encryption mechanism, and the address begins with https://. The IETF's RFC 9110 defines what it means.
How does HTTPS work?
Think of the difference between a postcard and registered mail. A postcard can be read by anyone on its way. Registered mail is a sealed envelope, and you can also check the counter that receives it. Ordinary HTTP is the postcard, and HTTPS is the registered mail.
RFC 9110 treats HTTPS as a scheme for servers that can establish a TLS connection for HTTP. What is protected is that the server is confirmed as the owner of that address, and that the content of the communication cannot be read or rewritten. The standard destination is port 443 of TCP. Pitfalls of unencrypted communication are set out in insecure communication.
A browser must check that the server's identity is valid for the address it reached. The RFC explains this as a check to prevent impersonation by an attacker in the middle of the communication. For sites that want to be reached always over HTTPS, there is a mechanism called HSTS. RFC 6797 defines it as a mechanism by which a site declares that it can be accessed only over a secure connection. For help with your own settings, contact us.
Why does HTTPS matter?
Login input and the contents of an inquiry form should not be snooped on during communication. RFC 6265 says that without a secure channel, sensitive information in cookies becomes a target of snooping and may be rewritten on the way.
But what HTTPS shows is protection of the path. It covers that the server reached is confirmed as the owner of the address, and the confidentiality and integrity of the communication. Whether the operator can be trusted, and whether the inside of the site has flaws, are separate questions. A site operator checks these points.
- Serve every page over HTTPS.
- Redirect HTTP access to HTTPS.
- Load images and scripts over HTTPS too.
- Tell browsers by HSTS to use only a secure connection.
- Build a way not to miss the expiry of the certificate.
- Do not set it once and stop. Review the settings at every update.
Related terms
- TLS: a mechanism that encrypts the content of communication to prevent snooping on the way
- SSL: the old name for TLS, a mechanism that encrypts communication
- SSL certificate: an electronic certificate that shows a site is genuine
- HSTS: a mechanism that tells the browser to use only encrypted communication
Frequently asked questions
If a site uses HTTPS, is it safe?
Not necessarily. What HTTPS shows is protection of the communication path and confirmation of the server you reached. RFC 9110 provides for the confidentiality and integrity of communication and for confirming the server. It does not cover the trustworthiness of the operator or flaws in how the site is built.
Is it a problem to stay on plain HTTP?
We do not recommend it. RFC 6265 says that without a secure channel, sensitive information in cookies may be snooped on. There is also the danger of being rewritten by equipment on the way. Serve pages with login or input over HTTPS.
Next step
Pitfalls of unencrypted communication are in insecure communication. The free URL check shows only what is visible from outside, and whether every page of your site is on HTTPS can be seen from outside. For settings help, contact us.
Frequently asked questions
If a site uses HTTPS, is it safe?
Not necessarily. What HTTPS shows is protection of the communication path and confirmation of the server you reached. RFC 9110 provides for the confidentiality and integrity of communication and for confirming the server. It does not cover the trustworthiness of the operator or flaws in how the site is built.
Is it a problem to stay on plain HTTP?
We do not recommend it. RFC 6265 says that without a secure channel, sensitive information in cookies may be snooped on. There is also the danger of being rewritten by equipment on the way. Serve pages with login or input over HTTPS.