SSL-Tools

SSL check results of michael-thumann.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for michael-thumann.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 Sat, 14 Aug 2021 20:22:21 +0000

The mailservers of michael-thumann.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @michael-thumann.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
utm-01.michael-thumann.de
185.248.142.25
 10
supported
utm-01.michael-thumann.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @michael-thumann.de sender addresses. Test mail delivery

Host TLS Version & Cipher
utm-01.michael-thumann.de (185.248.142.25)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=utm-01.michael-thumann.de

Certificate chain
  • utm-01.michael-thumann.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)
  • utm-01.michael-thumann.de
Alternative Names
  • utm-01.michael-thumann.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-08-01
Not valid after
2021-10-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3A:AE:4A:D6:AD:B3:72:8A:DD:3D:23:52:E3:58:04:6F:EA:57:72:EB:A9:2F:FB:10:64:D5:5A:01:79:41:A3:B3
SHA1
C3:5C:F4:24:2A:EE:65:06:51:4B:E6:EB:1F:C9:BF:3B:35:A9:2C:31
X509v3 extensions
subjectKeyIdentifier
  • 93:8B:6A:3E:87:47:28:6B:3D:BA:A9:E5:F7:96:23:50:51:12:20:15
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 : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Aug 1 22:39:19.816 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7A:00:F2:6B:B9:79:28:75:59:DA:05:36:
  • 59:0F:83:01:84:2E:80:DE:E8:3B:85:F9:9E:45:84:0C:
  • D9:DB:D1:86:02:20:55:4C:17:35:42:17:BC:DC:46:9C:
  • 36:C3:92:CD:1D:AA:AD:6C:16:B4:43:2D:38:76:55:F8:
  • 2C:BE:67:2E:BD:7A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Aug 1 22:39:19.991 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1A:27:25:38:CF:7F:6F:D6:36:64:63:86:
  • 34:0C:EE:34:75:19:14:00:5B:8F:1E:38:FE:74:94:9D:
  • C9:A4:69:DA:02:20:5E:B3:6C:D9:FC:28:12:67:EC:79:
  • A3:48:A4:AB:AF:06:A8:14:4A:DD:7A:52:7D:7B:E2:E0:
  • 4A:DA:00:0D:98:DA