SSL-Tools

SSL check results of teiter.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for teiter.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, 10 Sep 2025 00:30:07 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mailin.email-saar.de
2a03:4000:23:472::42
 30
supported
email-saar.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
mailin.email-saar.de
185.228.139.48
 30
supported
email-saar.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=email-saar.de

Certificate chain
  • email-saar.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • email-saar.de
Alternative Names
  • *.email-saar.de
  • email-saar.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-07-13
Not valid after
2025-10-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
69:89:C8:78:9A:82:64:AF:BC:30:53:CF:DF:DF:E5:AE:4F:B6:ED:E9:9F:80:E2:E0:96:2E:67:0B:8B:57:42:21
SHA1
0F:40:9B:FC:25:F1:63:16:80:BB:5B:95:85:A6:6D:89:1C:99:48:27
X509v3 extensions
subjectKeyIdentifier
  • 1B:D9:B6:0A:50:B9:27:D3:6F:82:D1:46:32:B2:5C:31:F5:37:6A:75
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/80.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 : Jul 13 16:03:44.116 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7E:FB:57:BB:71:B0:0D:46:53:DC:A1:86:
  • 6A:F5:81:FE:2E:12:6C:37:D4:95:2A:C5:52:2F:74:60:
  • B6:A2:25:D6:02:20:21:17:04:05:EB:A9:10:0C:90:80:
  • E5:0D:81:FF:87:9A:63:E0:7B:96:B4:18:E0:25:9D:EE:
  • 57:BC:BB:C8:68:36
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : Jul 13 16:03:44.134 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0A:4E:63:30:ED:DC:72:4B:28:EA:8A:4E:
  • E5:6C:33:89:02:19:FE:02:22:72:98:37:9E:D5:AC:00:
  • C0:E5:7D:9F:02:21:00:C8:94:4A:AC:7F:7E:3E:BA:D0:
  • 3F:A3:D9:92:2F:CE:EE:81:1F:9F:0D:59:E4:03:86:44:
  • D1:30:82:EA:78:37:B5