TLS/SSL Inspector

Fetch live TLS chain details for any host — protocol, cipher, and expiry.

Privacy: Server-Assisted. This tool calls /api/* for CORS proxies or TLS inspection. Payloads are not retained.

Uses a server-side TLS socket via /api/ssl— required because browsers cannot expose peer certificates. Trust is evaluated against this runtime's CA store.

Why inspect TLS from a sandbox?

Certificate chain mistakes, hostname mismatches, and upcoming expiry cause production outages. A quick host inspection surfaces protocol, cipher, and chain details.

Because browsers cannot fully expose remote TLS chain metadata, this tool uses a short-lived server-assisted probe and does not retain payloads as long-term logs.

How to use this tool

  1. Enter a hostname (and optional port) for the TLS endpoint.
  2. Run the inspection and review protocol, cipher, chain, and expiry.
  3. Fix DNS, chain, or certificate issues based on the reported fields.

Frequently asked questions

Does this store my hostname checks?

Probes are for live debugging and are not intended as retained payload archives. Prefer internal scanners for continuous production monitoring.

Is my data sent to a server?

TLS/SSL Inspector is hybrid: browser-first where possible, with short-lived server assistance (for example CORS proxies or TLS inspection) processed in memory and not retained as payload logs.