Test before and after installation of the certificate

Before you install it, use your web browsers and other clients to access this URL and check how they react. They should be very upset, since the server tries to identify with an certificate from an unknown authority. This is very much like someone that tries to identify itself with an impressive paper with cool stamps and a photograph that is clearly 20 years old and text in a language you do not understand. You may see it’s an identity card or a driver’s license for donkeys – but you will never ever trust it.

In order to continue with the tests, you need to install the CA certificate and go back to the same URL and make sure that your application does not complain at all, that your system now trusts our certificates as much as any other certificate.

Fork us on Github

All the tests, including keys and certificates, are available on Github.
https://github.com/edvinanet/tls-o-matic
That's also where you will find all the current tests while waiting for us to write documentation here.

What is TLS?

"The TLS protocol provides communications security
over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery."
From RFC 5446 that defines the current TLS - version 1.2. Wikipedia is also a good help in explaining TLS.