Worked examples for the SSL lookup: the certificate a host serves right now. First valid certificates (on a domain, on an IP address, on another port, with an elliptic-curve key), then certificates with problems, then connections that fail.

The problem certificates come from a public test site that serves broken certificates on purpose. Every example is a real response from September 24, 2026.

To judge a certificate, read parsed.signature.valid and parsed.signature.invalid_reason (why it is not valid), parsed.has_expired and parsed.signature.self_signed. A connection problem is not an HTTP error: the API returns 200 with the reason in connection_status and parsed set to null.

After the examples: Parameters Without an Example

Endpoint
SSL

Valid Certificates

ExampleParamValue
Certificate of a Domaintargetdeepinfo.com
Certificate Served on an IP Addresstarget1.1.1.1
Mail Server on Port 465target
port
smtp.gmail.com
465
An Elliptic Curve (ECDSA) Keytargetecc256.badssl.com

Certificate Problems

ExampleParamValue
An Expired Certificatetargetexpired.badssl.com
A Self-Signed Certificatetargetself-signed.badssl.com
An Untrusted Roottargetuntrusted-root.badssl.com
A Certificate for Another Host Nametargetwrong.host.badssl.com

Connection Problems

ExampleParamValue
A Host Name That Does Not Resolvetargetno-such-host.example.com
A Port Without TLStarget
port
1.1.1.1
80

Parameters Without an Example

As of September 24, 2026, these parameters have no worked example.

Parameter Why
proxy Needs a proxy server of your own, with its credentials; the lookup then connects through it.

Reference updated