SSL-Tools

SSL check results of svenfranken.de

NEW You can also bulk check multiple servers.

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

JSON Refresh

Report created Sun, 14 Apr 2024 08:49:05 +0000

The mailservers of svenfranken.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @svenfranken.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.svenfranken.de
2a05:8b81:1000:300::2
 1
supported
mail.svenfranken.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.svenfranken.de
185.82.21.18
 1
supported
mail.svenfranken.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.svenfranken.de

Certificate chain
  • mail.svenfranken.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.svenfranken.de
Alternative Names
  • mail.svenfranken.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-22
Not valid after
2024-05-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
88:E5:0E:9B:9B:02:81:57:82:EA:D4:08:50:B7:CE:26:F0:56:C8:3B:DD:78:92:9E:C8:F4:BB:17:DB:9F:43:F2
SHA1
27:EE:A4:9C:2E:DD:BE:E6:B3:63:E4:94:AD:FA:1D:6F:F7:68:C1:99
X509v3 extensions
subjectKeyIdentifier
  • 4B:C3:38:5E:5A:F6:DF:0F:84:94:AB:DA:90:B2:45:62:47:96:1C:0B
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Feb 22 08:51:17.771 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D9:6D:C3:F9:94:69:BE:B8:1A:4E:0E:
  • 33:A9:FA:32:69:B1:85:D2:CF:3E:E1:48:50:E9:C5:FE:
  • A8:9B:35:5F:D1:02:20:19:35:38:1C:29:3C:E4:50:85:
  • 2C:FB:70:BE:1D:F5:45:7A:F1:77:E1:5D:80:46:2B:D6:
  • A3:FF:96:0E:A9:25:2A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Feb 22 08:51:17.933 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:87:B6:78:F3:BF:93:DE:6F:AA:E7:3E:
  • 64:B0:6B:E3:4D:5E:81:76:27:A8:5F:7D:9F:7F:81:EA:
  • E9:E4:54:7A:63:02:20:4C:5F:9E:41:4C:0B:D1:C9:E8:
  • 14:27:EC:31:2F:62:FF:2B:EC:1B:20:DD:26:BC:89:B5:
  • 8C:0F:E1:A2:EE:8D:39