SSL Certificate Check
Issuer, expiry, chain and trust status of a domain's HTTPS certificate.
curl -X POST https://api.1lookup.dev/v1/ssl-certificate-check \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"domain":"example.com"}'{
"success": true,
"data": {
"domain": "example.com",
"reachable": true,
"protocol": "TLSv1.3",
"hostname_match": true,
"certificate": {
"subject": {
"common_name": "example.com"
},
"issuer": {
"common_name": "Example Trust TLS CA 1",
"organization": "Example Trust Services"
},
"sans": [
"example.com",
"www.example.com"
],
"serial_number": "04A1B2C3D4E5F60718293A4B5C6D7E8F",
"signature_algorithm": "ECDSA-SHA384",
"valid_from": "2026-10-02T00:00:00Z",
"valid_to": "2026-12-31T23:59:59Z",
"days_remaining": 42
},
"chain": {
"valid": true,
"depth": 3,
"issues": []
},
"transparency": {
"logged": true,
"first_seen": "2026-10-02T00:14:51Z"
}
},
"meta": {
"credits_used": 2,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
domainstring<domain>requiredDomain. Example: example.com
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.certificate.issuerobjectThe certificate authority that signed the certificate.
data.certificate.subjectobjectThe name the certificate was issued to.
data.certificate.sansarrayEvery hostname the certificate covers, including wildcards.
data.certificate.valid_tostringWhen the certificate stops being valid. The start date is in valid_from.
data.certificate.days_remainingnumberWhole days until expiry, ready to compare with an alert threshold.
data.chain.validbooleanWhether the served chain links to a trusted root without gaps.
data.hostname_matchbooleanWhether the domain you asked about is covered by the subject or a SAN.
data.protocolstringThe TLS version negotiated in the handshake, such as TLSv1.3.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
2 credits. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases