SSL check results of seiwert.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for seiwert.org 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 Tue, 17 Sep 2024 21:35:16 +0000

The mailservers of seiwert.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @seiwert.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.seiwert.org
152.89.104.91
10
supported
mx.seiwert.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
10 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx.seiwert.org

Certificate chain
  • mx.seiwert.org
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mx.seiwert.org
Alternative Names
  • autoconfig.seiwert.org
  • autodiscover.seiwert.org
  • mta-sts.seiwert-net.de
  • mta-sts.seiwert.org
  • mx.seiwert.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-16
Not valid after
2024-12-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E9:A8:E1:97:76:9A:88:B0:83:7C:BB:87:E0:77:63:C8:E0:83:8C:88:33:5A:A1:23:68:2F:BA:DA:6E:81:87:6A
SHA1
BD:EB:62:B4:78:57:13:85:89:96:C2:B5:04:33:B1:AC:FF:30:69:4E
X509v3 extensions
subjectKeyIdentifier
  • A0:8F:1F:1C:1B:7E:93:7B:6B:60:85:FA:8D:AE:79:5C:4F:DE:EC:A8
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 16 21:27:02.918 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CB:6D:7D:48:55:8A:0B:34:7C:3E:BF:
  • 9A:E7:DF:70:70:E1:4C:D3:E4:96:14:2C:86:2E:31:8E:
  • 45:F2:29:E1:2D:02:21:00:94:F8:61:D7:B4:5B:15:56:
  • 68:CF:87:88:9E:6F:DD:95:3B:DD:D8:6E:56:A4:42:7F:
  • 5A:80:87:91:10:13:BF:A6
  • 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 16 21:27:02.988 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:04:A6:0A:55:3C:00:A0:30:A1:AC:29:61:
  • D3:01:8A:FA:7C:FB:94:4A:23:D6:5D:3D:3C:64:27:24:
  • 3E:78:C4:CE:02:20:3B:51:12:66:F3:77:50:5D:2A:78:
  • 08:DB:48:B7:CB:CE:75:1D:CB:7E:BB:12:E9:13:E8:2E:
  • 4F:EE:7F:55:71:E3