/crtsh/certificates

POST /api/crtsh/certificates

Price: 1 credit

Get a Certificate Transparency log entry by its crt.sh certificate id

How to use it

Get a single Certificate Transparency log entry by its crt.sh certificate id. Returns the certificate's common name and full subject, the full list of covered domains (Subject Alternative Names), issuer name, serial number, signature algorithm, public-key algorithm and size, SHA-256 and SHA-1 fingerprints, validity window (not before / not after), when the certificate was logged, and whether it is a precertificate. Useful for certificate and subdomain reconnaissance.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• certificate integer required — crt.sh certificate id (numeric) or a crt.sh certificate URL (examples: 987119772, 8913351873, "https://crt.sh/?id=987119772"; >: 0)

Response

• @type string (default: "CrtshCertificateDetail")
• id integer required
• common_name string nullable
• name_value array (default: [])
• issuer_name string nullable
• issuer_ca_id integer nullable
• serial_number string nullable
• not_before string nullable
• not_after string nullable
• logged_at string nullable
• subject_name string nullable
• signature_algorithm string nullable
• public_key_algorithm string nullable
• public_key_size integer nullable
• sha256 string nullable
• sha1 string nullable
• is_precertificate boolean (default: false)

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Certificate not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.