SSL Certificate Checker API

Overview

To use SSL Certificate Checker, you need an API key. You can get one by creating a free account and visiting your dashboard.

GET Endpoint

https://api.apiverve.com/v1/sslchecker

Example

How to call the SSL Certificate Checker API in different programming languages.

curl -X GET \
  "https://api.apiverve.com/v1/sslchecker?domain=ebay.com" \
  -H "X-API-Key: your_api_key_here"

const response = await fetch('https://api.apiverve.com/v1/sslchecker?domain=ebay.com', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);

import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/sslchecker?domain=ebay.com', headers=headers)

data = response.json()
print(data)

package main

import (
    "fmt"
    "io"
    "net/http"

)

func main() {
    req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/sslchecker?domain=ebay.com", nil)

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

{
  "status": "ok",
  "error": null,
  "data": {
    "subject": {
      "C": "US",
      "ST": "California",
      "O": "eBay, Inc.",
      "CN": "ebay.com"
    },
    "issuer": {
      "C": "GB",
      "O": "Sectigo Limited",
      "CN": "Sectigo Public Server Authentication CA OV R36"
    },
    "subjectaltname": "DNS:ebay.com, DNS:befr.ebay.be, DNS:benl.ebay.be, DNS:cafr.ebay.ca, DNS:e-bay.it, DNS:ebay.at, DNS:ebay.be, DNS:ebay.ca, DNS:ebay.ch, DNS:ebay.co.uk, DNS:ebay.com.au, DNS:ebay.com.hk, DNS:ebay.com.my, DNS:ebay.com.sg, DNS:ebay.de, DNS:ebay.es, DNS:ebay.fr, DNS:ebay.ie, DNS:ebay.in, DNS:ebay.it, DNS:ebay.nl, DNS:ebay.ph, DNS:ebay.pl, DNS:ebay.us, DNS:ebay.vn, DNS:wwww.ebay.co.uk, DNS:wwww.ebay.com, DNS:wwww.ebay.com.au, DNS:wwww.ebay.de, DNS:wwww.ebay.in, DNS:wwww.ebay.it",
    "infoAccess": {
      "CA Issuers - URI": [
        "http://crt.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crt"
      ],
      "OCSP - URI": [
        "http://ocsp.sectigo.com"
      ]
    },
    "ca": false,
    "bits": 2048,
    "valid_from": "Jul 28 00:00:00 2025 GMT",
    "valid_to": "Jul 28 23:59:59 2026 GMT",
    "serialNumber": "99F408949A6416EDC3B8F5EC77B2EBE5",
    "domain": "ebay.com"
  }
}

Authentication

The SSL Certificate Checker API requires authentication via API key. Include your API key in the request header:

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the SSL Certificate Checker API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the SSL Certificate Checker API:

Response

The SSL Certificate Checker API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <subject>
      <C>US</C>
      <ST>California</ST>
      <O>eBay, Inc.</O>
      <CN>ebay.com</CN>
    </subject>
    <issuer>
      <C>GB</C>
      <O>Sectigo Limited</O>
      <CN>Sectigo Public Server Authentication CA OV R36</CN>
    </issuer>
    <subjectaltname>DNS:ebay.com, DNS:befr.ebay.be, DNS:benl.ebay.be, DNS:cafr.ebay.ca, DNS:e-bay.it, DNS:ebay.at, DNS:ebay.be, DNS:ebay.ca, DNS:ebay.ch, DNS:ebay.co.uk, DNS:ebay.com.au, DNS:ebay.com.hk, DNS:ebay.com.my, DNS:ebay.com.sg, DNS:ebay.de, DNS:ebay.es, DNS:ebay.fr, DNS:ebay.ie, DNS:ebay.in, DNS:ebay.it, DNS:ebay.nl, DNS:ebay.ph, DNS:ebay.pl, DNS:ebay.us, DNS:ebay.vn, DNS:wwww.ebay.co.uk, DNS:wwww.ebay.com, DNS:wwww.ebay.com.au, DNS:wwww.ebay.de, DNS:wwww.ebay.in, DNS:wwww.ebay.it</subjectaltname>
    <infoAccess>
      <CA_Issuers___URI>
        <item>http://crt.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crt</item>
      </CA_Issuers___URI>
      <OCSP___URI>
        <item>http://ocsp.sectigo.com</item>
      </OCSP___URI>
    </infoAccess>
    <ca>false</ca>
    <bits>2048</bits>
    <valid_from>Jul 28 00:00:00 2025 GMT</valid_from>
    <valid_to>Jul 28 23:59:59 2026 GMT</valid_to>
    <serialNumber>99F408949A6416EDC3B8F5EC77B2EBE5</serialNumber>
    <domain>ebay.com</domain>
  </data>
</response>

status: ok
error: null
data:
  subject:
    C: US
    ST: California
    O: eBay, Inc.
    CN: ebay.com
  issuer:
    C: GB
    O: Sectigo Limited
    CN: Sectigo Public Server Authentication CA OV R36
  subjectaltname: >-
    DNS:ebay.com, DNS:befr.ebay.be, DNS:benl.ebay.be, DNS:cafr.ebay.ca,
    DNS:e-bay.it, DNS:ebay.at, DNS:ebay.be, DNS:ebay.ca, DNS:ebay.ch,
    DNS:ebay.co.uk, DNS:ebay.com.au, DNS:ebay.com.hk, DNS:ebay.com.my,
    DNS:ebay.com.sg, DNS:ebay.de, DNS:ebay.es, DNS:ebay.fr, DNS:ebay.ie,
    DNS:ebay.in, DNS:ebay.it, DNS:ebay.nl, DNS:ebay.ph, DNS:ebay.pl,
    DNS:ebay.us, DNS:ebay.vn, DNS:wwww.ebay.co.uk, DNS:wwww.ebay.com,
    DNS:wwww.ebay.com.au, DNS:wwww.ebay.de, DNS:wwww.ebay.in, DNS:wwww.ebay.it
  infoAccess:
    CA Issuers - URI:
      - http://crt.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crt
    OCSP - URI:
      - http://ocsp.sectigo.com
  ca: false
  bits: 2048
  valid_from: Jul 28 00:00:00 2025 GMT
  valid_to: Jul 28 23:59:59 2026 GMT
  serialNumber: 99F408949A6416EDC3B8F5EC77B2EBE5
  domain: ebay.com

Response Structure

All API responses follow a consistent structure with the following fields:

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access SSL Certificate Checker through GraphQL to combine it with other API calls in a single request. Query only the ssl certificate checker data you need with precise field selection, and orchestrate complex data fetching workflows.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

POST https://api.apiverve.com/v1/graphql

query {
  sslchecker(
    input: {
      domain: "ebay.com"
    }
  ) {
    subject {
      C
      ST
      O
      CN
    }
    issuer {
      C
      O
      CN
    }
    subjectaltname
    infoAccess {
      CA Issuers _ URI
      OCSP _ URI
    }
    ca
    bits
    valid_from
    valid_to
    serialNumber
    domain
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The SSL Certificate Checker API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

SSL Certificate Checker requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The SSL Certificate Checker API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for SSL Certificate Checker

Official SSL Certificate Checker packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

SSL Certificate Checker works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in SSL Certificate Checker, you might also like these APIs:

WHOIS Lookup

Whois Lookup is a simple tool for checking the registration of a domain name. It returns the name and contact information of the domain owner, the domain registrar, and more.

10 credits per call

URL Unshortener

URL Unshortener is a simple tool for unshortening shortened URLs. It returns the original URL before it was shortened.

5 credits per call

URL Title

URL Title is a simple tool for getting the title of a web page. It returns the title of the web page based on the URL provided.

5 credits per call