SSL-Tools

SSL check results of mail.seibelapps.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.seibelapps.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, 04 Nov 2024 01:30:48 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.seibelapps.de
2.56.98.25
 -
supported
*.seibelapps.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
mail.seibelapps.de
2a03:4000:3e:19d:28f3:e4ff:fec0:8b60
 -
supported
*.seibelapps.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.seibelapps.de

Certificate chain
  • *.seibelapps.de
    • remaining
    • 384 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.seibelapps.de
Alternative Names
  • *.seibelapps.de
  • seibelapps.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-09-05
Not valid after
2024-12-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CD:D6:DF:06:E1:93:DC:E2:C8:64:BA:B6:05:F0:76:AE:E7:DC:97:E7:10:BE:8F:34:46:EC:E8:4E:55:35:63:C5
SHA1
8C:BE:36:ED:86:7D:06:16:78:15:D3:12:38:D7:D2:3F:B7:7E:9A:57
X509v3 extensions
subjectKeyIdentifier
  • 18:6A:EF:83:11:18:F8:60:8B:54:17:A5:BE:F7:40:60:B7:58:EC:14
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 5 10:23:17.500 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DD:14:D9:64:BE:9E:D6:0D:90:D6:3B:
  • EC:3E:36:6B:6D:0A:A8:0C:F5:D2:8F:50:0E:88:4F:D6:
  • 85:69:FF:B4:90:02:20:43:52:30:49:6D:44:6A:22:19:
  • B1:BD:1E:40:80:EE:25:01:CB:8A:BE:03:62:F0:FC:99:
  • 9C:1B:D6:41:9F:16:33
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Sep 5 10:23:17.451 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A9:6B:2A:67:07:57:A0:49:99:91:4D:
  • DC:9D:A9:8F:0B:2B:13:75:0C:A2:C3:61:44:3E:1B:35:
  • 18:66:E4:71:BD:02:20:28:F9:AC:28:5D:52:94:80:53:
  • 00:76:F5:7F:02:F7:D2:A5:3A:0C:62:24:A8:43:52:A4:
  • BE:0F:F2:BD:9D:7B:D1