SSL check results of mail.valentin-kahl.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.valentin-kahl.de 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 Thu, 25 Apr 2024 14:14:00 +0000

The mailservers of mail.valentin-kahl.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.valentin-kahl.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.valentin-kahl.de
173.212.253.215
-
supported
mail.valentin-kahl.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.valentin-kahl.de
2a02:c207:3003:3022::1
-
supported
mail.valentin-kahl.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @mail.valentin-kahl.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.valentin-kahl.de

Certificate chain
  • mail.valentin-kahl.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.valentin-kahl.de
Alternative Names
  • imap.valentin-kahl.de
  • mail.valentin-kahl.de
  • smtp.valentin-kahl.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-26
Not valid after
2024-06-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
45:55:0F:97:A0:CA:63:BB:68:00:C3:2A:94:81:3D:4E:82:1A:69:75:FD:D2:E8:E8:C7:1A:A2:1C:C8:5D:5A:7F
SHA1
41:BF:AE:48:53:08:D5:C2:C6:7F:94:13:66:9F:75:61:C1:8F:70:90
X509v3 extensions
subjectKeyIdentifier
  • 66:CA:35:E5:ED:1D:8C:11:32:70:28:A6:F3:08:22:6B:39:76:B4:3F
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 26 20:49:26.923 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7A:0A:E0:BF:A2:F8:59:6C:20:A3:36:39:
  • D3:BB:1B:57:F1:EF:07:C9:E0:24:74:87:B4:31:BC:B2:
  • 90:A2:A1:F8:02:21:00:B3:C7:28:A6:0E:29:21:C2:7D:
  • 0A:2B:E3:13:FA:79:17:7D:48:44:EF:D4:2B:5B:13:07:
  • CA:9B:6D:7F:E6:8F:62
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 26 20:49:26.971 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:27:8B:2C:62:0E:E5:52:DF:84:09:31:E2:
  • E8:F2:3F:B2:94:A2:53:C1:CF:C3:54:20:E3:31:CA:BD:
  • 09:1F:47:40:02:20:7C:DC:09:FD:6C:2B:D0:F0:36:A0:
  • 83:45:43:06:2C:EA:D3:8E:E9:5B:B4:5A:B7:4C:CB:BF:
  • 94:34:C2:FC:55:37