SSL Certificate Checker
SSL Checker is a simple tool for checking SSL certificates. It returns the SSL certificate details of a website.
This 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 this API, you need an API key. You can get one by creating a free account and visiting your dashboard.
View API in DirectoryEndpoint
GET https://api.apiverve.com/v1/sslcheckerCode Examples
Here are examples of how to call this 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', {
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', headers=headers)
data = response.json()
print(data)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', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/sslchecker');
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);
?>package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/sslchecker", 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))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/sslchecker')
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))Authentication
This API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereGraphQL AccessBETA
Most APIVerve APIs support GraphQL queries, allowing you to combine multiple API calls into a single request and retrieve only the data you need. This powerful feature enables you to orchestrate complex data fetching with precise field selection.
Not all APIs support GraphQL. Check the API schema or test in the GraphQL Explorer to confirm availability for this specific endpoint.
Token Cost: GraphQL requests cost 1 token for orchestration, plus the standard token cost for each API called in your query. For example, querying 3 APIs in a single GraphQL request would cost 1 + 3 = 4 tokens total.
POST https://api.apiverve.com/v1/graphqlquery {
sslchecker(
input: { domain: "ebay.com" }
) {
subject
issuer
subjectaltname
infoAccess
ca
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
Parameters
The following parameters are available for this API endpoint:
| Parameter | Type | Required | Location | Description | Example |
|---|---|---|---|---|---|
| domain | string | Yes | query | The domain of the website to check the SSL certificate of | ebay.com |
Response
The API returns responses in JSON, XML, and YAML formats:
Example Responses
{
"status": "ok",
"error": null,
"data": {
"subject": {
"C": "US",
"ST": "California",
"O": "eBay, Inc.",
"CN": "ebay.com"
},
"issuer": {
"C": "GB",
"ST": "Greater Manchester",
"L": "Salford",
"O": "Sectigo Limited",
"CN": "Sectigo RSA Organization Validation Secure Server CA"
},
"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",
"infoAccess": {
"CA Issuers - URI": [
"http://crt.sectigo.com/SectigoRSAOrganizationValidationSecureServerCA.crt"
],
"OCSP - URI": [
"http://ocsp.sectigo.com"
]
},
"ca": false,
"bits": 2048,
"valid_from": "Jan 8 00:00:00 2025 GMT",
"valid_to": "Jan 8 23:59:59 2026 GMT",
"serialNumber": "A89BCEBA167A33593AD3202C7FE2C420",
"domain": "ebay.com"
}
}<Root>
<status>ok</status>
<error />
<data>
<subject>
<C>US</C>
<ST>California</ST>
<O>eBay, Inc.</O>
<CN>ebay.com</CN>
</subject>
<issuer>
<C>GB</C>
<ST>Greater Manchester</ST>
<L>Salford</L>
<O>Sectigo Limited</O>
<CN>Sectigo RSA Organization Validation Secure Server CA</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</subjectaltname>
<infoAccess>
<CA_x0020_Issuers_x0020_-_x0020_URI>http://crt.sectigo.com/SectigoRSAOrganizationValidationSecureServerCA.crt</CA_x0020_Issuers_x0020_-_x0020_URI>
<OCSP_x0020_-_x0020_URI>http://ocsp.sectigo.com</OCSP_x0020_-_x0020_URI>
</infoAccess>
<ca>false</ca>
<bits>2048</bits>
<valid_from>Jan 8 00:00:00 2025 GMT</valid_from>
<valid_to>Jan 8 23:59:59 2026 GMT</valid_to>
<serialNumber>A89BCEBA167A33593AD3202C7FE2C420</serialNumber>
<domain>ebay.com</domain>
</data>
</Root>status: ok
error:
data:
subject:
C: US
ST: California
O: eBay, Inc.
CN: ebay.com
issuer:
C: GB
ST: Greater Manchester
L: Salford
O: Sectigo Limited
CN: Sectigo RSA Organization Validation Secure Server CA
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
infoAccess:
CA Issuers - URI:
- http://crt.sectigo.com/SectigoRSAOrganizationValidationSecureServerCA.crt
OCSP - URI:
- http://ocsp.sectigo.com
ca: false
bits: 2048
valid_from: Jan 8 00:00:00 2025 GMT
valid_to: Jan 8 23:59:59 2026 GMT
serialNumber: A89BCEBA167A33593AD3202C7FE2C420
domain: ebay.comResponse Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
| status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
| error | string | null | Contains error message if status is "error", otherwise null | null |
| data | object | null | Contains the API response data if successful, otherwise null | {...} |
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value |
|---|---|---|
| subject | object | {...} |
| subject.C | string | "US" |
| subject.ST | string | "California" |
| subject.O | string | "eBay, Inc." |
| subject.CN | string | "ebay.com" |
| issuer | object | {...} |
| issuer.C | string | "GB" |
| issuer.ST | string | "Greater Manchester" |
| issuer.L | string | "Salford" |
| issuer.O | string | "Sectigo Limited" |
| issuer.CN | string | "Sectigo RSA Organization Validation Secure Server CA" |
| subjectaltname | string | "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" |
| infoAccess | object | {...} |
| infoAccess.CA Issuers - URI | array | ["http://crt.sectigo.com/SectigoRSAOrganizationValidationSecureServerCA.crt"] |
| infoAccess.OCSP - URI | array | ["http://ocsp.sectigo.com"] |
| ca | boolean | false |
| bits | number | 2048 |
| valid_from | string | "Jan 8 00:00:00 2025 GMT" |
| valid_to | string | "Jan 8 23:59:59 2026 GMT" |
| serialNumber | string | "A89BCEBA167A33593AD3202C7FE2C420" |
Headers
Required and optional headers for API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
| X-API-Key | Yes | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
| Accept | No | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
| User-Agent | No | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
| X-Request-ID | No | req_123456789 | Custom request identifier for tracking and debugging requests |
| Cache-Control | No | no-cache | Control caching behavior for the request and response |
Client Libraries
To get started with minimal code, most of our APIs are available through client libraries and clients:
Error Codes
The API uses standard HTTP status codes to indicate success or failure:
| Status Code | Message | Description |
|---|---|---|
| 200 | OK | Request successful, data returned |
| 400 | Bad Request | Invalid request parameters or malformed request |
| 401 | Unauthorized | Missing or invalid API key |
| 403 | Forbidden | API key does not have permission for this endpoint |
| 429 | Too Many Requests | Rate limit exceeded, please slow down requests |
| 500 | Internal Server Error | Server error, please try again later |
Was this page helpful?
Help us improve our documentation




