What does a check return?

Whether the certificate is valid and trusted, the issuer, the subject and the names it covers, the validity period with days remaining, and the reason when validation fails.

Yes. Each call connects to the host and inspects the certificate it presents at that moment, so renewals and misconfigurations show immediately.

Does it check the whole chain?

It validates the certificate as a standard TLS client would, so a broken or untrusted chain reports as invalid with the reason.

Can I check hosts on non-standard ports?

Checks target the hostname's HTTPS port. Internal and private addresses are not reachable from the API.

What does a call cost?

10 tokens, because each check opens a live connection to the target host.

MonitoringMAINTAINED10 tokens / call

SSL Checker Api

Check any hostname's TLS certificate: validity, issuer, covered names and days until expiry, live

Check the TLS certificate of any hostname in one call: whether it is valid and trusted, who issued it, which names it covers, and when it expires, with the days remaining. Built for uptime monitors, security checks and expiry alerts.

Every call needs an X-Api-Key header. A free key includes 500 tokens a month, no card required. 10 tokens per call, so the free plan covers about 50 calls a month.

Start free — 500 tokens / mo →See all plans

No credit card requiredAccess to 125+ APIsCancel anytime

response.json

{
  "success": true,
  "data": {
    "hostname": "wikipedia.org",
    "port": 443,
    "valid": true,
    "validFrom": "Oct  9 23:02:03 2025 GMT",
    "validTo": "Jan  7 23:02:02 2026 GMT",
    "daysUntilExpiry": 35,
    "issuer": {
      "C": "US",
      "O": "Lets Encrypt",
      "CN": "E7"
    },
    "subject": {
      "CN": "*.wikipedia.org"
    },
    "serialNumber": "05E99AFAE9E9285C9A6B8CA6FEFF26C23F9B",
    "fingerprint": "28:F1:C8:C5:9F:B5:BC:B6:B6:37:54:D7:A4:E7:21:61:38:D3:AB:D7",
    "keyUsage": [
      "1.3.6.1.5.5.7.3.1",
      "1.3.6.1.5.5.7.3.2"
    ],
    "subjectAltName": "DNS:*.wikipedia.org, DNS:*.wikimedia.org, DNS:*.wikidata.org, DNS:*.wiktionary.org, DNS:wikipedia.org, DNS:wikimedia.org",
    "cipher": {
      "name": "TLS_AES_128_GCM_SHA256",
      "standardName": "TLS_AES_128_GCM_SHA256",
      "version": "TLSv1.3"
    },
    "protocol": "TLSv1.3",
    "authorized": true,
    "authorizationError": null
  }
}

Also available on

RapidApi

Production Ready: Battle-tested infrastructure with a 99.9% uptime SLA. Rate limits are generous, responses are consistent.
Simple Integration: Standard REST + JSON. Works with any HTTP client. Copy-ready code snippets in 4 languages.
One Key, 125+ APIs: Your DataAndAPIs subscription unlocks every API on the platform — anime, finance, sports, and more.

Use cases for SSL Checker Api

Alert before a certificate expires by checking your domains on a schedule.
Verify that a customer's domain has a valid, trusted certificate during onboarding.
Show certificate details on an uptime or security dashboard.
Catch misconfigured names by checking that the certificate covers the host you expect.

SSL Checker Api endpoints

Every endpoint with its parameters and a real example response.

OpenAPI definition Postman workspace

GETChecks SSL Certificate

GETChecks SSL Certificate

https://ssl-checker-api.dataandapis.com/v1/check

Query parameters

Parameter	Example
hostname	wikipedia.org	Required
port	443	Optional

Example request

curl "https://ssl-checker-api.dataandapis.com/v1/check?hostname=wikipedia.org&port=443" \
  -H "X-Api-Key: YOUR_API_KEY"

Example response

