SSL-Tools

SSL check results of salloth.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for salloth.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 Wed, 19 Feb 2025 01:38:29 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.salloth.de
85.214.150.74
 10
supported
salloth.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
salloth.de
85.214.150.74
 20
supported
salloth.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=salloth.de

Certificate chain
  • salloth.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)
  • salloth.de
Alternative Names
  • *.salloth.de
  • salloth.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-02-15
Not valid after
2025-05-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
86:72:74:D5:35:9B:3B:89:13:4C:FE:06:09:D2:05:1C:C8:F4:57:BE:7D:19:36:38:16:06:23:EE:CC:14:12:9A
SHA1
2B:8F:62:6D:6F:31:60:CC:FB:88:E0:A5:CC:54:27:92:30:B2:A1:D6
X509v3 extensions
subjectKeyIdentifier
  • 63:39:72:66:03:EC:A2:0D:C7:AF:1C:56:30:EB:4D:04:B0:40:B7:85
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 73:20:22:0F:08:16:8A:F9:F3:C4:A6:8B:0A:B2:6A:9A:
  • 4A:00:EE:F5:77:85:8A:08:4D:05:00:D4:A5:42:44:59
  • Timestamp : Feb 15 17:38:11.477 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C6:4C:3A:F2:BB:8E:F5:84:8C:15:32:
  • F6:0A:5B:5C:09:EC:ED:EC:1C:0F:87:96:C7:91:97:82:
  • 06:48:E8:00:EF:02:21:00:87:57:4E:FB:57:34:8C:AE:
  • F4:F1:21:1F:C6:C9:32:6F:8D:43:97:18:54:55:6F:4A:
  • 64:23:8B:5C:5A:37:0B:2D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Feb 15 17:38:11.499 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:09:6B:1C:06:3B:17:F2:07:F2:36:AF:4D:
  • 78:78:C5:44:24:6A:FC:2F:88:83:EB:BA:70:63:A7:AB:
  • EB:C9:B2:A8:02:20:25:F4:A6:31:95:A1:DD:3B:EE:B4:
  • 21:39:8D:75:F3:F1:C4:BE:45:66:D6:ED:6A:D2:E2:FA:
  • F8:17:C0:50:DD:F8