SSL-Tools

SSL check results of martinwemlinger.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for martinwemlinger.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 Fri, 05 Mar 2021 22:49:34 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.martinwemlinger.de
2a03:4000:3b:6b0::
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.martinwemlinger.de
185.163.116.185
 10
supported
mail.martinwemlinger.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.martinwemlinger.de

Certificate chain
  • mail.martinwemlinger.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • mail.martinwemlinger.de
Alternative Names
  • imap.martinwemlinger.de
  • mail.martinwemlinger.de
  • smtp.martinwemlinger.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-05
Not valid after
2021-06-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A9:3F:07:67:EA:6F:7C:84:F2:47:B7:36:3A:A9:3F:A4:2B:93:2B:14:31:AF:F3:1D:01:B7:E3:DB:DA:0F:48:93
SHA1
14:ED:92:69:03:05:53:CC:70:21:BE:EA:51:45:FA:E5:FE:02:58:FA
X509v3 extensions
subjectKeyIdentifier
  • 29:0F:B3:8F:79:EE:02:26:3E:F6:8F:EB:7B:00:E5:20:45:DA:DE:79
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Mar 5 18:46:51.707 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:58:85:F2:3F:90:19:84:45:7A:58:97:99:
  • 6C:92:58:D6:EB:A7:7C:20:3A:5F:3D:33:F8:CF:2A:85:
  • 0B:D5:73:82:02:21:00:EF:C5:DE:56:77:FE:31:3E:A3:
  • C2:A6:D3:D8:60:D8:31:38:AB:2D:4E:D9:49:44:1F:2E:
  • 37:78:17:E8:DB:68:62
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Mar 5 18:46:51.740 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:31:D7:BF:5B:62:D1:9C:03:6B:20:B1:CF:
  • 1E:65:43:73:22:93:88:A6:C2:C7:35:2B:42:45:3E:04:
  • 26:63:93:2E:02:21:00:92:0F:82:9D:67:8E:A1:D2:9E:
  • 2C:0F:52:B3:53:80:5E:D7:6F:71:90:9D:DB:D1:B8:B1:
  • CB:1B:C5:A6:5A:CF:24