crt.sh Cert Monitor — Subdomain & SSL Cert Discovery avatar

crt.sh Cert Monitor — Subdomain & SSL Cert Discovery

Under maintenance

Pricing

from $0.15 / 1,000 certificate records

Go to Apify Store
crt.sh Cert Monitor — Subdomain & SSL Cert Discovery

crt.sh Cert Monitor — Subdomain & SSL Cert Discovery

Under maintenance

Monitor certificate-transparency logs via crt.sh (keyless, no API key) for any domain: newly issued subdomains, certificate issuers, first/last-seen dates and cert IDs. Flat one-record-per-cert output for CSV/Excel/JSON export. Ideal for attack-surface discovery and brand monitoring.

Pricing

from $0.15 / 1,000 certificate records

Rating

0.0

(0)

Developer

Karl Sundström

Karl Sundström

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Categories

Share

crt.sh Certificate Transparency Monitor — New Subdomain & SSL Cert Discovery

Independent tool, not affiliated with crt.sh or Sectigo.

Monitor certificate-transparency logs for any domain via crt.sh — keyless, no API key, no login. Extract newly issued subdomains, certificate issuers, validity windows and cert IDs, and get a flat one-record-per-certificate output ready for CSV/Excel/JSON export. New CT-log entries are warm signals: every fresh certificate reveals a hostname that just went live.

Why crt.sh Certificate Transparency Monitor?

  • 🕵️ Attack-surface discovery — catch subdomains the moment certificates appear in public CT logs.
  • 🔔 Change monitoring — run it on a schedule with hoursBack to get only certificates issued since your last check.
  • 🏢 Brand & phishing tracking — watch lookalike domains' certificate activity for security and brand teams.
  • 📋 Flat output — one row per certificate (domain, subdomain, issuer, crtId) built for CRM, sheets and SIEM import.
  • No setup — queries crt.sh's open JSON endpoint directly; just enter a domain and run.

Use cases

Attack-surface management · subdomain enumeration · brand/typosquat monitoring · security compliance audits · OSINT research · expired-cert alerting

What data you get

🏷️ FieldDescription
🌐 domainDomain you asked to monitor
🔎 subdomainHost names covered by the certificate (SAN list)
🏛️ issuerCertificate-issuing CA (e.g. Let's Encrypt, DigiCert)
📅 notBeforeCertificate validity start
📅 notAfterCertificate expiry
🕐 entryTimestampWhen the log entry landed in CT logs (if present)
🆔 crtIdcrt.sh certificate ID — open https://crt.sh/?id=<crtId> for the full cert

How to use

  1. Add the actor to your Apify account and click Run.
  2. Enter one or more domainList entries (e.g. wikipedia.org).
  3. Set hoursBack to filter recent certificates (default 720 h = 30 days; 0 = full history).
  4. Set maxResults to cap the bill (default 100).
  5. Export results as JSON, CSV or Excel, or schedule runs for continuous monitoring.

Input

{
"domainList": ["wikipedia.org"],
"hoursBack": 720,
"maxResults": 100
}
FieldTypeDescriptionDefault
domainListarrayDomains to monitor (all subdomains included via %25.<domain> CT search)required
hoursBackintegerOnly certificates issued within the last N hours; 0 returns full history720
maxResultsintegerCap on records per run100

Output

{
"domain": "wikipedia.org",
"subdomain": "*.m.wikipedia.org *.wikipedia.org wikipedia.org",
"issuer": "C=US, O=Let's Encrypt, CN=YE2",
"notBefore": "2026-08-05T19:15:41",
"notAfter": "2026-11-03T19:15:40",
"entryTimestamp": null,
"crtId": "28567885787"
}
Typical subdomain scrapersThis actor
SourceDNS brute-force wordlistsOfficial certificate-transparency logs
CoverageOnly guessable namesEvery hostname that ever got a TLS certificate
API keyVariesNone
OutputMixed formatsFlat one-row-per-cert, export-ready

Support

Issues and feature requests via the Apify actor page.