SSL-Tools

SSL check results of gamersdecide.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for gamersdecide.com can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Sun, 22 May 2022 11:10:45 +0000

We can not guarantee a secure connection to the mailservers of gamersdecide.com!

Please contact the operator of gamersdecide.com and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/gamersdecide.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @gamersdecide.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.gamersdecide.com
159.65.162.36
 10
supported
mail.gamersdecide.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
15 s
newmail.gamersdecide.com
2604:a880:4:1d0::68a:7000
Results incomplete
20
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
newmail.gamersdecide.com
137.184.183.47
Results incomplete
20
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @gamersdecide.com address so far. Test mail delivery

Certificates

First seen at:

CN=mail.gamersdecide.com

Certificate chain
Subject
Common Name (CN)
  • mail.gamersdecide.com
Alternative Names
  • mail.gamersdecide.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2018-08-21
Not valid after
2018-11-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
46:F7:E5:32:A6:03:2D:67:7C:8B:7C:3F:D2:E5:FF:94:B2:DB:98:01:69:31:BE:BB:46:1F:1A:74:AC:CA:EE:DF
SHA1
0E:57:91:35:FE:ED:79:96:25:BA:40:CB:CC:AA:4D:4A:06:FC:A4:85
X509v3 extensions
subjectKeyIdentifier
  • DC:0B:8A:26:41:43:90:33:5F:1C:FE:50:33:14:2D:9D:8C:06:84:34
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
  • User Notice:
  • Explicit Text: This Certificate may only be relied upon by Relying Parties and only in accordance with the Certificate Policy found at https://letsencrypt.org/repository/
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DB:74:AF:EE:CB:29:EC:B1:FE:CA:3E:71:6D:2C:E5:B9:
  • AA:BB:36:F7:84:71:83:C7:5D:9D:4F:37:B6:1F:BF:64
  • Timestamp : Aug 21 06:01:33.288 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:37:21:C4:F0:CE:E6:6F:C5:49:0E:2C:E6:
  • C5:BF:5F:63:6D:FF:6E:CB:7E:29:2D:AA:B6:8B:26:99:
  • F7:F1:1B:3F:02:21:00:D1:73:62:0E:10:D1:38:23:CC:
  • A7:75:09:70:68:AB:22:D1:FC:12:C2:B4:48:4E:D1:8A:
  • EC:EF:9A:E6:2B:4C:18
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:3C:51:96:54:C8:39:65:BA:AA:50:FC:58:07:D4:B7:
  • 6F:BF:58:7A:29:72:DC:A4:C3:0C:F4:E5:45:47:F4:78
  • Timestamp : Aug 21 06:01:33.807 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:59:F6:6D:1B:99:46:A2:39:D9:23:C0:F6:
  • FE:CF:0B:F5:0E:32:A8:A2:0B:21:81:7E:31:DC:CB:98:
  • B3:4C:E4:66:02:20:4C:3E:1A:00:BC:33:21:5A:E8:58:
  • BD:F6:FA:25:A3:F1:3B:41:E2:11:4E:30:7D:00:86:6A:
  • 85:E4:EB:40:92:E1