SSL check results of tenexch.games

NEW You can also bulk check multiple servers.

Discover if the mail servers for tenexch.games 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

Report created Fri, 14 Mar 2025 01:39:42 +0000

We can not guarantee a secure connection to the mailservers of tenexch.games!

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

/mailservers/tenexch.games

Servers

Incoming Mails

These servers are responsible for incoming mails to @tenexch.games addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
tenexch.games
149.28.146.25
-
supported
flyseluler.xyz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
11 s
tenexch.games
2a02:4780:6:1858::1b3c:a250:b
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=flyseluler.xyz

Certificate chain
  • flyseluler.xyz
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • flyseluler.xyz
Alternative Names
  • flyseluler.xyz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-02-16
Not valid after
2025-05-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1B:99:DC:E5:86:1D:21:F2:C5:C3:0B:CC:B7:C0:A7:D7:4B:B8:55:42:FD:6C:CE:B2:BE:C5:DD:B1:45:B5:7F:29
SHA1
AB:FD:CD:66:A6:0C:93:E7:DD:2B:62:15:8F:D3:DE:5D:C2:C4:D1:4F
X509v3 extensions
subjectKeyIdentifier
  • 62:2F:39:CF:6D:B8:D9:22:54:37:B0:1F:BA:CC:14:97:88:6E:D3:57
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Feb 16 10:47:09.564 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7D:FE:44:89:2F:DE:2D:79:9F:69:79:FE:
  • 5E:25:0C:C3:63:A8:29:F0:62:4A:EA:3E:EA:CD:34:86:
  • 20:92:80:1C:02:20:19:33:4D:C6:45:1A:21:CF:85:AB:
  • F2:B6:43:95:E6:91:75:7B:C9:F6:E0:FF:F2:42:89:D4:
  • E3:3C:BE:9A:53:63
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DE:85:81:D7:50:24:7C:6B:CD:CB:AF:56:37:C5:E7:81:
  • C6:4C:E4:6E:D6:17:63:9F:8F:34:A7:26:C9:E2:BD:37
  • Timestamp : Feb 16 10:47:09.558 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6B:E5:F2:70:6A:AD:FD:19:A5:39:52:13:
  • 4E:0A:06:9B:A2:CB:2E:1F:0E:62:F3:D1:09:6E:7C:81:
  • 46:A2:C6:96:02:21:00:D1:9F:62:BD:77:06:B2:D8:14:
  • B1:09:AF:B2:D5:8C:3D:FF:25:57:4C:6E:84:7D:B0:01:
  • F5:C9:C9:27:35:06:45