SSL check results of hauck-manuel.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for hauck-manuel.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 Tue, 04 May 2021 15:12:21 +0000

The mailservers of hauck-manuel.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @hauck-manuel.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
server.hauck-manuel.de
2a01:4f8:1c0c:58e3::1
10
supported
hauck-manuel.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
server.hauck-manuel.de
195.201.25.6
10
supported
hauck-manuel.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s

Outgoing Mails

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

Host TLS Version & Cipher
server.hauck-manuel.de (195.201.25.6)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=hauck-manuel.de

Certificate chain
  • hauck-manuel.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)
  • hauck-manuel.de
Alternative Names
  • hauck-manuel.de
  • imap.hauck-manuel.de
  • pop3.hauck-manuel.de
  • server.hauck-manuel.de
  • smtp.hauck-manuel.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-05-03
Not valid after
2021-08-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
94:46:C5:2E:5D:F3:94:A6:E7:4A:07:82:7C:82:B1:88:52:4A:F9:A3:18:D9:85:B8:45:B3:AF:C9:E0:B5:7A:C9
SHA1
BD:65:0D:78:47:01:E0:EB:05:0C:D4:F0:C5:EE:13:48:DC:35:A3:31
X509v3 extensions
subjectKeyIdentifier
  • 3F:4B:CC:52:2F:D3:33:BC:3F:AA:6F:F7:68:CF:FA:DA:BF:96:24:62
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : May 3 08:54:55.587 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E2:D1:33:D6:D3:A3:E4:4B:47:EE:1D:
  • DD:C5:24:F3:DA:FF:37:34:1E:93:E9:68:09:F0:36:CC:
  • DC:B4:12:CC:4E:02:20:0D:0F:F0:5D:C8:23:48:01:B1:
  • 06:5B:CB:87:87:D8:3C:61:74:BC:6D:CB:05:87:3F:7C:
  • 9A:04:9C:8D:A7:31:0B
  • 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 : May 3 08:54:55.613 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8E:1E:60:AF:99:C6:D6:05:54:0B:E4:
  • 71:7E:74:AB:AF:6F:DD:76:4F:27:2B:D2:DB:3B:5B:85:
  • 68:40:C2:3E:AF:02:20:68:43:AB:07:F4:B6:C0:A0:3A:
  • F5:64:A3:33:7E:82:D3:73:C0:FC:10:C2:C3:6F:CB:2B:
  • 2E:41:25:D1:EA:94:80