Choose a standard

These results have been calculated using the following standard:

Export

B
is the overall score for
gsc-game.com

Crypto on this site is safe for legacy use, but is not up to date with the Cryptosense 2019 standard.

Note: The overall score is calculated based on the lowest score achieved by any of the machines scanned.

Machines Scanned

B
gsc-game.com 5.9.10.49 2019-09-22 19:56:13 UTC
You must be logged in to monitor hosts.
B
mail.gsc-game.com 5.9.10.59 2019-09-22 19:56:14 UTC
You must be logged in to monitor hosts.
down arrow

Crypto Services Discovered

Below we list all of the machines detected. For each machine, we list the cryptographic services found. For each service, we give the reasons behind the grading. To see the full details of the cryptography offered by a service, click on "show details".

gsc-game.com

IP address 5.9.10.49
Last scan 2019-09-22 19:56:13 UTC
TLS HTTP (port 443)
Rules applicable 21
A!
A
A!
B
C
D
18 3 0 0 0
TLS SMTP (port 465)
Rules applicable 19
B
A
A!
B
C
D
14 3 2 0 0

TLS (port 443 – HTTP)

Show scan details
Versions TLS 1.0, TLS 1.1, TLS 1.2
Fallback SCSV Supported
Ciphers
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_RSA_WITH_AES_256_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
Cipher order Server
Compression
  • NULL TLS 1.0, TLS 1.1, TLS 1.2
Certificate key RSA 2048-bit test this key
Hash algorithm SHA-256
Diffie-Hellman
  • Group (custom, 2048-bit): 0xb89e8933638a5695b63417c3213de16b1ea537e030681fb80b518c9c61246fbe00653516e7a71e576db43fa2a699491ddc78696b47fc9bb6432ff90357c0810b304fb1c55dc35b275d99e7e0423ac2452cfa2d5be07fe152243f9f60deea81f4ae72dfd8f10de66621868ee419774848230ba348084a32086ac9492868d775601a681ca66cf10eb1bad5d2527fb39fe2c461335a514e1298368d7e61e5ef13854b3e1613cfd2e9ecbbaeafa6603f2e5e48bc287a024f450261e21e7d58b1c32245f3287da3a2fb7dbdfe8a80dfed62b6f09b38be356f125ed1d3c8abc3ce90aa94d8e4c346e3080874358ff1f6ee1910b8042d2d2fe8450d4e5647dec5086ebb
  • Generator: 0x2
Certificate start date 2018-05-11 00:00:00 UTC
Certificate expiration date 2020-05-10 23:59:59 UTC
Certificate serial number 73047020241304048819727383402685332639
Certificate issuer C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
Certificate subject OU=Domain Control Validated,OU=PositiveSSL,CN=gsc-game.com
Certificate SANs
  • gsc-game.com
  • www.gsc-game.com
A!
Borderline Compliance Warnings
Support for TLS 1.0
Trigger TLS 1.0 among the protocols offered by TLS server.
Context

TLS 1.0 is discouraged by PCI-DSS and has been considered non-compliant since June 2018 (PCI-DSS v3.2).

Diffie-Hellman group security
Trigger The server uses a 2048-bit Diffie-Hellman group.
Context

Diffie-Hellman is mainly used so that two machines can compute a shared secret and so benefit from forward secrecy.

For security, a 2048-bit group is reasonable although ECRYPT recommends a group size of at least 3072 bits (ECRYPT 2016 report). The use of commonly-shared 1024-bit groups such as Oakley group 2 is especially discouraged because of possible precomputation attacks (weakdh.org).

Certificate RSA key length
Trigger The server uses a 2048-bit RSA key.
Context

RSA keys must be long enough to provide reasonable security against brute-force attack by factoring. While 2048-bit keys are fine today, a minimum of 3072-bit is recommended by ECRYPT for new systems.

A
Passed
Support for SSL 2.0
Trigger SSL 2.0 not among the protocols offered by TLS server.
Context

SSL 2.0 has been officially deprecated as of March 2011 (RFC 6176).

Support for SSL 3.0
Trigger SSL 3.0 not among the protocols offered by TLS server.
Context

SSL 3.0 has been officially deprecated as of June 2015 (RFC 7568).

Vulnerability to the POODLE attack
Trigger The server is not vulnerable to POODLE.
Context

Servers that support SSL 3.0 with cipher suites containing the CBC mode of operation can be vulnerable to the POODLE attack (RFC 7568). A possible countermeasure consists in enabling TLS Fallback SCSV along with more recent TLS protocols such as TLS 1.2.

Security of hash function for certificate signature digest
Trigger The hash used for the certificate is SHA-256.
Context

The hash function used on certificate signatures must be cryptographically secure in order for the certificate not to be forgeable. Hash functions MD2 and MD5 are considered to be broken. SHA-1 certificates are in the process of being deprecated because of their weaknesses although many browsers and websites still support them. The SHA-2 family of functions (SHA-224, SHA-256, ...) are a safe alternative.

Support for Null cipher
Trigger The server doesn't support any cipher suites containing the NULL cipher.
Context

Application data is not encrypted when the NULL cipher is used, exposing it to eavesdroppers.

Support for Export-grade cipher suites
Trigger The server doesn't support any EXPORT cipher suites.
Context

For legacy reasons, some TLS cipher suites are composed of export-grade cryptography, which is insecure by today's standards. Furthermore, servers that accept EXPORT cipher suites may be vulnerable to the FREAK (freakattack.com) or the Logjam (weakdh.org) downgrade attacks.

Support for DES cipher
Trigger The server doesn't support any cipher suites containing the DES cipher.
Context

