The SSL Integrity Monitor API offers robust tools to analyze and verify SSL certificates for websites, protecting sensitive data during transmission. This API checks certificate validity, expiration, encryption protocols, and issuing authorities, ensuring a secure connection for users. With JSON-based responses, it seamlessly integrates into your workflows to automate certificate audits, detect vulnerabilities, and maintain compliance with evolving security standards, safeguarding against cyber threats.
{"isvalidCertificate":true,"canBeSelfSigned":false,"isWildCard":true,"isExpired":false,"message":"Valid Certificate","expiry":"2025-07-27","daysLeft":242,"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":242},"apiVersion":2,"error":false}
curl --location --request GET 'https://zylalabs.com/api/5643/ssl+integrity+monitor+api/7348/verify+ssl?domain=amazon.com' --header 'Authorization: Bearer YOUR_API_KEY'
| 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.
The SSL Integrity Monitor API is designed to analyze and verify SSL certificates for websites, ensuring the protection of sensitive data during transmission by checking certificate validity, expiration, encryption protocols, and issuing authorities.
The API automates certificate audits, detects vulnerabilities, and helps maintain compliance with evolving security standards, which is crucial for safeguarding against cyber threats.
You can retrieve information regarding SSL certificate validity, expiration dates, encryption details, and the issuing authorities of the certificates.
Yes, the SSL Integrity Monitor API provides JSON-based responses, making it easy to integrate into your workflows and applications.
Yes, the SSL Integrity Monitor API is equipped to detect vulnerabilities in SSL configurations, helping to ensure a secure connection for users.
The Verify SSL endpoint returns data about the SSL certificate's validity, expiration status, encryption settings, and issuer details. It includes fields like `isvalidCertificate`, `expiry`, `issuer`, and `certDetails`, providing comprehensive insights into the certificate's security.
Key fields include `isvalidCertificate`, `expiry`, `daysLeft`, `issuer`, and `certDetails`. The `certDetails` object contains specific information such as `name`, `serialNumber`, `validFrom`, and `validTo`, which are crucial for understanding the certificate's status.
The response data is structured in a JSON format, with a top-level object containing boolean flags, expiration details, and a nested `certDetails` object. This organization allows for easy access to both summary and detailed information about the SSL certificate.
The Verify SSL endpoint accepts a single parameter: the website URL. Users must provide a valid URL in the request to receive the corresponding SSL certificate information.
Users can utilize the returned data to assess SSL certificate validity, monitor expiration dates, and ensure compliance with security standards. For example, the `daysLeft` field can help schedule renewals before expiration.
Typical use cases include automating SSL certificate audits, monitoring certificate expiration, and ensuring compliance with security policies. Organizations can integrate the API into their security workflows to proactively manage SSL configurations.
Data accuracy is maintained through regular updates and checks against trusted certificate authorities. The API verifies SSL certificates in real-time, ensuring that the information provided reflects the current status of the certificates.
If users receive partial or empty results, they should verify the provided URL for correctness and ensure that the website has an SSL certificate installed. Additionally, they can check for network issues or try again later to confirm the certificate's status.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
832ms
Service Level:
100%
Response Time:
1,045ms
Service Level:
100%
Response Time:
1,726ms
Service Level:
100%
Response Time:
505ms
Service Level:
100%
Response Time:
841ms
Service Level:
100%
Response Time:
800ms
Service Level:
100%
Response Time:
921ms
Service Level:
100%
Response Time:
559ms
Service Level:
100%
Response Time:
532ms
Service Level:
100%
Response Time:
487ms