Certificate transparency search
See every publicly logged certificate for a domain, who issued each one, when, and which names it covers.
Results for api.stars.github.com
- Cert Spotter answered. crt.sh didn’t, so wildcard and subdomain results may be missing.
Nothing logged
No logged certificates for api.stars.github.com
This usually means the name never had a publicly trusted certificate. Certificates from private authorities are not logged, and a new one can take a few minutes to appear.
Structured result (JSON) · 646 B
{
"domain": "api.stars.github.com",
"includeSubdomains": false,
"excludeExpired": true,
"sources": [
{
"id": "certspotter",
"name": "Cert Spotter",
"status": "ok",
"ms": 292
},
{
"id": "crtsh",
"name": "crt.sh",
"status": "failed"
}
],
"asOf": "2026-11-15T19:25:03.836Z",
"stale": false,
"summary": {
"certificates": 0,
"rawEntries": 0,
"firstLogged": null,
"lastLogged": null,
"currentlyValid": 0,
"wildcards": 0,
"issuers": [],
"cadenceDays": null,
"truncated": false,
"newestEnd": null
},
"certificates": [],
"next": null
}Next step
- Subdomain finderWhich names appear in these certificates?Check api.stars.github.com in Subdomain finder
- SSL checkerWhich certificate is live right now?Check api.stars.github.com in SSL checker
- Certificate decoderRead one certificate field by fieldOpen in Certificate decoder
What Certificate Transparency is
Certificate Transparency, or CT, is a set of public, append-only logs. When a certificate authority that browsers trust issues a certificate, it records it in several of these logs, and browsers such as Chrome and Safari refuse certificates that were not logged. The point is simple: if a certificate is issued for your domain, you can find out, even if you did not ask for it.
That makes CT the best public record of who has issued certificates for a name. It is how people notice a mistaken issuance, a forgotten test site that got a certificate, or a certificate authority that has been switched without telling the team.
This page searches those logs for you. Enter a domain and you get the certificates, a timeline grouped by issuer, and the numbers that matter: how many there are, how many are valid today, and how often they are renewed.
How to use it
- Enter a domainType a name such as
example.org. A bare name lists certificates that name it. Add a subdomain, such aswww.example.org, to narrow the search to that name. - Decide about subdomainsSwitch on "Include subdomains" to list certificates for every name under the domain. It is the heavier question, so it can wait in a short queue, and the answer is kept for an hour so the next person gets it at once.
- Read the timelineEach lane is one issuer and each bar is one certificate, from the day it started to the day it ends. Filled bars are valid now, outlined bars have expired. A change of lane shows a change of authority, and a gap shows a lapse.
- Open a certificateEach row shows the names, the issuer, the dates, the serial number and the SHA-256 fingerprint when we have it, with a link to the entry on crt.sh.
# The same search from a terminal, as JSON
curl "https://lookupowl.com/api/v1/tools/ct-search?domain=example.org&includeSubdomains=true"Why it asks two sources
crt.sh, run by Sectigo, is the standard way to search CT. It is free and thorough, and it is also slow and often unavailable. Cert Spotter, run by SSLMate, is fast and reports revocation, but it allows only a small number of questions.
So we ask both at once for a single name and merge what comes back. A precertificate and its final certificate, which crt.sh lists as two entries, become one row, and the "log entries" line says how many were merged. If one source does not answer, you get the other, with a note saying so. If both are down and we have a copy from an earlier search, you get that copy with its age on the page.
- Both answered. The fullest result, with fingerprints and revocation where Cert Spotter returned the certificate.
- One answered. The result is still useful, but wildcard and subdomain results can be missing when crt.sh is the one that failed.
- A stored copy. Shown only when both are down, with how old it is.
- Neither, and no copy. We say so plainly. The logs are on their side, not yours.
Reading the results
| What you see | What it means |
|---|---|
| Renewal cadence | The typical number of days between issues, from the median gap of recent certificates. Short cadences such as 60 or 90 days point to automated renewal. |
| Two certificates at each renewal | Often an ECC and an RSA certificate issued together, so older clients can still connect. |
| Wildcard | A name starting with *. covers every name one level below it. It is the reason a subdomain list can look short. |
| Email address in the names | Some certificates, such as S/MIME certificates, name a person. They are shown in the list and left out of subdomain results. |
| Revoked | Reported by Cert Spotter. crt.sh does not report revocation, so a certificate only seen on crt.sh shows as not revoked. |
Big domains have more certificates than one answer can hold. We then show the newest 100 (or the number you pick, up to 500) and say how many exist, and you can narrow the search by issuer or by date under More options.
What it cannot tell you
- Logged is not the same as in use. CT shows that a certificate exists. It cannot show which one a server is serving. For that, use the SSL checker.
- Private certificates are missing. Certificates from a private authority, such as a company's internal one, are not logged.
- New certificates take a little while. A certificate can take a few minutes to show up after it is issued.
- Very big domains are cut. An answer from the logs has a size limit, so for a domain with thousands of certificates we say the list is cut and suggest a filter.
To see the names themselves, try the subdomain finder, which reads the same certificates and lists the hosts, with where each one points now.
Questions people ask
What is crt.sh and why is this an alternative?
crt.sh is a free search over Certificate Transparency logs run by Sectigo. It is the standard tool, but it is often slow or down. This page asks crt.sh and Cert Spotter together and merges the answers, so you still get a result when one of them is not answering.
Does every certificate show up here?
No. Only certificates that were logged do, and browser-trusted authorities log nearly all of them. Certificates from private authorities are not logged, and a very new certificate can take a few minutes to appear.
Why does a certificate show 3 log entries?
A certificate is usually logged twice: first as a precertificate before issuance, then as the final certificate, and often in more than one log. We merge them into one row so a renewal is one line, and the entry count says how many were merged.
Can I search for a whole organisation?
Not here. The search is by domain name, with an option to include the names under it. Searching by organisation name needs a different kind of query that the free sources do not allow.
Why is "Include subdomains" slower?
It asks the logs for every certificate that names anything under the domain, which is far more work than one name. It uses crt.sh only, so it can wait in a short queue. The answer is kept for an hour, so a second search for the same domain is quick.
How do I find out which certificate a site is using now?
Use the SSL checker. It connects to the server and shows the certificate it really sends, with its chain and expiry. Certificate Transparency can only show what was issued.
Is the data private?
The logs are public by design, so the certificates are public. We keep a short-lived copy of each answer so repeated searches are quick, and we pace searches for the same domain to be kind to the logs.
Use it from AI, the API or the command line
Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is ct_search. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/ct-search?q=example.org&excludeExpired=false&includeSubdomains=true"claude mcp add --transport http lookupowl https://lookupowl.com/mcp