SSL Verify API

SSL Verify API verifies the validity of SSL certificates, ensuring that the connection to a website is secure and encrypted, protecting sensitive data during transmission.

About the API:  

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.

 

What this API receives and what your API provides (input/output)?

This API receives the URL of a website and returns details about the SSL certificate, including its validity, expiration date and encryption settings.

 

What are the most common uses cases of this API?

  1. 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.

     

Are there any limitations to your plans?

Basic Plan: 2 requests per second.

Pro Plan: 5 requests per second.

Pro Plus Plan: 5 requests per second.

API Documentation

Endpoints


To use this endpoint, you submit the website URL in the request. The API verifies the SSL certificate and returns details about its validity, expiration and encryption settings.



                                                                            
GET https://zylalabs.com/api/4984/ssl+verify+api/6288/ssl+verify
                                                                            
                                                                        

Ssl Verify - Endpoint Features

Object Description
domain [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"isvalidCertificate":true,"canBeSelfSigned":false,"isWildCard":true,"isExpired":false,"message":"Valid Certificate","expiry":"2025-07-27","daysLeft":328,"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":"keyid:24:6E:2B:2D:D0:6A:92:51:51:25:69:01:AA:9A:47:A6:89:E7:40:20\n","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\n","keyUsage":"Digital Signature, Key Encipherment","extendedKeyUsage":"TLS Web Server Authentication, TLS Web Client Authentication","crlDistributionPoints":"\nFull Name:\n  URI:http:\/\/crl3.digicert.com\/DigiCertGlobalCAG2.crl\n\nFull Name:\n  URI:http:\/\/crl4.digicert.com\/DigiCertGlobalCAG2.crl\n","authorityInfoAccess":"OCSP - URI:http:\/\/ocsp.digicert.com\nCA Issuers - URI:http:\/\/cacerts.digicert.com\/DigiCertGlobalCAG2.crt\n","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":328},"apiVersion":2,"error":false}
                                                                                                                                                                                                                    
                                                                                                    

Ssl Verify - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/4984/ssl+verify+api/6288/ssl+verify?domain=amazon.com' --header 'Authorization: Bearer YOUR_API_KEY' 

    

API Access Key & Authentication

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 REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

๐Ÿš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • โœ”๏ธŽ Only Pay for Successful Requests
  • โœ”๏ธŽ Free 7-Day Trial
  • โœ”๏ธŽ Multi-Language Support
  • โœ”๏ธŽ One API Key, All APIs.
  • โœ”๏ธŽ Intuitive Dashboard
  • โœ”๏ธŽ Comprehensive Error Handling
  • โœ”๏ธŽ Developer-Friendly Docs
  • โœ”๏ธŽ Postman Integration
  • โœ”๏ธŽ Secure HTTPS Connections
  • โœ”๏ธŽ Reliable Uptime

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.

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldโ€™s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, look at the โ€˜X-Zyla-API-Calls-Monthly-Remainingโ€™ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the โ€˜X-Zyla-RateLimit-Limitโ€™ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The โ€˜X-Zyla-RateLimit-Resetโ€™ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itโ€™s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.

 Service Level
100%
 Response Time
849ms

Category:


Related APIs