SSL-Tools

SSL check results of schenkspedition.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for schenkspedition.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 Thu, 10 Jul 2025 15:47:41 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mxlb.ispgateway.de
80.67.18.126
Results incomplete
100
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.schenkspedition.de
212.184.95.242
 110
supported
mail.schenkspedition.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.schenkspedition.de

Certificate chain
  • mail.schenkspedition.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.schenkspedition.de
Alternative Names
  • autodiscover.schenkspedition.de
  • mail.schenkspedition.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-06-23
Not valid after
2025-09-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EA:18:83:35:5B:E0:F1:A6:FB:3F:F6:B9:84:3F:8C:B4:E2:06:3B:23:50:68:87:C9:E1:0B:C4:5F:A3:A4:A2:1D
SHA1
C4:16:67:B9:CC:23:B6:C9:9A:3E:0B:AD:32:99:36:18:A3:BB:5B:A9
X509v3 extensions
subjectKeyIdentifier
  • 0E:F3:A8:9B:99:F8:1E:42:3C:EB:2E:CB:BD:82:62:3B:FA:45:9C:BF
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/66.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jun 23 17:20:20.208 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:06:0A:4E:47:C1:30:41:15:F0:75:08:60:
  • B3:25:7D:D6:3F:91:D9:45:24:BF:79:BF:D6:34:8A:DB:
  • 31:66:62:B2:02:20:16:14:FD:F4:8F:13:A3:7C:F5:E2:
  • 2B:00:34:A4:CE:FD:E6:BB:FC:78:14:5B:1E:9F:82:29:
  • FA:ED:49:2E:03:54
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jun 23 17:20:20.205 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9E:3C:1A:84:06:3C:E8:03:7B:66:2B:
  • C8:D2:05:DB:66:FC:83:CA:5E:BF:1E:33:ED:95:DE:70:
  • 2D:12:A7:CC:26:02:20:5B:C7:6F:DC:3C:07:92:F0:C6:
  • EF:66:A9:26:B1:4D:9F:5D:A7:4B:E0:F7:7B:97:32:D5:
  • 1F:53:50:F3:C6:9D:0B