SSL-Tools

SSL check results of spegel-beck.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for spegel-beck.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 Mon, 23 Sep 2024 00:30:35 +0000

The mailservers of spegel-beck.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @spegel-beck.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
host.deutschetopvermittler.de
2a01:4f8:121:126::2
 10
supported
host.deutschetopvermittler.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
host.deutschetopvermittler.de
78.46.100.196
 10
supported
host.deutschetopvermittler.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 @spegel-beck.de address so far. Test mail delivery

Certificates

First seen at:

CN=host.deutschetopvermittler.de

Certificate chain
  • host.deutschetopvermittler.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)
  • host.deutschetopvermittler.de
Alternative Names
  • host.deutschetopvermittler.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-01
Not valid after
2024-11-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
04:86:40:AB:C8:F8:89:EC:EA:B9:E7:A2:13:9F:1C:A9:ED:1F:24:DC:E6:E9:87:A5:4B:FB:C6:20:5F:D7:07:1F
SHA1
C5:99:6E:D5:35:3D:50:6A:9B:50:1D:66:8E:DE:4E:0A:D6:39:DD:FE
X509v3 extensions
subjectKeyIdentifier
  • F6:A5:AA:2E:09:F8:C5:39:23:00:E2:98:29:1B:84:4C:93:4E:8E:CE
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 : 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 : Sep 1 15:20:09.656 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1F:1A:75:10:EF:E7:BC:D3:2B:C5:B2:27:
  • 3E:58:3D:57:CE:3C:4B:69:7E:CB:4E:71:9E:1B:DD:55:
  • 0B:95:A0:48:02:21:00:E4:78:04:84:1A:99:95:3C:80:
  • E4:11:05:04:4F:42:A1:DD:73:7E:D1:9C:BE:75:73:70:
  • 41:59:1F:A7:AF:93:D2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Sep 1 15:20:09.734 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1D:A3:18:A4:68:EB:5E:FA:02:E5:D4:8C:
  • AD:B2:38:85:4D:88:4A:07:D5:D8:F1:C1:88:A1:0F:51:
  • 0D:79:4C:64:02:20:62:D9:79:27:3E:24:E8:20:74:C9:
  • 03:8F:19:5A:75:8D:44:07:B0:81:B7:01:FD:38:D8:CE:
  • 84:EE:DB:63:93:E0