Instantly Validate Any Website’s SSL with Our Live SSL Certificate Lookup API

Quickly verify any website’s SSL certificate, expiration, and authenticity in real time using SSL Lookup API.

curl --location --request GET 'https://api.whoisfreaks.com/v1.0/ssl/live?apiKey=API_KEY&domainName=whoisfreaks.com&chain=true&sslRaw=true'
[
  {
    "domainName": "whoisfreaks.com",
    "queryTime": "2024-10-04 07:17:04",
    "sslCertificates": [
      {
        "chainOrder": "end-user",
        "authenticationType": "domain",
        "validityStartDate": "2024-09-7 23:03:18 UTC",
        "validityEndDate": "2024-12-6 23:03:17 UTC",
        "serialNumber": "04:8e:90:ab:b3:ec:32:10:1e:de:83:4a:e8:9c:3c:e7:1e:a7",
        "signatureAlgorithm": "ECDSA-SHA2384",
        "subject": {
          "commonName": "whoisfreaks.com"
        },
        "issuer": {
          "commonName": "E6",
          "organization": "Let's Encrypt",
          "country": "US"
        },
        "publicKey": {
          "keySize": "256 bit",
          "keyAlgorithm": "ECDSA"
        },
        "extensions": {
          "authorityKeyIdentifier": "93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2",
          "subjectKeyIdentifier": "95:B1:F8:43:43:1B:A9:D9:A0:73:E6:F7:BF:FB:34:D8:DE:69:CC:39",
          "keyUsages": [
            "Digital Signature"
          ],
          "extendedKeyUsages": [
            "TLS Web Server Authentication",
            "TLS Web Client Authentication"
          ],
          "authorityInfoAccess": {
            "issuers": [
              "http://e6.i.lencr.org/"
            ],
            "ocsp": [
              "http://e6.o.lencr.org"
            ]
          },
          "subjectAlternativeNames": {
            "dnsNames": [
              "www.whoisfreaks.com",
              "whoisfreaks.com"
            ]
          },
          "certificatePolicies": [
            {
              "policyId": "2.23.140.1.2.1"
            }
          ]
        }
      },
      {
        "chainOrder": "intermediate",
        "authenticationType": "organization",
        "validityStartDate": "2024-03-13 00:00:00 UTC",
        "validityEndDate": "2027-03-12 23:59:59 UTC",
        "serialNumber": "b0:57:3e:91:73:97:27:70:db:b4:87:cb:3a:45:2b:38",
        "signatureAlgorithm": "SHA256-RSA",
        "subject": {
          "commonName": "E6",
          "organization": "Let's Encrypt",
          "country": "US"
        },
        "issuer": {
          "commonName": "ISRG Root X1",
          "organization": "Internet Security Research Group",
          "country": "US"
        },
        "publicKey": {
          "keySize": "384 bit",
          "keyAlgorithm": "ECDSA"
        },
        "extensions": {
          "authorityKeyIdentifier": "79:B4:59:E6:7B:B6:E5:E4:01:73:80:08:88:C8:1A:58:F6:E9:9B:6E",
          "subjectKeyIdentifier": "93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2",
          "keyUsages": [
            "CRL Sign",
            "Digital Signature",
            "Certificate Sign"
          ],
          "extendedKeyUsages": [
            "TLS Web Server Authentication",
            "TLS Web Client Authentication"
          ],
          "authorityInfoAccess": {
            "issuers": [
              "http://x1.i.lencr.org/"
            ]
          },
          "certificatePolicies": [
            {
              "policyId": "2.23.140.1.2.1"
            }
          ]
        }
      },
      {
        "chainOrder": "root",
        "authenticationType": "self-signed-ca",
        "validityStartDate": "2015-06-4 11:04:38 UTC",
        "validityEndDate": "2035-06-4 11:04:38 UTC",
        "serialNumber": "82:10:cf:b0:d2:40:e3:59:44:63:e0:bb:63:82:8b:00",
        "signatureAlgorithm": "SHA256-RSA",
        "subject": {
          "commonName": "ISRG Root X1",
          "organization": "Internet Security Research Group",
          "country": "US"
        },
        "issuer": {
          "commonName": "ISRG Root X1",
          "organization": "Internet Security Research Group",
          "country": "US"
        },
        "publicKey": {
          "keySize": "4096 bit",
          "keyAlgorithm": "RSA"
        },
        "extensions": {
          "subjectKeyIdentifier": "79:B4:59:E6:7B:B6:E5:E4:01:73:80:08:88:C8:1A:58:F6:E9:9B:6E",
          "keyUsages": [
            "CRL Sign",
            "Certificate Sign"
          ]
        }
      }
    ]
  }
]
pricing backgroundEclipse Top RightEclipse Top LeftEclipse WHOIS Stats