DES is a cipher with an effective key length of 56 bits, which is now considered too weak by many agencies, including ECRYPT and NIST (ECRYPT 2016 report, NIST SP 800-57, Part 1, Rev. 3).

Support for Triple DES cipher
Trigger The server doesn't support any cipher suites containing the 3DES cipher.
Context

Three-key-3DES is a cipher with 168-bit keys but an effective key length of 112 bits because of a meet-in-the-middle attack. This is considered enough only for legacy. Furthermore, it has a 64-bit block size, which can be insufficient for some applications, for example because of birthday attacks (sweet32.info).

Support for RC4 cipher
Trigger The server doesn't support any cipher suites containing the RC4 cipher.
Context

RC4 is a stream cipher in which significant weaknesses have been found. The use of this cipher in any protocol has been discouraged by ECRYPT as of 2014 (ECRYPT 2016 report).

In TLS, cipher suites using RC4 have been deprecated as of February 2015 (RFC 7465).

Support for cipher suites giving forward secrecy
Trigger The server supports some cipher suites that provide forward secrecy.
Context

Forward secrecy is achieved when the security of session keys is not affected by a compromise of long-term keys.

In TLS, forward secrecy is enabled by DHE, ECDHE and DH_anon cipher suites. They protect past communications from a compromise of a long-term key (such as an RSA key).

Support for TLS Fallback SCSV
Trigger The server supports TLS Fallback SCSV.
Context

TLS Fallback SCSV (RFC 7507) enables a server to determine whether a protocol version downgrade by the client is legitimate. If this mechanism is not supported, an attacker could make both endpoints choose a lower protocol version they both support, probably resulting in a less secure connection.

DROWN vulnerability
Trigger The server is not vulnerable to DROWN.
Context

A server is vulnerable to the "General DROWN" attack when it supports, willingly or not, weak SSLv2 cipher suites. A server is vulnerable to the even more powerful "Special DROWN" attack when it is affected by CVE-2016-0703. DROWN may affect any TLS server (even with TLS 1.2 and on a different machine) which uses the same RSA key as the vulnerable SSLv2 server (drownattack.com).

ROBOT vulnerability
Trigger The server is not vulnerable to ROBOT.
Context

