plain-prompt
Explain a TLS handshake failure
Separate certificate, name, chain, protocol, cipher, and time problems.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Identify the earliest failed TLS validation stage.
Context: Never recommend disabling certificate verification as a fix.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Endpoint and client:
{{environment}}
TLS evidence:
{{evidence}}
Return finding and safe verification.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
curl: (60) SSL certificate problem: unable to get local issuer certificate
Expected result
The client could not build a chain to a trusted issuer. Inspect the served chain with `openssl s_client -showcerts`; verify that the intermediate, not the private root key, is served.