If failure is consistent (except for a connection error which is probably a VPN or firewall issue), that indicates no support for TLS 1.2, for the CURL version on that particular machine.

Test CURL with force TLS 1.2: curl -k -tlsv1.2 -tls-max 1.2 ' 'ģ. Other than that, any error code likely indicates a failure.Ģ. Success message from CURL if TLS 1.2 supported: Connected successfully with TLS 1.2.Test default CURL TLS choice: curl -k ' ' Here are the steps to test your TLS 1.2 compliance using CURL command on a Linux machine:ġ. openssl sclient example commands with detail output. If it is unsuccessful an error message will be returned such as OpenSSL SSL_connect: SSL_ERROR_SYSCALL Use OpenSSL command line to test and check TLS/SSL server connectivity, cipher suites, TLS/SSL version, check server certificate etc.If it is successful the endpoint will return Connected successfully with TLS 1.2.It accepts all methods (GET, POST, PATCH, etc) and doesn’t require any credentials.Here is the endpoint which you can use to verify that your systems are TLS 1.2 compliant: This may have an impact on your use of the MessageMedia REST and/or SOAP API if the systems you have in place do not support TLS 1.2 or higher. On Augwe are ending support for TLS 1.0 and 1.1.

Curl test tls 1.2