mTLS (mutual TLS) — a TLS mode where not only the server but also the client presents a certificate. The server verifies the client cert against a trusted CA list → decides access. Use cases: service-to-service in microservices, API Gateway with client certs, banking and gov services, Zero Trust architectures. More complex than regular HTTPS — you need CA infrastructure + rotation.
Below: details, example, related terms, FAQ.
ssl_verify_client on; + ssl_client_certificate ca.pem;--cert client.pem --key client.keynginx:
ssl_verify_client on;
ssl_client_certificate /etc/ssl/ca.pem;
# $ssl_client_s_dn contains client cert subjectSSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up freemTLS — cryptographic proof of private-key ownership. API key — a string vulnerable to leaks. mTLS is safer but harder to rotate.
Automated issuance via an internal CA (Vault, Smallstep), rotate every 30-90 days. For external partners — manual process.
Yes. Browser shows a cert-picker UI from the OS store. Chrome + macOS — TouchID unlock.