Handy hints for updating your TLS to v1.2

On November 30th, 2016, we’ll be deprecating some of the older security protocols (TLS 1.0,
TLS 1.1) used to make connections with FireText’s API & App.

We’ve put together a couple of test URLs for you to check which version you are connecting on. Please note, the testing end-points should not be used in production as they will be retired following the change.

Simple TLS Header Check


This is a simple TLSv1.2 check. If all is well you will get a HTTP 200 response with a body: “OK TLSv1.2.”
If accessed using another protocol will get an SSL connection error in your code / no response.

Live Send Check


(e.g. https://tls.firetext.co.uk/api/credit)

This allows for a live test of the API using TLSv1.2. It simply points to a TLSv1.2 only version of our API.

Upgrading to TLS 1.2 will generally not involve any changes to your code, but may require that you update your operating systems, system packages, or language runtime libraries. (The exact methodology depends on your technology stack.)

We’d like to stress that TLS 1.0, TLS 1.1, and SHA-1 are widely considered to be weak and upgrading as early as possible is an important part of keeping your business secure. If you’d like more information about the topic, we’ve written up a blog post here.

If you have any questions about this change, or need help in upgrading your systems, please don’t hesitate to get in touch

FireText provide SMS Marketing for your business.
Add SMS to your marketing mix today – find out more.