Frequently Asked Questions
Why are we only supporting TLS 1.2 and above?
The PCI Security Council sets the rules on which technologies are acceptable for use in transmitting cardholder data. They have explicitly identified TLS 1.0 as no longer being a strong form of encryption because it is vulnerable to many known attacks.
Almost every website has stopped supporting TLS 1.0 and 1.1, this is done to help safeguard your information.
Are you affected?
If you don't use our API's then it's un-likely you will be affected unless you're using a really old browser and or operating system. To check to see if your computer/browser supports TLS 1.2 or higher please visit this link: https://www.ssllabs.com/ssltest/viewMyClient.html
API Library support
If you have code that connects with the ZeroBounce API, you must ensure that it will continue to work after June 1, 2018. Each language and library is different, below are the more popular languages.
These languages will need significant changes/upgrades in order to work:
- Java 6u45 / 7u45
- .NET before 4.5 (does not support TLS 1.2)
- .NET 4.5 (must have settings changed to explicitly enable TLS 1.2)
- OpenSSL 0.9.8
- Most dynamic languages such as Ruby, PHP, & Python rely on the underlying operating system’s OpenSSL version. You can check it by running OpenSSL version. 1.0.1 in the minimum required.
- PHP 5.5.19 and up has support for TLS 1.2
You can test your connection with various tools and documentation found on the internet. Please keep in mind that we are not experts in every language or framework and so we aren’t able to test or fix your code for you.
Language specific instructions
- .NET 4.6: TLS 1.2 is used automatically. No changes are necessary.
- .NET 4.5: The SecurityProtocolType needs to be changed to Tls12 (using the SecurityProtocol Setter)
- .NET 4.0: TLS 1.2 is supported, but there’s no named SecurityProtocolType enumeration. Use (SecurityProtocolType)3072.
- .NET 3 and below: Must be upgraded to 4.5
Most browsers have supported TLS 1.2 for several years.
The following browsers DO NOT support TLS 1.2 and will no longer work.
- Google Chrome 29
- Firefox 26
- Internet Explorer 10
- Safari 8
- iOS 4
- Android 4
Your API Dashboard is located in your account off the left hand menu. Every-time you make a call to the API, it will record the results, so you can quickly see big picture overview of your usage and your results. No emails are saved, just a count of the results.
In the API Dashboard, as seen above, you will have a drop-down the drill into the details of the invalids, do not mail, and unknown status codes. And be able to graph by daily or monthly trends to get a more in-depth look into your email validations.
In the above image, I clicked on the status I didn't want to show, leaving just the trend of the invalids. To get further details about the invalid, change the menu on top to "Invalids by Sub_Status"
Now you can see the sub_status break down of the "Invalids" emails. It's a very powerful tool, to allow you to see usage summary by day, months, and even years with a visual representation of the health of the emails you are passing through the API.
The API Keys page is where you can manage API access to your ZeroBounce account. On the API Keys page you can create new API keys or you can edit or delete existing keys with the exception of the Master Key.
Add New API Key:
To create a new API Key click on "+ Add Additional API Key" on the top left of the page
Type in the name you wish to give the key and make sure to set the "active state" of the key to either yes or no. Once complete, click on the green check mark to create the key or the red x to cancel.
After creating the key, your new key would be listed like in the example below.
To edit your API key status, click on the pencil icon on the right (see example below). The master key is not editable
On the edit mode, you will be able to change the name and active state of your API key. Once you are finished click on the green check mark to update or the red "x" to cancel your changes.
Generate New Key
You can regenerate a new key to replace the current one.
Click OK to process the changes or Cancel to exit
Except for the Master key, you can delete the additional keys if they are no longer be used.
Click OK to delete the selected key or Cancel to exit.
If you have reached the maximum number of allowed API Keys specified in your account, you will not be able to add any additional key
Do you need a hands on specialist integrating our API into your applications, web pages, sign up forms, or registration screens?
Here is a list of approved integration vendors.