Deep TLS Audit — Protocols, Ciphers and Known Vulnerabilities
This is the most thorough TLS assessment available here. Beyond enumerating protocols and cipher suites, it tests for the specific named vulnerabilities that affect TLS implementations and configurations, checks forward secrecy and certificate details, and reports the whole posture as a graded assessment.
Why run it
Because vulnerability exposure is not something you can reason about from configuration. Whether a specific attack applies depends on the interaction of protocol version, cipher selection, implementation version and options — a combination too intricate to evaluate by reading the config file. Testing empirically answers it. This is also the right tool for producing evidence: an audit or a customer security questionnaire wants a document, and a graded report is considerably more convincing than an assurance.
Why automate it
Two independent clocks make a good result decay. New vulnerabilities are discovered against configurations that were previously fine, and your own configuration drifts as infrastructure is rebuilt from images whose defaults you did not choose. Both are gradual and neither generates an event. Scheduled auditing tracks the grade over time, which means a regression is attributable to a specific change rather than discovered at the next annual review with no idea when it happened.
What it gives you
The definitive statement of your TLS security posture, in a form that satisfies an auditor and a security team. Tracked over time it converts a compliance exercise into continuous assurance.