Product

SSL Certificate API

Ensure your website’s authenticity and security by checking SSL certificate details, expiration, and encryption status with our Live Lookup API.

SSL Certificate Lookup API

SSL certificate lookup API allows you to fetch live streaming Secure Sockets Layer (SSL) certificate along with its complete SSL cert chain to provide up-to-date and consistent data.

monitoring

Features

What our SSL Lookup API Provide

Access comprehensive SSL certificate data with our API to validate, monitor, and ensure website security in real time.

Feature icon

Comprehensive Chain

Validates complete chain to ensure authenticity and strengthen website security.

Feature icon

Comprehensive data

Thoroughly parse SSL data and get server details like common name and certificate issuer.

Feature icon

SSL Expiry Monitoring

Monitor SSL certificate expiration dates effortlessly to ensure continuous website security.

Feature icon

Supported Formats

Easily retrieve SSL lookup data in JSON or XML, offering flexibility and seamless integration.

Use Cases

SSL Certificate Action

See how SSL Lookup API can be used for brand protection and typosquatting defense.

Feature icon

Trust Badge

This API allows you to know which domains are trustworthy and which are not in the chain for faster risk-based decisions.

Feature icon

Certificate Chain Monitoring

Monitor expiring SSL certificates and detect changes to prevent domain takeover before outages and security incidents occur.

Feature icon

3rd Party & Typosquatting Attacks

Check SSL certificate validation to identify self-signed certificates and prevent MITM or typosquatting attacks.

Feature icon

Real Time Data

Access well-parsed, real-time SSL certificate data in JSON or XML for seamless integration with third party applications.

Feature icon

Data Enrichment

SSL certificate chain lookup helps uncover inconsistencies that may indicate exploitable security vulnerabilities.

Feature icon

Compliance & Auditing

Monitor and validate SSL certificates to ensure compliance and generate audit-ready reports using SSL Lookup API.

Request demo background

Stay secure and informed by monitoring SSL certificates with real-time data. Track expirations, detect certificate changes, and support faster incident response.

pricing background

Documentation

SSL Live Lookup

The Live SSL Lookup API retrieves the real‑time SSL certificate of a domain and, when the chain parameter is set to true, also returns the complete certificate chain. Additionally, you can obtain the raw OpenSSL response by setting the sslRaw parameter to true.

Authorization

You can make authorized requests to our API by passing API key as a query parameter. To get your API key, login to our billing dashboard and get your API key! If your API key has been compromised, you can change it by clicking on reset button in billing dashboard.

Query Parameters

Required
  • apiKey
    Get your API key from our billing dashboard.
  • domainName
    The domainName for requested ssl data.
Optional
  • chain
    For getting the chain of all domain ssl certificates sorted from end-user to root. Default value is "false"
  • sslRaw
    For getting the raw openssl response of the domain. Default value is "false"
  • format
    Two formats are available JSON, XML. If you don't specify the 'format' parameter, the default format will be JSON.

Request

shellnodejsjavapythonphprubyjscsharpgocswiftjquery
SHELL
Loading request...

Response

Loading response...

Status Codes

Success Codes
  • 200  Request is processed successfully.
