SSL-Tools

SSL check results of schaerf-druck.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for schaerf-druck.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, 30 Sep 2022 12:04:40 +0000

The mailservers of schaerf-druck.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @schaerf-druck.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
srv.fletschtec.de
2a01:4f8:a1:104:1:2:104:1
 10
supported
srv.fletschtec.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
srv.fletschtec.de
88.198.202.13
 10
supported
srv.fletschtec.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 @schaerf-druck.de address so far. Test mail delivery

Certificates

First seen at:

CN=srv.fletschtec.de

Certificate chain
  • srv.fletschtec.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)
  • srv.fletschtec.de
Alternative Names
  • srv.fletschtec.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-09-30
Not valid after
2022-12-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BD:7C:45:A1:71:5B:C2:8F:48:62:4F:EE:8B:9D:C2:19:96:97:F7:1F:5B:9B:1E:40:7E:CE:19:05:B9:89:C7:58
SHA1
40:78:35:30:D7:A0:83:43:67:B7:66:76:DC:C0:4F:7A:3F:A4:E3:43
X509v3 extensions
subjectKeyIdentifier
  • 5E:D2:81:F5:5B:21:F8:BD:DB:11:9B:BC:BA:CB:97:B2:45:9B:13:C4
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 : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
  • 4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
  • Timestamp : Sep 30 11:58:38.404 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:32:77:5E:F0:F9:C2:BF:F0:7F:FD:69:5F:
  • 65:E6:FF:59:A3:D2:36:8F:EB:E9:1B:79:28:0E:ED:56:
  • 3B:0D:CE:17:02:21:00:EF:56:89:01:15:97:2E:94:7F:
  • F5:F4:FC:54:7A:61:85:45:14:80:C0:C6:33:18:4A:E6:
  • C1:48:09:17:05:05:17
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Sep 30 11:58:38.236 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9D:17:B5:C6:E6:5E:15:38:1A:C2:91:
  • 38:CE:DF:BB:4F:11:BD:25:CF:1E:E5:D8:47:45:75:4F:
  • A8:23:A5:F6:48:02:21:00:92:D7:CE:E1:8B:D6:4D:74:
  • 65:9C:28:EF:07:F7:AC:C2:80:52:72:DF:54:30:96:9D:
  • 51:7D:54:93:00:4A:7C:89