TLS and certificates
The padlock in the browser: what the certificate vouches for, why it must match every name and why old encryption is a risk.
- Browser
- Check certificate
- Name, expiry, issuer
- Encrypted connection
Your website's ID card
A certificate is your website's ID card. It confirms to visitors: “You really are talking to www.your-company.ch, and nobody is listening in.” It is issued by a recognised authority, for example Let's Encrypt.
What can go wrong
- Expired: like an expired passport. Browsers show a warning and many visitors leave.
- Wrong name: the ID card is made out to another name. For the browser this is like someone else's passport – it warns.
- Self-issued: a home-made ID card. Nobody can check whether it is genuine.
- No HTTPS: the page is transmitted unencrypted – like a postcard instead of a letter.
Old encryption
Encryption methods age too. Older versions (TLS 1.0 and 1.1) and weak ciphers are considered broken or insecure. Modern browsers no longer use them – but an attacker can force them if the server still offers them.
What you can do
Have certificates renewed automatically, secure all names in use and switch off old methods. With most hosting providers this takes a few clicks; eam.ch shows them for your environment.
The TLS grade
eam.ch summarises the encryption of every server in a grade of its own, similar to well-known online tests: from A+ (exemplary) to C (outdated). T means the certificate is not trusted – then even the best encryption is of no use.
The TLS grade is a detailed view for your IT team. Only the individual findings count towards the overall grade, so that nothing is counted twice.
In short
- The certificate is the website's ID card and must cover every name in use.
- Expired, self-signed or wrong certificates trigger warnings.
- Offer only TLS 1.2 and 1.3 with modern ciphers.
- Automate and monitor renewal.