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
What eam.ch checks
| Check | Severity | Type |
|---|---|---|
| Certificate expired | critical | passive |
| Invalid chain or name does not match (SAN) | high | passive |
| Self-signed | high | passive |
| No HTTPS or no redirect from HTTP | high | passive |
| Expires in less than 30 days | medium | passive |
| TLS 1.0/1.1 offered | medium | active |
| Weak ciphers (RC4, 3DES, NULL, EXPORT, anonymous: medium; only without forward secrecy, e.g. static RSA key exchange: low) | medium/low | active |
Names used only for e-mail or FTP
With Plesk and similar panels, HTTPS on a name without its own website (e.g. mail., ftp.) returns the server's default page with the server certificate. The chain is valid, only the name does not match. eam.ch rates this “low” and refers to the STARTTLS check in the e-mail category. Solution: include the names in the certificate (“Mail access” for Let's Encrypt in Plesk), delete unused DNS records or accept the risk with a reason.
Recommended configuration
TLS 1.2 and 1.3 only, AEAD ciphers with ECDHE, in line with Mozilla's “Intermediate” profile. Example nginx:
ssl_protocols TLSv1.2 TLSv1.3; ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305; ssl_prefer_server_ciphers off;
In Plesk: Websites & Domains → “SSL It!” → Settings → “TLS versions and ciphers by Mozilla” → “Intermediate”. Check yourself: openssl s_client -connect www.example.ch:443 -tls1_1 must fail.
Further measures
- Monitor automatic renewal (ACME); Let's Encrypt certificates are valid for 90 days, and lifetimes are being shortened further.
- CAA record in DNS so that only the authorities you want may issue (see DNS and DNSSEC).
- Set HSTS only once all names have valid certificates (see Security headers).
TLS grade: rules
Per endpoint (name and port 443; same address and same certificate are combined). The worst applicable level applies.
| Grade | Condition |
|---|---|
| T | Certificate not trusted: chain incomplete or invalid, expired, self-signed, name mismatch, signature with SHA-1 or MD5 |
| C | Key too weak (RSA below 2048 bits, EC below 256 bits) or outdated cipher suites (RC4, 3DES, NULL, EXPORT, anonymous) |
| B | TLS 1.0 or 1.1 offered, or no cipher suite with forward secrecy |
| A- | TLS 1.3 not supported, or additional cipher suites without forward secrecy |
| A | no limitation |
| A+ | as A and HSTS of at least 180 days |
Passively (without approval), TLS 1.0/1.1 and the list of cipher suites are unknown; the grade is then provisional. eam.ch deliberately performs no attack tests such as Heartbleed or ROBOT. The grade is modelled on the SSL Labs rating but independent; differences are possible.
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.
Check it yourself
Commands to verify on Linux or macOS. Replace ihre-domain.ch with your domain and only check your own systems.
openssl s_client -connect www.ihre-domain.ch:443 -servername www.ihre-domain.ch </dev/null 2>/dev/null | openssl x509 -noout -subject -issuer -enddate
openssl s_client -connect www.ihre-domain.ch:443 -tls1_1 </dev/null