It provides complete SSL certificate chains for thorough validation, ensuring certificates in the chain are valid, enhancing overall security. It helps maintain a secure connection by verifying the authenticity of each certificate in the chain.
Monitor SSL certificate expiration dates effortlessly to ensure continuous website security. It enables you to track a domain's certificate expiration date, ensuring prompt renewal and avoiding potential downtime or security risks.
We parse SSL data thoroughly to give details in JSON/ XML format. This API provides details about the server including, common name and certificate issuer.
We support SSL lookup data retrieval in JSON and XML formats, offering flexibility and compatibility with various applications. This allows you to efficiently analyze and manage SSL certificate information across your systems.
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.
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.
All available TLDs are supported by SSL certificate lookup API.
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.
We provide surcharge requests on all active API credits subscriptions. You can fetch credits and surcharge requests information through our API. Each subscription plan has different surcharge requests limit.
No, We do not charge credits on 4xx status codes in response. All Whois APIs follow same rule for 4xx status codes in response.
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.
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.
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:
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 |
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 |
In case, the request per minute exceeds, it'll throw an error with HTTP error code of 429.
Yes, there are following three header parameters in the response: