Historical SSL/TLS at 20B+ records.

Historical SSL/TLS certificate data across domains and IP addresses. 20B+ records sourced from certificate transparency logs and active TLS scanning.

WHAT'S IN THIS FEED

Multi-snapshot certificate state, at internet scale.

The Historical SSL Records Feed is the bulk version of the SSL Lookup API. The API answers single-target queries; the feed delivers the full historical corpus for analytical workloads, certificate-chain clustering, and offline pivot graphs.

Each record is one observed certificate at one point in time. The corpus exceeds 20B records across CT-log monitoring of all major operators, active TLS scanning of registered apex domains and discovered subdomains, and Deepinfo's own continuous discovery pipeline. Coverage includes the full chain, validity dates, subject and issuer details, SANs, and fingerprint identifiers.

Use this feed for SAN-graph clustering of brand-impersonation infrastructure, issuer-distribution analysis at scale, expiry-and-renewal tracking across vendor portfolios, or any research workflow that benefits from offline indexing of the full SSL observation history.

HOW IT'S DELIVERED

Historical bulk export, delivered on demand.

Available as a one-time bulk export or as periodic refreshes against the latest cumulative snapshot. Authenticate with an API token scoped to the feed.

Delivery

Historical bulk export. Single API call returns metadata plus a signed download_url. S3 and SFTP for large transfers.

Format

JSON or CSV. Partitioned by issuer and observation year for efficient downstream processing.

Refresh cadence

On-demand bulk export; periodic refresh available.

Authentication

API token in the request header. Per-feed scoping. Reference at docs.deepinfo.com.

SAMPLE RECORD

What you actually get.

The API response, with the metadata for the latest cumulative snapshot:

{
  "download_url": "https://feeds.deepinfo.com/historical-ssl/2026-05-02/historical-ssl.json.gz?...",
  "file_format": "json",
  "file_size": 412384719834,
  "file_update_time": "2026-05-02T03:14:27Z",
  "line_count": 21847391284
}

A few representative records from the JSON-formatted file at download_url:

{"sha256":"3a4b...e9","subject":"CN=*.acme.com","issuer":"CN=DigiCert TLS RSA SHA256 2020 CA1","not_before":"2024-03-12T00:00:00Z","not_after":"2025-04-12T23:59:59Z","sans":["acme.com","*.acme.com","api.acme.com"],"observed_at":"2024-03-13T08:14:00Z","source":"ct_log"}
{"sha256":"8c1d...a2","subject":"CN=login.contoso.io","issuer":"CN=Let's Encrypt R3","not_before":"2025-09-01T00:00:00Z","not_after":"2025-11-30T23:59:59Z","sans":["login.contoso.io"],"observed_at":"2025-09-02T10:00:00Z","source":"active_scan"}

“Certificate-lineage analysis across years is impossible without a deep historical corpus. The 20B-record dataset gives us the certificate-rotation patterns that map directly to threat-actor infrastructure.”

— Senior Threat Intel Lead, Defense Contractor
GET STARTED

Get the full SSL history, in bulk.

Most teams scope to an issuer or year range first. We'll set up token access and discuss partitioning that fits your workload.

Talk to us Browse API docs