SSL check results of lachaloupe.eu

NEW You can also bulk check multiple servers.

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

Report created Tue, 22 Oct 2024 10:30:26 +0000

The mailservers of lachaloupe.eu can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.lachaloupe.eu
2a01:4f9:c011:ab72::1
10
supported
*.lachaloupe.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.lachaloupe.eu
135.181.148.37
10
supported
*.lachaloupe.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.lachaloupe.eu

Certificate chain
  • *.lachaloupe.eu
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • *.lachaloupe.eu
Alternative Names
  • *.lachaloupe.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-10-18
Not valid after
2025-01-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C1:D2:D4:63:9B:36:8F:C0:D5:5A:E7:00:A7:6B:6C:BD:C0:60:B2:40:ED:3A:2B:4B:BC:C4:2D:E8:30:C5:4C:42
SHA1
6D:D6:7E:3D:2E:D8:56:D8:18:82:19:E1:AE:A2:F7:E7:70:9F:EC:EE
X509v3 extensions
subjectKeyIdentifier
  • 6A:FB:59:6A:6E:C9:DD:4C:5E:6B:F0:EC:04:59:2B:F6:F4:0F:77:62
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 18 13:28:32.627 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FE:F5:14:4F:8D:25:48:A1:DC:98:89:
  • A2:B5:50:1C:CA:6A:FC:9E:FB:EF:6E:0E:C1:B9:98:C1:
  • E6:9E:E9:4A:12:02:21:00:ED:12:C2:24:21:08:B6:C1:
  • 63:CF:36:BB:FB:D2:A1:3A:8D:9B:45:E0:90:F3:11:DD:
  • 3A:6E:53:52:C6:67:F0:2D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Oct 18 13:28:32.747 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FA:1F:39:E5:D8:D7:DE:94:F0:EE:B1:
  • AE:21:4E:46:A0:58:0C:3D:73:99:4C:8E:25:A3:43:20:
  • 4D:8C:11:AB:40:02:21:00:BC:AA:14:65:30:21:2E:F1:
  • C2:45:99:79:04:54:8C:E2:E9:2B:C9:1B:CD:B3:D7:A6:
  • C9:A1:C2:6F:4C:9B:EC:A1