Jason Coleman

Payment gateways are now requiring commmunication via TLS 1.2. This plugin will test your webserver for compatibility to ensure there is no outage in your ecommerce application.
If your server is not able to communicate via TLS 1.2, you will be shown the appropriate steps to take to upgrade the server version of OpenSSL, PHP, or direct you to update the SSLVERSION of CURL.
The plugin currently offers testing via these API Endpoints: 
* PayPal (https://tlstest.paypal.com/) 
* How’s My SSL? (https://www.howsmyssl.com/a/check)
Testing against these API Endpoints should validate compatibility for other gateways and APIs, even if you are not using PayPal, for example, on your ecommerce application. However, we do plan to add more tests for API Endpoints provided by popular gateways.

TLS 1.2 Compatibility Test

Very simple plugin to ensure your server supports TLS1.2. For example, are you worried about your payment processor being able to work with Stripe? First, make sure this test passes.
5 Stars



This plugin is key to ensuring your eCommerce site can still conduct commerce.

Thanks for making this tool! This saved me a lot of time!

Very helpful!

Verify TLS 1.2 support on your webserver for included API endpoints and diagnose a solution to enable compatibility.

Simon Waters

TLS is growing in complexity. Server Name Indication (SNI) now means HTTPS sites may be on shared IP addresses, or otherwise restricted. For these servers it is handy to be able to set desired HTTP headers without access to the web servers configuration or using .htaccess file.
This plug-in exposes controls for:
<ul>
<li>HSTS (Strict-Transport-Security)</li>
<li>HPKP (Public-Key-Pins)</li>
<li>Disabling content sniffing (X-Content-Type-Options)</li>
<li>XSS protection (X-XSS-Protection)</li>
<li>Clickjacking mitigation (X-Frame-Options in main site)</li>
<li>Expect-CT</li>
</ul>
HSTS is used to ensure that future connections to a website always use TLS, and disallowing bypass of certificate warnings for the site.
HPKP is used if you don’t want to rely solely on the Certificate Authority trust model for certificate issuance.
Disabling content sniffing is mostly of interest for sites that allow users to upload files of specific types, but that browsers might be silly enough to interpret of some other type, thus allowing unexpected attacks.
XSS protection re-enables XSS protection for the site, if the user has disabled it previously, and sets the “block” option so that attacks are not silently ignored.
Clickjacking protection is usually only relevant when someone is logged in but users requested it, presumably they have rich content outside of WordPress authentication they wish to protect.
Expect-CT is used to ensure Certificate Transparency is configured correctly.

Security Headers

Plug-in to ease the setting of TLS headers for HSTS and similar

TLS 1.2 Compatibility Test vs Security Headers