{
  "success": true,
  "data": {
    "hostname": "wikipedia.org",
    "port": 443,
    "valid": true,
    "validFrom": "Oct  9 23:02:03 2025 GMT",
    "validTo": "Jan  7 23:02:02 2026 GMT",
    "daysUntilExpiry": 35,
    "issuer": {
      "C": "US",
      "O": "Lets Encrypt",
      "CN": "E7"
    },
    "subject": {
      "CN": "*.wikipedia.org"
    },
    "serialNumber": "05E99AFAE9E9285C9A6B8CA6FEFF26C23F9B",
    "fingerprint": "28:F1:C8:C5:9F:B5:BC:B6:B6:37:54:D7:A4:E7:21:61:38:D3:AB:D7",
    "fingerprint256": "D8:BB:C0:CA:A9:93:C7:BA:CA:E3:11:33:64:69:5A:BA:BF:CE:12:94:95:F3:E0:28:39:E5:B8:AC:8D:DA:1B:78",
    "keyUsage": [
      "1.3.6.1.5.5.7.3.1",
      "1.3.6.1.5.5.7.3.2"
    ],
    "subjectAltName": "DNS:*.m.mediawiki.org, DNS:*.m.wikibooks.org, DNS:*.m.wikidata.org, DNS:*.m.wikimedia.org, DNS:*.m.wikinews.org, DNS:*.m.wikipedia.org, DNS:*.m.wikiquote.org, DNS:*.m.wikisource.org, DNS:*.m.wikiversity.org, DNS:*.m.wikivoyage.org, DNS:*.m.wiktionary.org, DNS:*.mediawiki.org, DNS:*.planet.wikimedia.org, DNS:*.wikibooks.org, DNS:*.wikidata.org, DNS:*.wikifunctions.org, DNS:*.wikimedia.org, DNS:*.wikimediafoundation.org, DNS:*.wikinews.org, DNS:*.wikipedia.org, DNS:*.wikiquote.org, DNS:*.wikisource.org, DNS:*.wikiversity.org, DNS:*.wikivoyage.org, DNS:*.wiktionary.org, DNS:*.wmfusercontent.org, DNS:mediawiki.org, DNS:w.wiki, DNS:wikibooks.org, DNS:wikidata.org, DNS:wikifunctions.org, DNS:wikimedia.org, DNS:wikimediafoundation.org, DNS:wikinews.org, DNS:wikipedia.org, DNS:wikiquote.org, DNS:wikisource.org, DNS:wikiversity.org, DNS:wikivoyage.org, DNS:wiktionary.org, DNS:wmfusercontent.org",
    "cipher": {
      "name": "TLS_AES_128_GCM_SHA256",
      "standardName": "TLS_AES_128_GCM_SHA256",
…

Show full response

{
  "success": true,
  "data": {
    "hostname": "wikipedia.org",
    "port": 443,
    "valid": true,
    "validFrom": "Oct  9 23:02:03 2025 GMT",
    "validTo": "Jan  7 23:02:02 2026 GMT",
    "daysUntilExpiry": 35,
    "issuer": {
      "C": "US",
      "O": "Lets Encrypt",
      "CN": "E7"
    },
    "subject": {
      "CN": "*.wikipedia.org"
    },
    "serialNumber": "05E99AFAE9E9285C9A6B8CA6FEFF26C23F9B",
    "fingerprint": "28:F1:C8:C5:9F:B5:BC:B6:B6:37:54:D7:A4:E7:21:61:38:D3:AB:D7",
    "fingerprint256": "D8:BB:C0:CA:A9:93:C7:BA:CA:E3:11:33:64:69:5A:BA:BF:CE:12:94:95:F3:E0:28:39:E5:B8:AC:8D:DA:1B:78",
    "keyUsage": [
      "1.3.6.1.5.5.7.3.1",
      "1.3.6.1.5.5.7.3.2"
    ],
    "subjectAltName": "DNS:*.m.mediawiki.org, DNS:*.m.wikibooks.org, DNS:*.m.wikidata.org, DNS:*.m.wikimedia.org, DNS:*.m.wikinews.org, DNS:*.m.wikipedia.org, DNS:*.m.wikiquote.org, DNS:*.m.wikisource.org, DNS:*.m.wikiversity.org, DNS:*.m.wikivoyage.org, DNS:*.m.wiktionary.org, DNS:*.mediawiki.org, DNS:*.planet.wikimedia.org, DNS:*.wikibooks.org, DNS:*.wikidata.org, DNS:*.wikifunctions.org, DNS:*.wikimedia.org, DNS:*.wikimediafoundation.org, DNS:*.wikinews.org, DNS:*.wikipedia.org, DNS:*.wikiquote.org, DNS:*.wikisource.org, DNS:*.wikiversity.org, DNS:*.wikivoyage.org, DNS:*.wiktionary.org, DNS:*.wmfusercontent.org, DNS:mediawiki.org, DNS:w.wiki, DNS:wikibooks.org, DNS:wikidata.org, DNS:wikifunctions.org, DNS:wikimedia.org, DNS:wikimediafoundation.org, DNS:wikinews.org, DNS:wikipedia.org, DNS:wikiquote.org, DNS:wikisource.org, DNS:wikiversity.org, DNS:wikivoyage.org, DNS:wiktionary.org, DNS:wmfusercontent.org",
    "cipher": {
      "name": "TLS_AES_128_GCM_SHA256",
      "standardName": "TLS_AES_128_GCM_SHA256",
      "version": "TLSv1.3"
    },
    "protocol": "TLSv1.3",
    "authorized": true,
    "authorizationError": null
  }
}

Where the data comes from

Source: Live TLS handshake with the target host. No stored dataset.
Freshness: Checked live on every call.

One install. Every endpoint.

No proprietary SDKs needed. Any HTTP client works. Pick your language and paste.

3languages

1endpoints

RESTarchitecture

1key for all APIs

Fully typed responses — auto-completion in your IDE
Tracks the API in lockstep — new endpoints land same day
One key works across 125+ APIs on the platform

import axios from 'axios';

const { data } = await axios.get(
  'https://ssl-checker-api.dataandapis.com/v1/check',
  { headers: { 'X-Api-Key': process.env.API_KEY } }
);

SSL Checker Api · X-Api-Key

Explore the endpoints

Browse request parameters and inspect live example responses.

Available Endpoints

Request Parameters

API URL

Headers

X-Api-Key

Query Parameters

hostname(Required)

port(Optional)

Target:

Client:

import axios from 'axios';

const url = 'https://ssl-checker-api.dataandapis.com/v1/check';
const { data } = await axios.get(url, {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' }
});