testssl

Probe TLS/SSL services with testssl.sh and report severity-mapped vulnerabilities.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/aurainfosec/cloud-review-automation-poc --skill testssl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testssl
Source: https://github.com/aurainfosec/cloud-review-automation-poc/tree/main/skills/testssl
Command: npx skills add https://github.com/aurainfosec/cloud-review-automation-poc --skill testssl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly determine whether a public service is truly using secure TLS/SSL settings by checking real protocol support, cipher behavior, certificates, and known TLS vulnerabilities as clients experience them.

Core Features & Use Cases

  • Protocol and cipher analysis: Detects offered TLS versions and cipher weaknesses (e.g., deprecated protocols, weak cipher suites) and maps findings to plugin severities for consistent reporting.
  • Vulnerability and certificate validation: Runs targeted checks for widely known TLS/SSL issues (e.g., Heartbleed/POODLE-style classes) and validates certificate properties like expiry, chain completeness, key size, CN/SAN mismatch, and OCSP status.
  • External probe for AWS endpoints: Verifies runtime TLS negotiation for ALB/NLB, CloudFront, API Gateway, EC2 HTTPS, RDS TLS (via STARTTLS), OpenSearch, and other endpoints where configuration claims must be confirmed from the outside.

Quick Start

Ask the AI to run the testssl TLS scan against your endpoint and return a severity-labeled summary of protocol support, certificate health, and discovered TLS vulnerabilities.

Frequently Asked Questions about testssl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my AWS endpoint for TLS vulnerabilities from the outside?

To check AWS endpoint TLS vulnerabilities from the outside, run an external probe using testssl.sh to evaluate runtime TLS negotiation and detect issues like Heartbleed or POODLE on ALB, CloudFront, or RDS endpoints.

What is the best way to validate SSL certificate expiry and chain trust for public services?

Validating SSL certificate expiry and chain trust involves probing internet-facing services to verify certificate properties like expiration dates, chain completeness, key size, and hostname alignment against client expectations.

Can I scan for weak ciphers and deprecated TLS protocols on my CloudFront distribution?

Yes, you can scan for weak ciphers and deprecated TLS protocols on CloudFront distributions by running an external probe that detects offered TLS versions and cipher weaknesses, mapping findings to severity levels.

How do I verify RDS TLS settings using an external probe?

To verify RDS TLS settings using an external probe, run testssl.sh with correct target formatting and STARTTLS to evaluate the database endpoint's TLS negotiation and certificate health from the outside.

Does testssl.sh support SNI and STARTTLS for scanning custom service ports?

Yes, testssl.sh supports SNI and STARTTLS for scanning custom service ports, requiring correct target formatting like hostname:port with optional SNI or STARTTLS parameters to accurately probe specific internet-facing services.

Why does my TLS scan return a hostname mismatch warning for my API Gateway endpoint?

A TLS scan returns a hostname mismatch warning when the endpoint's certificate CN or SAN does not align with the requested hostname, indicating a certificate validation weakness discovered during the external runtime probe.