SSL-Tools

SSL check results of mail.richterserv.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.richterserv.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 Thu, 18 Sep 2025 06:04:09 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.richterserv.de
178.254.25.112
 -
supported
mail.richterserv.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.richterserv.de
2a00:6800:3:f91::112
 -
supported
mail.richterserv.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.richterserv.de

Certificate chain
  • mail.richterserv.de
    • remaining
    • 384 bit
    • ecdsa-with-SHA384
      • E8
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.richterserv.de
Alternative Names
  • mail.richterserv.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E8
validity period
Not valid before
2025-09-18
Not valid after
2025-12-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BE:34:DE:5A:54:00:ED:C0:4B:63:DD:97:59:46:A4:AA:C0:CD:75:6E:50:E6:76:6C:E0:92:5F:C6:6F:A7:98:73
SHA1
AD:A6:A0:02:52:D1:8C:EC:BD:D1:A2:D9:D9:18:DD:D3:EB:7A:6E:CE
X509v3 extensions
subjectKeyIdentifier
  • B5:7F:34:BA:69:BB:4B:F8:54:59:31:E5:64:8D:86:62:F9:D9:CA:35
authorityKeyIdentifier
  • keyid:8F:0D:13:A2:F6:2E:7E:D1:50:6C:33:18:38:5D:59:8E:23:72:91:CA
authorityInfoAccess
  • CA Issuers - URI:http://e8.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e8.c.lencr.org/47.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Sep 18 04:59:17.657 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2F:53:DC:7F:6B:06:3A:FE:25:F0:93:0F:
  • 0A:1D:B0:D9:36:39:FC:93:7E:B0:B3:00:F8:16:86:47:
  • 50:BD:95:5D:02:20:63:96:60:3B:C8:01:AA:F1:81:E8:
  • 1A:30:B0:03:2C:6D:97:08:8E:9D:80:16:2B:C3:F3:30:
  • B2:01:81:06:43:12
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Sep 18 04:59:17.717 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D3:E3:AF:20:A9:6F:13:F7:AC:7B:26:
  • BE:08:9C:FF:7D:E4:F9:CD:ED:6E:90:0B:8F:81:31:75:
  • 30:A6:D4:E0:74:02:20:67:D9:ED:B8:5D:83:DE:FF:C9:
  • 28:6B:C3:06:9D:58:02:FE:73:A5:89:50:59:C4:8C:D9:
  • C0:74:DD:48:37:17:3F