Failure Codes
  • 400  Please pass domain param correct value e.g. whoisfreaks.com, https://whoisfreaks.com, http://whoisfreaks.com
  • 401  Provided API key is invalid.
  • 401  Provided API key is inactive.
  • 401  Please buy a subscription plan or add api credits, then use this api key.
  • 401  Your subscription is deactivated. Please buy new plan or add api credits for using whoisfreaks APIs.
  • 401  Your subscription is deactivated due to much time payment failure. Please buy a new plan or add api credits for using whoisfreaks APIs.
  • 401  Your account is deactivated.
  • 401  You are blocked due to suspicious activity.
  • 404  No Ssl Certificate exists for this Domain
  • 412  You have exceeded the limit of api plan requests and your subscription is canceled.
  • 413  You have exceeded the limit of api credits requests [allowed_request_no]. Please upgrade your plan.
  • 413  You have exceeded the limit of Surcharge Requests [allowed_surcharge_request_no]. Please upgrade your plan.
  • 429  Please slow down. Your maximum request limit per minute is reached.
  • 500  Internal Server error occurred.
  • 503  Service is unavailable. Please try after some time.
  • 504  Request is timed-out.

FAQs

Common questions on SSL integration: rate limits, errors, and interpreting certificate metadata.

What is the SSL certificate?

SSL (Secure Sockets Layer) is a cryptographic protocol that ensures data transferred between the web browser and the web server remains private. It also prevents cybercriminals from reading and modifying any transaction done between them such as the transmission of sensitive information like credit card while doing online shopping.

What is meant by SSL Certificate Chain?

The SSL chain is a list of certificates used to authenticate an end-user. The path, begins with the certificate of that end-user and each cert in the chain is signed by the entity identified by the next cert in the chain. The chain ends with a root CA cert. The signatures of all certs in the chain must be verified until the root CA certificate is reached.

Which TLDs are supported by your system?

All available TLDs are supported by SSL certificate lookup API.

Do you have notification service when API credits are near to an end?

Yes, we will inform you via an email. We send notification email on 80%,90%,100% usage. You can get credits/ subscription usage information from our billing portal or through API.

Do you charge credit on 4xx error status codes in response?

No, We do not charge credits on 4xx status codes in response. All WHOIS APIs follow same rule for 4xx status codes in response.

What is the number of free API credits available for new users, and are these credits rate-limited?

We will provide 500 API credits to new users and yes, those credits have a rate-limiting of 10 requests per minute for Live APIs, 5 requests per minute for Bulk Domain Lookup, and 1 request per minute for Reverse/Historical Endpoints.

What is meant by Live Lookup endpoint and how much data latency does it offer?

Our Live Lookup API offers real-time access to various endpoints, including domain whois, SSL and DNS data. By directly connecting to authoritative sources, this API ensures that you receive the most current and up-to-date information, eliminating data latency.

Do you have rate limiting on number of requests being made on your paid plans?

Yes, we have rate limiting on requests being made on all of our paid plans. The requests limit is shown in the following table.

The Table is divided into three types of plans:

1) API Credits

Credits Live-rpm Bulk-rpm Historical/Reverse-rpm
5000 20 8 3
15000 35 12 5
50000 80 20 10
150000 120 25 15
450000 150 35 20
1000000 200 50 25
3000000 300 70 35

2) API Subscription

Credits Live-rpm Bulk-rpm Historical/Reverse-rpm
5000 20 8 3
15000 35 12 5
50000 80 20 10
150000 120 25 15
450000 150 35 20
1000000 200 50 25
3000000 300 70 35
  • Live-rpm: API requests per minute limit for live WHOIS lookup API, domain availability API, SSL certificate lookup API, and DNS lookup API endpoints.
  • Bulk-rpm: API requests per minute limit for bulk domain WHOIS lookup API endpoint.
  • Historical/Reverse-rpm: API requests per minute limit for historical, and reverse WHOIS API endpoints.

In case, the request per minute exceeds, it'll throw an error with HTTP error code of 429.

Do you provide any headers in API response regarding rate limiting?

Yes, there are following three header parameters in the response:
  • X-RateLimit-Allowed-Requests: Tells the max allowed API requests per minute on a specific plan.
  • X-RateLimit-Remaining-Requests: Tells the remaining API requests per minute for that plan.
  • X-RateLimit-Remaining-Time: Tells after how much time the API requests per minute will be reset.

Ready to get started?

Join now and claim 500 credits for free!

Elevate your cybersecurity strategy with our all-in-one domain and IP intelligence platform empowering analysts, researchers, and brand owners with real-time WHOIS, DNS, IP, and subdomain insights.

Sign Up For Free