SSL Certificate CheckerSSL Certificate Checker API

OnlineCredit Usage:1 per callLive Data
avg: 859ms|p50: 802ms|p75: 897ms|p90: 1010ms|p99: 1237ms

SSL Checker is a simple tool for checking SSL certificates. It returns the SSL certificate details of a website.

The SSL Certificate Checker API provides reliable and fast access to ssl certificate checker data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

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

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

Code Examples

Here are examples of how to call the SSL Certificate Checker API in different programming languages:

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/sslchecker?domain=ebay.com" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
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);
Python (Requests)
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)
Node.js (Native HTTPS)
const https = require('https');
const url = require('url');

const options = {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const req = https.request('https://api.apiverve.com/v1/sslchecker?domain=ebay.com', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.end();
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/sslchecker?domain=ebay.com');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
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))
}
Ruby (Net::HTTP)
require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/sslchecker?domain=ebay.com')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))
C# (HttpClient)
using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        var response = await client.GetAsync("https://api.apiverve.com/v1/sslchecker?domain=ebay.com");
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

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

Required 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:

Check SSL Certificate

ParameterTypeRequiredDescriptionDefaultExample
domainstringrequired
The domain of the website to check the SSL certificate of
Format: domain (e.g., ebay.com)
-ebay.com

Response

The SSL Certificate Checker API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

JSON Response
200 OK
{
  "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"
  }
}
XML Response
200 OK
<?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>
YAML Response
200 OK
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
CSV Response
200 OK
keyvalue
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}
subjectaltnameDNS: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]}
cafalse
bits2048
valid_fromJul 28 00:00:00 2025 GMT
valid_toJul 28 23:59:59 2026 GMT
serialNumber99F408949A6416EDC3B8F5EC77B2EBE5
domainebay.com

Response Structure

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

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

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

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
subjectPremiumobject{...}Certificate subject information including country, state, organization, and common name
â”” CPremiumstring"US"Country code of the certificate subject
â”” STPremiumstring"California"State or province of the certificate subject
â”” OPremiumstring"eBay, Inc."Organization name of the certificate subject
â”” CNPremiumstring"ebay.com"Common name of the certificate subject domain
issuerPremiumobject{...}Certificate issuing authority information including country, organization, and common name
â”” CPremiumstring"GB"Country code of the certificate issuer
â”” OPremiumstring"Sectigo Limited"Organization name of the certificate issuing authority
â”” CNPremiumstring"Sectigo Public Server Authentication CA OV R36"Common name of the certificate authority
subjectaltnamePremiumstring"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"Alternative subject names included in the certificate
infoAccessPremiumobject{...}Information access extension with CA issuers and OCSP URIs
â”” CA Issuers - URIPremiumarray["http://crt.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crt"]URLs to CA issuer certificates for validation
â”” OCSP - URIPremiumarray["http://ocsp.sectigo.com"]Online Certificate Status Protocol URLs for validation
cabooleanfalseIndicates if certificate is a certificate authority
bitsnumber2048Key size in bits representing certificate strength
valid_fromstring"Jul 28 00:00:00 2025 GMT"Certificate validity start date and time in GMT
valid_tostring"Jul 28 23:59:59 2026 GMT"Certificate validity end date and time in GMT
serialNumberPremiumstring"99F408949A6416EDC3B8F5EC77B2EBE5"Unique serial number of the SSL certificate
domainstring"ebay.com"Domain name the certificate was checked for

Headers

Required and optional headers for SSL Certificate Checker API requests:

Header NameRequiredExample ValueDescription
X-API-Keyrequiredyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
Acceptoptionalapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentoptionalMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDoptionalreq_123456789Custom request identifier for tracking and debugging requests
Cache-Controloptionalno-cacheControl caching behavior for the request and response

Learn more about 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.

Test SSL Certificate Checker in the GraphQL Explorer to confirm availability and experiment with queries.

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

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
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 supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call SSL Certificate Checker directly from browser-based applications without proxy servers.

CORS HeaderValueDescription
Access-Control-Allow-Origin*Accepts requests from any origin
Access-Control-Allow-Methods*Accepts any HTTP method
Access-Control-Allow-Headers*Accepts any request headers

Browser Usage: You can call SSL Certificate Checker directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

SSL Certificate Checker API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all SSL Certificate Checker users.

PlanRate LimitDescription
Free5 requests/minHard rate limit enforced - exceeding will return 429 errors
StarterNo LimitProduction ready - standard traffic priority
ProNo LimitProduction ready - preferred traffic priority
MegaNo LimitProduction ready - highest traffic priority

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each SSL Certificate Checker response includes headers to help you track your usage:

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per time window
X-RateLimit-RemainingNumber of requests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

Handling Rate Limits

Free Plan: When you exceed your rate limit, SSL Certificate Checker returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for SSL Certificate Checker:

  • Monitor the rate limit headers to track your SSL Certificate Checker usage (Free plan only)
  • Cache ssl certificate checker responses where appropriate to reduce API calls
  • Upgrade to Pro or Mega for guaranteed no-throttle SSL Certificate Checker performance

Note: SSL Certificate Checker rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using SSL Certificate Checker on Free tier.

Error Codes

The SSL Certificate Checker API uses standard HTTP status codes to indicate success or failure:

CodeMessageDescriptionSolution
200OKRequest successful, data returnedNo action needed - request was successful
400Bad RequestInvalid request parameters or malformed requestCheck required parameters and ensure values match expected formats
401UnauthorizedMissing or invalid API keyInclude x-api-key header with valid API key from dashboard
403ForbiddenAPI key lacks permission or insufficient creditsCheck credit balance in dashboard or upgrade plan
429Too Many RequestsRate limit exceeded (Free: 5 req/min)Implement request throttling or upgrade to paid plan
500Internal Server ErrorServer error occurredRetry request after a few seconds, contact support if persists
503Service UnavailableAPI temporarily unavailableWait and retry, check status page for maintenance updates

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate SSL Certificate Checker with SDKs

Get started quickly with official SSL Certificate Checker SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

Integrate SSL Certificate Checker with No-Code API Tools

Connect the SSL Certificate Checker API to your favorite automation platform without writing code. Build workflows that leverage ssl certificate checker data across thousands of apps.

All platforms use your same API key to access SSL Certificate Checker. Visit our integrations hub for step-by-step setup guides.

Frequently Asked Questions

How do I get an API key for SSL Certificate Checker?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for SSL Certificate Checker and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does SSL Certificate Checker cost?

Each successful SSL Certificate Checker API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful ssl certificate checker lookups.

Can I use SSL Certificate Checker in production?

The free plan is for testing and development only. For production use of SSL Certificate Checker, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use SSL Certificate Checker from a browser?
Yes! The SSL Certificate Checker API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my SSL Certificate Checker credit limit?

When you reach your monthly credit limit, SSL Certificate Checker API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?