{"isvalidCertificate":true,"canBeSelfSigned":false,"isWildCard":true,"isExpired":false,"message":"Valid Certificate","expiry":"2025-07-27","daysLeft":225,"lifespanInDays":335,"issuer":"DigiCert Global CA G2 DigiCert Inc","certDetails":{"name":"\/CN=*.peg.a2z.com","subject":{"CN":"*.peg.a2z.com"},"hash":"3cae1f61","issuer":{"C":"US","O":"DigiCert Inc","CN":"DigiCert Global CA G2"},"version":2,"serialNumber":"4891915750396980015937368629838977478","serialNumberHex":"03AE261164DB2D8F280B8821F48199C6","validFrom":"240826000000Z","validTo":"250727235959Z","validFrom_time_t":1724630400,"validTo_time_t":1753660799,"signatureTypeSN":"RSA-SHA256","signatureTypeLN":"sha256WithRSAEncryption","signatureTypeNID":668,"purposes":{"1":[true,false,"sslclient"],"2":[true,false,"sslserver"],"3":[true,false,"nssslserver"],"4":[false,false,"smimesign"],"5":[false,false,"smimeencrypt"],"6":[false,false,"crlsign"],"7":[true,true,"any"],"8":[true,false,"ocsphelper"],"9":[false,false,"timestampsign"]},"extensions":{"authorityKeyIdentifier":"24:6E:2B:2D:D0:6A:92:51:51:25:69:01:AA:9A:47:A6:89:E7:40:20","subjectKeyIdentifier":"DB:DB:B1:DA:10:24:B4:C7:1A:82:93:C7:01:23:88:CF:0D:C3:E5:0D","subjectAltName":"DNS:amazon.co.uk, DNS:uedata.amazon.co.uk, DNS:www.amazon.co.uk, DNS:origin-www.amazon.co.uk, DNS:*.peg.a2z.com, DNS:amazon.com, DNS:amzn.com, DNS:uedata.amazon.com, DNS:us.amazon.com, DNS:www.amazon.com, DNS:www.amzn.com, DNS:corporate.amazon.com, DNS:buybox.amazon.com, DNS:iphone.amazon.com, DNS:yp.amazon.com, DNS:home.amazon.com, DNS:origin-www.amazon.com, DNS:origin2-www.amazon.com, DNS:buckeye-retail-website.amazon.com, DNS:huddles.amazon.com, DNS:amazon.de, DNS:www.amazon.de, DNS:origin-www.amazon.de, DNS:amazon.co.jp, DNS:amazon.jp, DNS:www.amazon.jp, DNS:www.amazon.co.jp, DNS:origin-www.amazon.co.jp, DNS:*.aa.peg.a2z.com, DNS:*.ab.peg.a2z.com, DNS:*.ac.peg.a2z.com, DNS:origin-www.amazon.com.au, DNS:www.amazon.com.au, DNS:*.bz.peg.a2z.com, DNS:amazon.com.au, DNS:origin2-www.amazon.co.jp, DNS:edgeflow.aero.4d5ad1d2b-frontier.amazon.co.jp, DNS:edgeflow.aero.04f01a85e-frontier.amazon.com.au, DNS:edgeflow.aero.47cf2c8c9-frontier.amazon.com, DNS:edgeflow.aero.abe2c2f23-frontier.amazon.de, DNS:edgeflow.aero.bfbdc3ca1-frontier.amazon.co.uk, DNS:edgeflow-dp.aero.4d5ad1d2b-frontier.amazon.co.jp, DNS:edgeflow-dp.aero.04f01a85e-frontier.amazon.com.au, DNS:edgeflow-dp.aero.47cf2c8c9-frontier.amazon.com, DNS:edgeflow-dp.aero.bfbdc3ca1-frontier.amazon.co.uk, DNS:edgeflow-dp.aero.abe2c2f23-frontier.amazon.de","certificatePolicies":"Policy: 2.23.140.1.2.1\n CPS: http:\/\/www.digicert.com\/CPS","keyUsage":"Digital Signature, Key Encipherment","extendedKeyUsage":"TLS Web Server Authentication, TLS Web Client Authentication","crlDistributionPoints":"Full Name:\n URI:http:\/\/crl3.digicert.com\/DigiCertGlobalCAG2.crl\nFull Name:\n URI:http:\/\/crl4.digicert.com\/DigiCertGlobalCAG2.crl","authorityInfoAccess":"OCSP - URI:http:\/\/ocsp.digicert.com\nCA Issuers - URI:http:\/\/cacerts.digicert.com\/DigiCertGlobalCAG2.crt","basicConstraints":"CA:FALSE","ct_precert_scts":"Signed Certificate Timestamp:\n Version : v1 (0x0)\n Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:\n 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A\n Timestamp : Aug 26 17:46:50.162 2024 GMT\n Extensions: none\n Signature : ecdsa-with-SHA256\n 30:46:02:21:00:86:83:64:1B:5C:A8:AC:61:D7:81:C6:\n A0:C7:53:37:11:D9:FD:27:AB:29:92:C1:3F:2F:A5:59:\n 40:2B:3F:1C:5C:02:21:00:E0:0A:6D:A2:F2:C4:98:78:\n 93:2A:C5:CF:F5:98:DA:E3:4B:56:89:1F:2D:63:B9:A2:\n 39:96:B8:EF:EB:CA:30:8D\nSigned Certificate Timestamp:\n Version : v1 (0x0)\n Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:\n D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50\n Timestamp : Aug 26 17:46:50.178 2024 GMT\n Extensions: none\n Signature : ecdsa-with-SHA256\n 30:45:02:20:65:F5:3D:C3:2A:8F:C6:C0:BC:7F:BF:37:\n 5C:15:A9:B9:FA:F9:EE:65:C2:DC:18:DC:5C:7F:73:59:\n 3B:79:A0:5A:02:21:00:EE:45:E3:C5:29:68:6A:23:EE:\n FF:8E:D9:F3:86:F4:8F:34:68:FF:6E:D8:8F:FA:6E:70:\n D5:17:6F:FB:CC:FD:4C\nSigned Certificate Timestamp:\n Version : v1 (0x0)\n Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:\n 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0\n Timestamp : Aug 26 17:46:50.170 2024 GMT\n Extensions: none\n Signature : ecdsa-with-SHA256\n 30:46:02:21:00:E6:5E:B5:34:70:3A:EE:D7:A6:40:6C:\n 35:5F:FE:97:AA:1A:48:C7:76:83:38:9D:76:4F:79:3D:\n 60:3C:E6:BA:15:02:21:00:8E:A1:3E:51:CB:3A:F6:01:\n 64:1C:D6:86:E6:B3:F4:48:5B:9B:27:80:EE:CB:E9:93:\n 95:15:69:41:AC:A9:98:93"},"validLeft":225},"apiVersion":2,"error":false}
curl --location --request GET 'https://pr213-testing.zylalabs.com/api/4984/ssl+verify+api/6288/ssl+verify?domain=amazon.com' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the SSL Verify API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
SSL Verify API is a crucial tool for ensuring the security and integrity of web communications. This API is designed to verify the validity and configuration of a website's SSL (Secure Sockets Layer) certificates, ensuring that connections are secure and comply with the latest encryption standards.
SSL is a security protocol that encrypts information transmitted between a web browser and a server, protecting sensitive data, such as passwords, credit card information and personal data, during transfer. Proper implementation of SSL is essential to maintain data confidentiality and integrity, as well as to protect users against cyber-attacks and vulnerabilities.
The SSL Verify API makes it easy to monitor and maintain website security by providing a number of advanced features for evaluating SSL certificates. By using this API, website administrators and users can ensure that their SSL certificates are up to date and configured correctly, avoiding issues that could compromise the security of their users.
To use the SSL Verify API, users submit a request to the API that includes the URL of the Web site whose SSL certificate they wish to verify. The API responds with detailed information about the site's SSL certificate, including its validity, expiration date, issuing certificate authority (CA) and the details of the encryption used. This allows administrators and developers to detect problems such as expired certificates, incorrect configurations or weaknesses in encryption algorithms.
This API receives the URL of a website and returns details about the SSL certificate, including its validity, expiration date and encryption settings.
Web Security Monitoring: Use the API to periodically verify website SSL certificates to ensure they are up-to-date and configured correctly, protecting site security.
Expired Certificate Detection: Implement the API in alerting systems to notify administrators when an SSL certificate is about to expire, preventing site security disruptions.
Compliance Audits: Integrate the API into auditing processes to verify that all SSL certificates in an organization meet security requirements and industry standards.
Multiple Certificate Management: Use the API to manage and verify multiple SSL certificates in an infrastructure with multiple domains or subdomains, ensuring that all are current and correctly configured.
Encryption Configuration Optimization: Apply the API to evaluate and improve encryption configuration on web servers, ensuring the use of current and secure encryption algorithms and protocols.
Basic Plan: 2 requests per second.
Pro Plan: 5 requests per second.
Pro Plus Plan: 5 requests per second.
Send a request to the endpoint with the site URL. You will receive details about the verified SSL certificate.
The SSL Verify API verifies SSL certificates of web sites, providing details about their validity, expiration and encryption configuration
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The API returns detailed information about the age and history of a domain, including years, months and days since its creation, as well as expiration and update dates.
The SSL Verify API returns detailed information about an SSL certificate, including its validity status, expiration date, issuer details, and encryption settings.
Key fields in the response include `isvalidCertificate`, `expiry`, `issuer`, `isExpired`, and `certDetails`, which provide insights into the certificate's status and configuration.
The response is structured in JSON format, with a top-level object containing boolean flags, dates, and nested objects for detailed certificate information, making it easy to parse.
The API provides information on certificate validity, expiration dates, issuer details, encryption algorithms, and whether the certificate is self-signed or a wildcard.
Users can customize requests by specifying the URL of the website they wish to verify, allowing for targeted checks on specific domains or subdomains.
`isvalidCertificate` indicates if the certificate is valid, `expiry` shows the expiration date, and `issuer` provides details about the certificate authority that issued the SSL certificate.
Data accuracy is maintained through regular updates and checks against trusted certificate authorities, ensuring that the information reflects the current status of SSL certificates.
Typical use cases include monitoring SSL certificate validity, detecting expired certificates, ensuring compliance with security standards, and optimizing encryption configurations for web servers.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund