Historical SSL Records
Where Certificate Data Reaches Your Team Today.
There is no public feed of historical SSL records. Certificate data reaches your team three ways today: a live check of one host, a search of the index by certificate field, and the full record of one domain. For certificate history in bulk, talk to our data team.
SSL Lookup
deepinfo.com:443
issuer WE1 · Google Trust Services · 2026-08-22 → 2026-11-20 · valid_ true
your stored answers
- today
- A renewal, between two stored answers
The Routes to Certificate Data.
| SSL Lookup | The certificate a host serves right now: subject, issuer, validity, the SAN names, fingerprints, and a verdict on signature and chain. / |
|---|---|
| Domain Search | Domains filtered by certificate fields, combined with any of the other searchable fields. / |
| Domain Detail | The certificate on record for one domain, next to its WHOIS, DNS and web data. / |
| Continuous Scanning | A dated SSL snapshot from each scan of the assets you monitor, in External Attack Surface Management. |
| Fraudulent Domain Monitoring | The SSL history of each lookalike domain your team monitors, in Brand Risk Protection. |
Paths are relative to https:/. Which routes your plan includes depends on your modules.
SSL Lookup Reads the Certificate a Host Serves Right Now.
SSL Lookup opens a TLS connection and parses the certificate the host presents. It returns that certificate and a valid_ verdict, not the whole chain.
Run it on a schedule against the hosts you care about and store the answers, and you are building a certificate history for those hosts from today.
{
"target": "deepinfo.com",
"port": 443,
"connection_status": "success",
"parsed": {
"subject": { "common_name": "deepinfo.com", "…": "…" },
"issuer": {
"common_name": "WE1",
"organization": "Google Trust Services",
"…": "…"
},
"validity": {
"start": "2026-08-22T16:13:55Z",
"end": "2026-11-20T17:13:40Z"
},
"signature": { "valid": true, "valid_chain": true },
"…": "…"
}
}curl "https://api.deepinfo.com/v1/lookup/ssl?target=deepinfo.com" \
-H "apikey: YOUR_API_KEY"Work That Spans Many Hosts at Once.
Brand Impersonation
Cluster lookalike infrastructure by the names its certificates cover and the issuers it uses.
Attack Surface Management
Find certificates that name your domains on hosts your inventory does not list.
Incident Investigation
Establish which certificate a host presented around the time of an incident.
Supply Chain Security
Review certificate hygiene across the hosts of many suppliers at once.
Questions About Historical SSL Records
Is there an SSL history API?
Not among the public Data & API endpoints. SSL Lookup checks a host live, and Domain Search and Domain Detail read the certificates in the index. For the assets you monitor, the Deepinfo Platform keeps a dated SSL snapshot from every scan.
Does SSL Lookup return the full certificate chain?
No. It returns the certificate the host serves and a valid_ verdict on whether the chain validates, next to the signature check.
Can we find the hosts that serve one certificate?
Yes. Filter Domain Search on ssl.fingerprint.sha256. A fingerprint identifies one certificate, so the result lists the hosts in the index that serve it.
Can we tell when a host’s certificate last changed?
For hosts in the index, yes. Each record carries ssl_, the last time Deepinfo saw its certificate change, and Domain Search can sort on it to show the latest changes first.
What should we bring to the data team?
Tell our data team which domains or hosts, which period and which certificate fields your analysis needs, and how your team loads data. They tell you what can be provided, and in what form.
Bring Your Certificate Question to Our Data Team.
Name the hosts, the period and the fields you need. Our data team tells you what can be provided, and in what form.