SSL check results of mail.schellworth.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.schellworth.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 Mon, 29 Apr 2024 19:49:54 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.schellworth.de
2.59.132.108
-
supported
schellworth.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
mail.schellworth.de
2a0d:5940:7:9b::8e65
-
supported
schellworth.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s

Outgoing Mails

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

Certificates

First seen at:

CN=schellworth.de

Certificate chain
  • schellworth.de
    • remaining
    • 256 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • schellworth.de
Alternative Names
  • cloud.sdips.de
  • mail.schellworth.de
  • mail.schellworth.name
  • schellworth.de
  • schellworth.name
  • sdips.de
  • sync.sdips.de
  • www.schellworth.de
  • www.schellworth.name
  • www.sdips.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-17
Not valid after
2024-06-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E3:C7:62:7A:37:7A:66:60:EC:05:3F:5E:8C:87:71:AB:49:6E:26:68:09:F5:9E:02:7D:C9:E2:81:EF:DA:26:07
SHA1
B8:74:4E:21:C6:3E:BD:99:1C:F3:E7:E4:AA:46:91:DE:14:A6:BB:CF
X509v3 extensions
subjectKeyIdentifier
  • 7F:38:15:CD:31:9F:9E:30:62:30:1D:20:67:25:14:39:03:14:C1:6C
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 : Mar 17 02:51:08.678 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B5:5B:0B:AB:DF:37:F3:CA:30:8A:2C:
  • 37:C5:99:5D:9C:82:62:73:E1:E8:D9:F6:42:5A:EA:73:
  • 31:08:3C:92:2C:02:20:73:BF:53:5C:81:36:4B:05:1B:
  • 7D:54:2C:EF:14:13:43:E9:CA:D0:47:FD:E1:AF:FE:61:
  • A0:17:C0:C8:D3:45:AA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 17 02:51:08.710 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AB:6F:0D:2D:1A:98:22:70:AA:28:35:
  • 31:78:49:42:CD:24:1F:23:9E:D3:D5:1A:0A:96:09:EF:
  • C7:16:99:0E:4F:02:21:00:CD:03:C4:62:FC:D5:D9:C4:
  • 82:44:FD:25:6A:07:BE:70:91:AA:AE:6A:2F:05:81:21:
  • F5:D0:7A:9B:BF:A7:0C:15

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.schellworth.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid