SSL-Tools

SSL check results of samxela.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for samxela.eu 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 Sat, 06 Sep 2025 05:26:28 +0000

We can not guarantee a secure connection to the mailservers of samxela.eu!

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

/mailservers/samxela.eu

Servers

Incoming Mails

These servers are responsible for incoming mails to @samxela.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.samxela.eu
2a02:c206:3015:7503::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
mail.samxela.eu
109.205.180.41
 10
supported
mail.samxela.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.samxela.eu

Certificate chain
  • mail.samxela.eu
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Expired
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.samxela.eu
Alternative Names
  • mail.samxela.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-06-07
Not valid after
2025-09-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
51:3C:B6:FC:C4:81:BB:9A:B0:55:BB:0C:B6:31:92:A7:FA:7C:D7:37:5F:F0:BD:D5:7B:BE:4F:4A:42:A4:BA:60
SHA1
40:C6:C2:3C:34:98:E8:9C:C0:73:03:7A:4C:1D:FF:5C:91:7A:11:7C
X509v3 extensions
subjectKeyIdentifier
  • 78:BC:0C:6E:B9:C3:E9:09:D9:10:43:24:C7:14:00:31:A1:53:C0:6B
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/21.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jun 7 11:03:02.660 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:93:E2:88:72:5F:4E:53:24:38:BD:F3:
  • 38:5D:C5:F1:21:EF:86:33:66:70:1C:D2:6F:7E:CF:EE:
  • 01:D7:3C:37:37:02:20:0A:FF:C9:64:97:4A:24:F6:5F:
  • 0A:2F:C3:34:A8:1B:64:2C:F6:52:EC:33:CD:10:08:F3:
  • D3:60:4A:1B:44:A9:5D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Jun 7 11:03:04.660 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:81:1B:7C:64:42:DB:2F:9E:7C:F0:F2:
  • AE:54:EC:15:0A:C1:BB:A9:EA:1E:1F:41:80:3D:EB:63:
  • 13:9A:AC:6E:10:02:20:67:9E:21:8B:7B:11:0D:66:5F:
  • 8C:DF:A5:E8:24:44:D5:22:4E:57:02:AA:99:0B:CB:17:
  • 32:5D:EA:83:0E:3F:A8