ROBOT (https://robotattack.org/) is the return of a 19-year-old vulnerability that allows performing RSA decryption and signing operations with the private key of a TLS server. It affects vulnerable server implementations that also allow the use of RSA encryption (e.g. TLS_RSA cipher suites).

Certificate expiration
Trigger The expiration date of this certificate is 2020-05-10 23:59:59 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. In particular, no revocation information will be kept about an expired certificate.

Certificate not valid yet
Trigger The start date of this certificate is 2018-05-11 00:00:00 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. A validity start date in the future is a sign that the certificate is bogus or that the system that generated it has a desynchronized clock.

Support for TLS compression (CRIME)
Trigger This service supports the following compression algorithms: NULL.
Context

The CRIME vulnerability (also known as CVE-2012-4929) happens when TLS compression is enabled. An attacker can get information about sensitive data in pages by observing the size of compressed responses. Using this, it is possible to impersonate users by retrieving their session cookies. This exploit has been demonstrated on HTTPS, but the weakness is fundamental to compression in TLS and may be exploitable in non-HTTP services.

Support for anonymous cipher suites
Trigger This service does not support any anonymous cipher suite.
Context

Each cipher suite describes how server authentication is done. Anonymous cipher suites tell the client not to authenticate the server. They should thus not be used unless server authentication is not required, as is usually the case for SMTP servers.

Heartbleed vulnerability
Trigger The server is not vulnerable to Heartbleed.
Context

The OpenSSL Heartbleed bug (heartbleed.com, CVE-2014-0160) allows secrets including the server's private key to be extracted in the clear.

TLS (port 465 – SMTP)

Show scan details
Versions TLS 1.0, TLS 1.1, TLS 1.2
Fallback SCSV Not supported
Ciphers
  • TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.1
  • TLS_RSA_WITH_AES_128_CBC_SHA TLS 1.1
  • TLS_RSA_WITH_AES_256_CBC_SHA TLS 1.1
  • TLS_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.1
  • TLS_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.1
Cipher order Client
Compression
  • NULL TLS 1.0
Certificate key RSA 2048-bit test this key
Hash algorithm SHA-256
Diffie-Hellman
  • Group (2048-bit MODP from RFC 5114): 0xad107e1e9123a9d0d660faa79559c51fa20d64e5683b9fd1b54b1597b61d0a75e6fa141df95a56dbaf9a3c407ba1df15eb3d688a309c180e1de6b85a1274a0a66d3f8152ad6ac2129037c9edefda4df8d91e8fef55b7394b7ad5b7d0b6c12207c9f98d11ed34dbf6c6ba0b2c8bbc27be6a00e0a0b9c49708b3bf8a317091883681286130bc8985db1602e714415d9330278273c7de31efdc7310f7121fd5a07415987d9adc0a486dcdf93acc44328387315d75e198c641a480cd86a1b9e587e8be60e69cc928b2b9c52172e413042e9b23f10b0e16e79763c9b53dcf4ba80a29e3fb73c16b8e75b97ef363e2ffa31f71cf9de5384e71b81c0ac4dffe0c10e64f
  • Generator: 0xac4032ef4f2d9ae39df30b5c8ffdac506cdebe7b89998caf74866a08cfe4ffe3a6824a4e10b9a6f0dd921f01a70c4afaab739d7700c29f52c57db17c620a8652be5e9001a8d66ad7c17669101999024af4d027275ac1348bb8a762d0521bc98ae247150422ea1ed409939d54da7460cdb5f6c6b250717cbef180eb34118e98d119529a45d6f834566e3025e316a330efbb77a86f0c1ab15b051ae3d428c8f8acb70a8137150b8eeb10e183edd19963ddd9e263e4770589ef6aa21e7f5f2ff381b539cce3409d13cd566afbb48d6c019181e1bcfe94b30269edfe72fe9b6aa4bd7b5a0f1c71cfff4c19c418e1f6ec017981bc087f2a7065b384b890d3191f2bfa
Certificate start date 2014-12-20 00:00:00 UTC
Certificate expiration date 2019-12-19 23:59:59 UTC
Certificate serial number 169189091054436175579115634615590372918
Certificate issuer C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
Certificate subject OU=Domain Control Validated,OU=PositiveSSL,CN=mail.gsc-game.com
Certificate SANs
  • mail.gsc-game.com
  • www.mail.gsc-game.com
B
Warnings
Support for Triple DES cipher
Trigger The server supports a cipher suite containing the 3DES cipher.
Context

Three-key-3DES is a cipher with 168-bit keys but an effective key length of 112 bits because of a meet-in-the-middle attack. This is considered enough only for legacy. Furthermore, it has a 64-bit block size, which can be insufficient for some applications, for example because of birthday attacks (sweet32.info).

Fix Log in to get remediation advice
Support for TLS Fallback SCSV
Trigger The server does not support TLS Fallback SCSV.
Context

TLS Fallback SCSV (RFC 7507) enables a server to determine whether a protocol version downgrade by the client is legitimate. If this mechanism is not supported, an attacker could make both endpoints choose a lower protocol version they both support, probably resulting in a less secure connection.

Fix Log in to get remediation advice
A!
Borderline Compliance Warnings
Support for TLS 1.0
Trigger TLS 1.0 among the protocols offered by TLS server.
Context

TLS 1.0 is discouraged by PCI-DSS and has been considered non-compliant since June 2018 (PCI-DSS v3.2).

Diffie-Hellman group security
Trigger The server uses a commonly-shared 2048-bit Diffie-Hellman group.
Context

Diffie-Hellman is mainly used so that two machines can compute a shared secret and so benefit from forward secrecy.

For security, a 2048-bit group is reasonable although ECRYPT recommends a group size of at least 3072 bits (ECRYPT 2016 report). The use of commonly-shared 1024-bit groups such as Oakley group 2 is especially discouraged because of possible precomputation attacks (weakdh.org).

Certificate RSA key length
Trigger The server uses a 2048-bit RSA key.
Context

RSA keys must be long enough to provide reasonable security against brute-force attack by factoring. While 2048-bit keys are fine today, a minimum of 3072-bit is recommended by ECRYPT for new systems.

A
Passed
Support for SSL 2.0
Trigger SSL 2.0 not among the protocols offered by TLS server.
Context

SSL 2.0 has been officially deprecated as of March 2011 (RFC 6176).

Support for SSL 3.0
Trigger SSL 3.0 not among the protocols offered by TLS server.
Context

SSL 3.0 has been officially deprecated as of June 2015 (RFC 7568).

Security of hash function for certificate signature digest
Trigger The hash used for the certificate is SHA-256.
Context

The hash function used on certificate signatures must be cryptographically secure in order for the certificate not to be forgeable. Hash functions MD2 and MD5 are considered to be broken. SHA-1 certificates are in the process of being deprecated because of their weaknesses although many browsers and websites still support them. The SHA-2 family of functions (SHA-224, SHA-256, ...) are a safe alternative.

Support for Null cipher
Trigger The server doesn't support any cipher suites containing the NULL cipher.
Context

Application data is not encrypted when the NULL cipher is used, exposing it to eavesdroppers.

Support for Export-grade cipher suites
Trigger The server doesn't support any EXPORT cipher suites.
Context

For legacy reasons, some TLS cipher suites are composed of export-grade cryptography, which is insecure by today's standards. Furthermore, servers that accept EXPORT cipher suites may be vulnerable to the FREAK (freakattack.com) or the Logjam (weakdh.org) downgrade attacks.

Support for DES cipher
Trigger The server doesn't support any cipher suites containing the DES cipher.
Context

DES is a cipher with an effective key length of 56 bits, which is now considered too weak by many agencies, including ECRYPT and NIST (ECRYPT 2016 report, NIST SP 800-57, Part 1, Rev. 3).

Support for RC4 cipher
Trigger The server doesn't support any cipher suites containing the RC4 cipher.
Context

RC4 is a stream cipher in which significant weaknesses have been found. The use of this cipher in any protocol has been discouraged by ECRYPT as of 2014 (ECRYPT 2016 report).

In TLS, cipher suites using RC4 have been deprecated as of February 2015 (RFC 7465).

Support for cipher suites giving forward secrecy
Trigger The server supports some cipher suites that provide forward secrecy.
Context

Forward secrecy is achieved when the security of session keys is not affected by a compromise of long-term keys.

In TLS, forward secrecy is enabled by DHE, ECDHE and DH_anon cipher suites. They protect past communications from a compromise of a long-term key (such as an RSA key).

DROWN vulnerability
Trigger The server is not vulnerable to DROWN.
Context

A server is vulnerable to the "General DROWN" attack when it supports, willingly or not, weak SSLv2 cipher suites. A server is vulnerable to the even more powerful "Special DROWN" attack when it is affected by CVE-2016-0703. DROWN may affect any TLS server (even with TLS 1.2 and on a different machine) which uses the same RSA key as the vulnerable SSLv2 server (drownattack.com).

ROBOT vulnerability
Trigger The server is not vulnerable to ROBOT.
Context

ROBOT (https://robotattack.org/) is the return of a 19-year-old vulnerability that allows performing RSA decryption and signing operations with the private key of a TLS server. It affects vulnerable server implementations that also allow the use of RSA encryption (e.g. TLS_RSA cipher suites).

Certificate expiration
Trigger The expiration date of this certificate is 2019-12-19 23:59:59 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. In particular, no revocation information will be kept about an expired certificate.

Certificate not valid yet
Trigger The start date of this certificate is 2014-12-20 00:00:00 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. A validity start date in the future is a sign that the certificate is bogus or that the system that generated it has a desynchronized clock.

Support for TLS compression (CRIME)
Trigger This service supports the following compression algorithms: NULL.
Context

The CRIME vulnerability (also known as CVE-2012-4929) happens when TLS compression is enabled. An attacker can get information about sensitive data in pages by observing the size of compressed responses. Using this, it is possible to impersonate users by retrieving their session cookies. This exploit has been demonstrated on HTTPS, but the weakness is fundamental to compression in TLS and may be exploitable in non-HTTP services.

Heartbleed vulnerability
Trigger The server is not vulnerable to Heartbleed.
Context

The OpenSSL Heartbleed bug (heartbleed.com, CVE-2014-0160) allows secrets including the server's private key to be extracted in the clear.

mail.gsc-game.com

IP address 5.9.10.59
Last scan 2019-09-22 19:56:14 UTC
TLS HTTP (port 443)
Rules applicable 21
B
A
A!
B
C
D
17 3 1 0 0
TLS SMTP (port 465)
Rules applicable 19
B
A
A!
B
C
D
14 3 2 0 0
TLS SMTP (port 587)
Rules applicable 18
B
A
A!
B
C
D
15 2 1 0 0

TLS (port 443 – HTTP)

Show scan details
Versions TLS 1.0, TLS 1.1, TLS 1.2
Fallback SCSV Supported
Ciphers
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_256_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_AES_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
Cipher order Server
Compression
  • NULL TLS 1.0, TLS 1.1, TLS 1.2
Certificate key RSA 2048-bit test this key
Hash algorithm SHA-256
Diffie-Hellman
  • Group (custom, 2048-bit): 0xc17ad63f840d21be68f21a0a9deb73284ecf49d02ba27f6cc5abdab8bf3115d0f2e013de7641e806ea378f5e6e16af1c564ecf3172c12057a19c516214e179df67edd19950224e7efa98319e94fe48097d0ba6685ac4dbc9d5937303b8a231d2e1be667ae714bc3748afa1eec9d7b3fe6b666f7a71ce8dbcc546ecbb3c7865141eb0dc9cd1ca1c1b362cde8d6021507b085787e1c1d77e242d7c767a3f1121190a64546ecbe015763ce65276d49626000fb19dfe90a6df6c4af30933772cac174c13e787d9759c11e5864a43472063b784a5cfce37a4ec1bc427da09d1e95855f454e296a3f6081193ec4e899be788fa83b25340f514f3e24f4a1588c8196feb
  • Generator: 0x2
Certificate start date 2014-12-20 00:00:00 UTC
Certificate expiration date 2019-12-19 23:59:59 UTC
Certificate serial number 169189091054436175579115634615590372918
Certificate issuer C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
Certificate subject OU=Domain Control Validated,OU=PositiveSSL,CN=mail.gsc-game.com
Certificate SANs
  • mail.gsc-game.com
  • www.mail.gsc-game.com
B
Warnings
Support for Triple DES cipher
Trigger The server supports a cipher suite containing the 3DES cipher.
Context

Three-key-3DES is a cipher with 168-bit keys but an effective key length of 112 bits because of a meet-in-the-middle attack. This is considered enough only for legacy. Furthermore, it has a 64-bit block size, which can be insufficient for some applications, for example because of birthday attacks (sweet32.info).

Fix Log in to get remediation advice
A!
Borderline Compliance Warnings
Support for TLS 1.0
Trigger TLS 1.0 among the protocols offered by TLS server.
Context

TLS 1.0 is discouraged by PCI-DSS and has been considered non-compliant since June 2018 (PCI-DSS v3.2).

Diffie-Hellman group security
Trigger The server uses a 2048-bit Diffie-Hellman group.
Context

Diffie-Hellman is mainly used so that two machines can compute a shared secret and so benefit from forward secrecy.

For security, a 2048-bit group is reasonable although ECRYPT recommends a group size of at least 3072 bits (ECRYPT 2016 report). The use of commonly-shared 1024-bit groups such as Oakley group 2 is especially discouraged because of possible precomputation attacks (weakdh.org).

Certificate RSA key length
Trigger The server uses a 2048-bit RSA key.
Context

RSA keys must be long enough to provide reasonable security against brute-force attack by factoring. While 2048-bit keys are fine today, a minimum of 3072-bit is recommended by ECRYPT for new systems.

A
Passed
Support for SSL 2.0
Trigger SSL 2.0 not among the protocols offered by TLS server.
Context

SSL 2.0 has been officially deprecated as of March 2011 (RFC 6176).

Support for SSL 3.0
Trigger SSL 3.0 not among the protocols offered by TLS server.
Context

SSL 3.0 has been officially deprecated as of June 2015 (RFC 7568).

Vulnerability to the POODLE attack
Trigger The server is not vulnerable to POODLE.
Context

Servers that support SSL 3.0 with cipher suites containing the CBC mode of operation can be vulnerable to the POODLE attack (RFC 7568). A possible countermeasure consists in enabling TLS Fallback SCSV along with more recent TLS protocols such as TLS 1.2.

Security of hash function for certificate signature digest
Trigger The hash used for the certificate is SHA-256.
Context

The hash function used on certificate signatures must be cryptographically secure in order for the certificate not to be forgeable. Hash functions MD2 and MD5 are considered to be broken. SHA-1 certificates are in the process of being deprecated because of their weaknesses although many browsers and websites still support them. The SHA-2 family of functions (SHA-224, SHA-256, ...) are a safe alternative.

Support for Null cipher
Trigger The server doesn't support any cipher suites containing the NULL cipher.
Context

Application data is not encrypted when the NULL cipher is used, exposing it to eavesdroppers.

Support for Export-grade cipher suites
Trigger The server doesn't support any EXPORT cipher suites.
Context

For legacy reasons, some TLS cipher suites are composed of export-grade cryptography, which is insecure by today's standards. Furthermore, servers that accept EXPORT cipher suites may be vulnerable to the FREAK (freakattack.com) or the Logjam (weakdh.org) downgrade attacks.

Support for DES cipher
Trigger The server doesn't support any cipher suites containing the DES cipher.
Context

DES is a cipher with an effective key length of 56 bits, which is now considered too weak by many agencies, including ECRYPT and NIST (ECRYPT 2016 report, NIST SP 800-57, Part 1, Rev. 3).

Support for RC4 cipher
Trigger The server doesn't support any cipher suites containing the RC4 cipher.
Context

RC4 is a stream cipher in which significant weaknesses have been found. The use of this cipher in any protocol has been discouraged by ECRYPT as of 2014 (ECRYPT 2016 report).

In TLS, cipher suites using RC4 have been deprecated as of February 2015 (RFC 7465).

Support for cipher suites giving forward secrecy
Trigger The server supports some cipher suites that provide forward secrecy.
Context

Forward secrecy is achieved when the security of session keys is not affected by a compromise of long-term keys.

In TLS, forward secrecy is enabled by DHE, ECDHE and DH_anon cipher suites. They protect past communications from a compromise of a long-term key (such as an RSA key).

Support for TLS Fallback SCSV
Trigger The server supports TLS Fallback SCSV.
Context

TLS Fallback SCSV (RFC 7507) enables a server to determine whether a protocol version downgrade by the client is legitimate. If this mechanism is not supported, an attacker could make both endpoints choose a lower protocol version they both support, probably resulting in a less secure connection.

DROWN vulnerability
Trigger The server is not vulnerable to DROWN.
Context

A server is vulnerable to the "General DROWN" attack when it supports, willingly or not, weak SSLv2 cipher suites. A server is vulnerable to the even more powerful "Special DROWN" attack when it is affected by CVE-2016-0703. DROWN may affect any TLS server (even with TLS 1.2 and on a different machine) which uses the same RSA key as the vulnerable SSLv2 server (drownattack.com).

ROBOT vulnerability
Trigger The server is not vulnerable to ROBOT.
Context

ROBOT (https://robotattack.org/) is the return of a 19-year-old vulnerability that allows performing RSA decryption and signing operations with the private key of a TLS server. It affects vulnerable server implementations that also allow the use of RSA encryption (e.g. TLS_RSA cipher suites).

Certificate expiration
Trigger The expiration date of this certificate is 2019-12-19 23:59:59 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. In particular, no revocation information will be kept about an expired certificate.

Certificate not valid yet
Trigger The start date of this certificate is 2014-12-20 00:00:00 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. A validity start date in the future is a sign that the certificate is bogus or that the system that generated it has a desynchronized clock.

Support for TLS compression (CRIME)
Trigger This service supports the following compression algorithms: NULL.
Context

The CRIME vulnerability (also known as CVE-2012-4929) happens when TLS compression is enabled. An attacker can get information about sensitive data in pages by observing the size of compressed responses. Using this, it is possible to impersonate users by retrieving their session cookies. This exploit has been demonstrated on HTTPS, but the weakness is fundamental to compression in TLS and may be exploitable in non-HTTP services.

Support for anonymous cipher suites
Trigger This service does not support any anonymous cipher suite.
Context

Each cipher suite describes how server authentication is done. Anonymous cipher suites tell the client not to authenticate the server. They should thus not be used unless server authentication is not required, as is usually the case for SMTP servers.

Heartbleed vulnerability
Trigger The server is not vulnerable to Heartbleed.
Context

The OpenSSL Heartbleed bug (heartbleed.com, CVE-2014-0160) allows secrets including the server's private key to be extracted in the clear.

TLS (port 465 – SMTP)

Show scan details
Versions TLS 1.0, TLS 1.1, TLS 1.2
Fallback SCSV Not supported
Ciphers
  • TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS 1.0, TLS 1.1, TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS 1.0, TLS 1.1
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.1
Cipher order Client
Compression
  • NULL TLS 1.1, TLS 1.2
Certificate key RSA 2048-bit test this key
Hash algorithm SHA-256
Diffie-Hellman
  • Group (2048-bit MODP from RFC 5114): 0xad107e1e9123a9d0d660faa79559c51fa20d64e5683b9fd1b54b1597b61d0a75e6fa141df95a56dbaf9a3c407ba1df15eb3d688a309c180e1de6b85a1274a0a66d3f8152ad6ac2129037c9edefda4df8d91e8fef55b7394b7ad5b7d0b6c12207c9f98d11ed34dbf6c6ba0b2c8bbc27be6a00e0a0b9c49708b3bf8a317091883681286130bc8985db1602e714415d9330278273c7de31efdc7310f7121fd5a07415987d9adc0a486dcdf93acc44328387315d75e198c641a480cd86a1b9e587e8be60e69cc928b2b9c52172e413042e9b23f10b0e16e79763c9b53dcf4ba80a29e3fb73c16b8e75b97ef363e2ffa31f71cf9de5384e71b81c0ac4dffe0c10e64f
  • Generator: 0xac4032ef4f2d9ae39df30b5c8ffdac506cdebe7b89998caf74866a08cfe4ffe3a6824a4e10b9a6f0dd921f01a70c4afaab739d7700c29f52c57db17c620a8652be5e9001a8d66ad7c17669101999024af4d027275ac1348bb8a762d0521bc98ae247150422ea1ed409939d54da7460cdb5f6c6b250717cbef180eb34118e98d119529a45d6f834566e3025e316a330efbb77a86f0c1ab15b051ae3d428c8f8acb70a8137150b8eeb10e183edd19963ddd9e263e4770589ef6aa21e7f5f2ff381b539cce3409d13cd566afbb48d6c019181e1bcfe94b30269edfe72fe9b6aa4bd7b5a0f1c71cfff4c19c418e1f6ec017981bc087f2a7065b384b890d3191f2bfa
Certificate start date 2014-12-20 00:00:00 UTC
Certificate expiration date 2019-12-19 23:59:59 UTC
Certificate serial number 169189091054436175579115634615590372918
Certificate issuer C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
Certificate subject OU=Domain Control Validated,OU=PositiveSSL,CN=mail.gsc-game.com
Certificate SANs
  • mail.gsc-game.com
  • www.mail.gsc-game.com
B
Warnings
Support for Triple DES cipher
Trigger The server supports a cipher suite containing the 3DES cipher.
Context

Three-key-3DES is a cipher with 168-bit keys but an effective key length of 112 bits because of a meet-in-the-middle attack. This is considered enough only for legacy. Furthermore, it has a 64-bit block size, which can be insufficient for some applications, for example because of birthday attacks (sweet32.info).

Fix Log in to get remediation advice
Support for TLS Fallback SCSV
Trigger The server does not support TLS Fallback SCSV.
Context

TLS Fallback SCSV (RFC 7507) enables a server to determine whether a protocol version downgrade by the client is legitimate. If this mechanism is not supported, an attacker could make both endpoints choose a lower protocol version they both support, probably resulting in a less secure connection.

Fix Log in to get remediation advice
A!
Borderline Compliance Warnings
Support for TLS 1.0
Trigger TLS 1.0 among the protocols offered by TLS server.
Context

TLS 1.0 is discouraged by PCI-DSS and has been considered non-compliant since June 2018 (PCI-DSS v3.2).

Diffie-Hellman group security
Trigger The server uses a commonly-shared 2048-bit Diffie-Hellman group.
Context

Diffie-Hellman is mainly used so that two machines can compute a shared secret and so benefit from forward secrecy.

For security, a 2048-bit group is reasonable although ECRYPT recommends a group size of at least 3072 bits (ECRYPT 2016 report). The use of commonly-shared 1024-bit groups such as Oakley group 2 is especially discouraged because of possible precomputation attacks (weakdh.org).

Certificate RSA key length
Trigger The server uses a 2048-bit RSA key.
Context

RSA keys must be long enough to provide reasonable security against brute-force attack by factoring. While 2048-bit keys are fine today, a minimum of 3072-bit is recommended by ECRYPT for new systems.

A
Passed
Support for SSL 2.0
Trigger SSL 2.0 not among the protocols offered by TLS server.
Context

SSL 2.0 has been officially deprecated as of March 2011 (RFC 6176).

Support for SSL 3.0
Trigger SSL 3.0 not among the protocols offered by TLS server.
Context

SSL 3.0 has been officially deprecated as of June 2015 (RFC 7568).

Security of hash function for certificate signature digest
Trigger The hash used for the certificate is SHA-256.
Context

The hash function used on certificate signatures must be cryptographically secure in order for the certificate not to be forgeable. Hash functions MD2 and MD5 are considered to be broken. SHA-1 certificates are in the process of being deprecated because of their weaknesses although many browsers and websites still support them. The SHA-2 family of functions (SHA-224, SHA-256, ...) are a safe alternative.

Support for Null cipher
Trigger The server doesn't support any cipher suites containing the NULL cipher.
Context

Application data is not encrypted when the NULL cipher is used, exposing it to eavesdroppers.

Support for Export-grade cipher suites
Trigger The server doesn't support any EXPORT cipher suites.
Context

For legacy reasons, some TLS cipher suites are composed of export-grade cryptography, which is insecure by today's standards. Furthermore, servers that accept EXPORT cipher suites may be vulnerable to the FREAK (freakattack.com) or the Logjam (weakdh.org) downgrade attacks.

Support for DES cipher
Trigger The server doesn't support any cipher suites containing the DES cipher.
Context

DES is a cipher with an effective key length of 56 bits, which is now considered too weak by many agencies, including ECRYPT and NIST (ECRYPT 2016 report, NIST SP 800-57, Part 1, Rev. 3).

Support for RC4 cipher
Trigger The server doesn't support any cipher suites containing the RC4 cipher.
Context

RC4 is a stream cipher in which significant weaknesses have been found. The use of this cipher in any protocol has been discouraged by ECRYPT as of 2014 (ECRYPT 2016 report).

In TLS, cipher suites using RC4 have been deprecated as of February 2015 (RFC 7465).

Support for cipher suites giving forward secrecy
Trigger The server supports some cipher suites that provide forward secrecy.
Context

Forward secrecy is achieved when the security of session keys is not affected by a compromise of long-term keys.

In TLS, forward secrecy is enabled by DHE, ECDHE and DH_anon cipher suites. They protect past communications from a compromise of a long-term key (such as an RSA key).

DROWN vulnerability
Trigger The server is not vulnerable to DROWN.
Context

A server is vulnerable to the "General DROWN" attack when it supports, willingly or not, weak SSLv2 cipher suites. A server is vulnerable to the even more powerful "Special DROWN" attack when it is affected by CVE-2016-0703. DROWN may affect any TLS server (even with TLS 1.2 and on a different machine) which uses the same RSA key as the vulnerable SSLv2 server (drownattack.com).

ROBOT vulnerability
Trigger The server is not vulnerable to ROBOT.
Context

ROBOT (https://robotattack.org/) is the return of a 19-year-old vulnerability that allows performing RSA decryption and signing operations with the private key of a TLS server. It affects vulnerable server implementations that also allow the use of RSA encryption (e.g. TLS_RSA cipher suites).

Certificate expiration
Trigger The expiration date of this certificate is 2019-12-19 23:59:59 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. In particular, no revocation information will be kept about an expired certificate.

Certificate not valid yet
Trigger The start date of this certificate is 2014-12-20 00:00:00 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. A validity start date in the future is a sign that the certificate is bogus or that the system that generated it has a desynchronized clock.

Support for TLS compression (CRIME)
Trigger This service supports the following compression algorithms: NULL.
Context

The CRIME vulnerability (also known as CVE-2012-4929) happens when TLS compression is enabled. An attacker can get information about sensitive data in pages by observing the size of compressed responses. Using this, it is possible to impersonate users by retrieving their session cookies. This exploit has been demonstrated on HTTPS, but the weakness is fundamental to compression in TLS and may be exploitable in non-HTTP services.

Heartbleed vulnerability
Trigger The server is not vulnerable to Heartbleed.
Context

The OpenSSL Heartbleed bug (heartbleed.com, CVE-2014-0160) allows secrets including the server's private key to be extracted in the clear.

TLS (port 587 – SMTP)

Show scan details
Versions TLS 1.2
Ciphers
  • TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_CCM TLS 1.2
  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_CCM TLS 1.2
  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_128_GCM_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256 TLS 1.2
  • TLS_DHE_RSA_WITH_CAMELLIA_256_GCM_SHA384 TLS 1.2
  • TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_CAMELLIA_128_GCM_SHA256 TLS 1.2
  • TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_CAMELLIA_256_GCM_SHA384 TLS 1.2
  • TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 TLS 1.2
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS 1.2
  • TLS_RSA_WITH_AES_128_CBC_SHA TLS 1.2
  • TLS_RSA_WITH_AES_128_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_128_CCM TLS 1.2
  • TLS_RSA_WITH_AES_128_GCM_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_256_CBC_SHA TLS 1.2
  • TLS_RSA_WITH_AES_256_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_AES_256_CCM TLS 1.2
  • TLS_RSA_WITH_AES_256_GCM_SHA384 TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_128_CBC_SHA TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_128_GCM_SHA256 TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_256_CBC_SHA TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 TLS 1.2
  • TLS_RSA_WITH_CAMELLIA_256_GCM_SHA384 TLS 1.2
Cipher order Client
Compression
  • NULL TLS 1.2
Certificate key RSA 2048-bit test this key
Hash algorithm SHA-256
Diffie-Hellman
  • Group (2048-bit MODP from RFC 5114): 0xad107e1e9123a9d0d660faa79559c51fa20d64e5683b9fd1b54b1597b61d0a75e6fa141df95a56dbaf9a3c407ba1df15eb3d688a309c180e1de6b85a1274a0a66d3f8152ad6ac2129037c9edefda4df8d91e8fef55b7394b7ad5b7d0b6c12207c9f98d11ed34dbf6c6ba0b2c8bbc27be6a00e0a0b9c49708b3bf8a317091883681286130bc8985db1602e714415d9330278273c7de31efdc7310f7121fd5a07415987d9adc0a486dcdf93acc44328387315d75e198c641a480cd86a1b9e587e8be60e69cc928b2b9c52172e413042e9b23f10b0e16e79763c9b53dcf4ba80a29e3fb73c16b8e75b97ef363e2ffa31f71cf9de5384e71b81c0ac4dffe0c10e64f
  • Generator: 0xac4032ef4f2d9ae39df30b5c8ffdac506cdebe7b89998caf74866a08cfe4ffe3a6824a4e10b9a6f0dd921f01a70c4afaab739d7700c29f52c57db17c620a8652be5e9001a8d66ad7c17669101999024af4d027275ac1348bb8a762d0521bc98ae247150422ea1ed409939d54da7460cdb5f6c6b250717cbef180eb34118e98d119529a45d6f834566e3025e316a330efbb77a86f0c1ab15b051ae3d428c8f8acb70a8137150b8eeb10e183edd19963ddd9e263e4770589ef6aa21e7f5f2ff381b539cce3409d13cd566afbb48d6c019181e1bcfe94b30269edfe72fe9b6aa4bd7b5a0f1c71cfff4c19c418e1f6ec017981bc087f2a7065b384b890d3191f2bfa
Certificate start date 2014-12-20 00:00:00 UTC
Certificate expiration date 2019-12-19 23:59:59 UTC
Certificate serial number 169189091054436175579115634615590372918
Certificate issuer C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
Certificate subject OU=Domain Control Validated,OU=PositiveSSL,CN=mail.gsc-game.com
Certificate SANs
  • mail.gsc-game.com
  • www.mail.gsc-game.com
B
Warnings
Support for Triple DES cipher
Trigger The server supports a cipher suite containing the 3DES cipher.
Context

Three-key-3DES is a cipher with 168-bit keys but an effective key length of 112 bits because of a meet-in-the-middle attack. This is considered enough only for legacy. Furthermore, it has a 64-bit block size, which can be insufficient for some applications, for example because of birthday attacks (sweet32.info).

Fix Log in to get remediation advice
A!
Borderline Compliance Warnings
Diffie-Hellman group security
Trigger The server uses a commonly-shared 2048-bit Diffie-Hellman group.
Context

Diffie-Hellman is mainly used so that two machines can compute a shared secret and so benefit from forward secrecy.

For security, a 2048-bit group is reasonable although ECRYPT recommends a group size of at least 3072 bits (ECRYPT 2016 report). The use of commonly-shared 1024-bit groups such as Oakley group 2 is especially discouraged because of possible precomputation attacks (weakdh.org).

Certificate RSA key length
Trigger The server uses a 2048-bit RSA key.
Context

RSA keys must be long enough to provide reasonable security against brute-force attack by factoring. While 2048-bit keys are fine today, a minimum of 3072-bit is recommended by ECRYPT for new systems.

A
Passed
Support for SSL 2.0
Trigger SSL 2.0 not among the protocols offered by TLS server.
Context

SSL 2.0 has been officially deprecated as of March 2011 (RFC 6176).

Support for SSL 3.0
Trigger SSL 3.0 not among the protocols offered by TLS server.
Context

SSL 3.0 has been officially deprecated as of June 2015 (RFC 7568).

Support for TLS 1.0
Trigger TLS 1.0 not among the protocols offered by TLS server.
Context

TLS 1.0 is discouraged by PCI-DSS and has been considered non-compliant since June 2018 (PCI-DSS v3.2).

Security of hash function for certificate signature digest
Trigger The hash used for the certificate is SHA-256.
Context

The hash function used on certificate signatures must be cryptographically secure in order for the certificate not to be forgeable. Hash functions MD2 and MD5 are considered to be broken. SHA-1 certificates are in the process of being deprecated because of their weaknesses although many browsers and websites still support them. The SHA-2 family of functions (SHA-224, SHA-256, ...) are a safe alternative.

Support for Null cipher
Trigger The server doesn't support any cipher suites containing the NULL cipher.
Context

Application data is not encrypted when the NULL cipher is used, exposing it to eavesdroppers.

Support for Export-grade cipher suites
Trigger The server doesn't support any EXPORT cipher suites.
Context

For legacy reasons, some TLS cipher suites are composed of export-grade cryptography, which is insecure by today's standards. Furthermore, servers that accept EXPORT cipher suites may be vulnerable to the FREAK (freakattack.com) or the Logjam (weakdh.org) downgrade attacks.

Support for DES cipher
Trigger The server doesn't support any cipher suites containing the DES cipher.
Context

DES is a cipher with an effective key length of 56 bits, which is now considered too weak by many agencies, including ECRYPT and NIST (ECRYPT 2016 report, NIST SP 800-57, Part 1, Rev. 3).

Support for RC4 cipher
Trigger The server doesn't support any cipher suites containing the RC4 cipher.
Context

RC4 is a stream cipher in which significant weaknesses have been found. The use of this cipher in any protocol has been discouraged by ECRYPT as of 2014 (ECRYPT 2016 report).

In TLS, cipher suites using RC4 have been deprecated as of February 2015 (RFC 7465).

Support for cipher suites giving forward secrecy
Trigger The server supports some cipher suites that provide forward secrecy.
Context

Forward secrecy is achieved when the security of session keys is not affected by a compromise of long-term keys.

In TLS, forward secrecy is enabled by DHE, ECDHE and DH_anon cipher suites. They protect past communications from a compromise of a long-term key (such as an RSA key).

DROWN vulnerability
Trigger The server is not vulnerable to DROWN.
Context

A server is vulnerable to the "General DROWN" attack when it supports, willingly or not, weak SSLv2 cipher suites. A server is vulnerable to the even more powerful "Special DROWN" attack when it is affected by CVE-2016-0703. DROWN may affect any TLS server (even with TLS 1.2 and on a different machine) which uses the same RSA key as the vulnerable SSLv2 server (drownattack.com).

ROBOT vulnerability
Trigger The server is not vulnerable to ROBOT.
Context

ROBOT (https://robotattack.org/) is the return of a 19-year-old vulnerability that allows performing RSA decryption and signing operations with the private key of a TLS server. It affects vulnerable server implementations that also allow the use of RSA encryption (e.g. TLS_RSA cipher suites).

Certificate expiration
Trigger The expiration date of this certificate is 2019-12-19 23:59:59 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. In particular, no revocation information will be kept about an expired certificate.

Certificate not valid yet
Trigger The start date of this certificate is 2014-12-20 00:00:00 UTC.
Context

Each certificate defines a validity period. Outside of this period, it is not valid. A validity start date in the future is a sign that the certificate is bogus or that the system that generated it has a desynchronized clock.

Support for TLS compression (CRIME)
Trigger This service supports the following compression algorithms: NULL.
Context

The CRIME vulnerability (also known as CVE-2012-4929) happens when TLS compression is enabled. An attacker can get information about sensitive data in pages by observing the size of compressed responses. Using this, it is possible to impersonate users by retrieving their session cookies. This exploit has been demonstrated on HTTPS, but the weakness is fundamental to compression in TLS and may be exploitable in non-HTTP services.

Heartbleed vulnerability
Trigger The server is not vulnerable to Heartbleed.
Context

The OpenSSL Heartbleed bug (heartbleed.com, CVE-2014-0160) allows secrets including the server's private key to be extracted in the clear.