SSL-Tools

SSL check results of mailarchiv.goldrichtig-personal.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mailarchiv.goldrichtig-personal.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, 19 May 2025 00:31:44 +0000

The mailservers of mailarchiv.goldrichtig-personal.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mailarchiv.goldrichtig-personal.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mailarchiv.goldrichtig-personal.de
185.210.103.14
 -
supported
mailarchiv.goldrichtig-personal.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

We have not received any emails from a @mailarchiv.goldrichtig-personal.de address so far. Test mail delivery

Certificates

First seen at:

CN=mailarchiv.goldrichtig-personal.de

Certificate chain
  • mailarchiv.goldrichtig-personal.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)
  • mailarchiv.goldrichtig-personal.de
Alternative Names
  • mailarchiv.goldrichtig-personal.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-05-11
Not valid after
2025-08-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
94:1B:ED:96:7C:51:8F:E7:03:EE:4F:1C:14:E7:D2:53:92:72:62:A0:67:67:A0:58:8C:3B:EE:5B:84:75:54:A5
SHA1
7F:3F:E2:80:77:F7:02:A6:7B:5C:98:26:1E:05:9C:23:46:F2:51:7F
X509v3 extensions
subjectKeyIdentifier
  • 77:2F:61:F9:3E:51:F2:83:20:51:E9:98:79:9D:76:05:0B:0F:2B:ED
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/75.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : May 11 01:31:23.730 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:75:68:C3:E8:EA:ED:37:A5:A4:78:E4:28:
  • 62:A4:52:E6:9E:78:14:16:80:B1:59:73:26:FE:5C:D1:
  • 7E:57:70:7A:02:20:11:11:0E:BF:F3:90:DD:A8:4D:3C:
  • 98:2B:9C:5B:75:A2:21:13:0B:FD:C9:86:C4:B8:55:D1:
  • 95:B7:C8:60:27:D5
  • 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 : May 11 01:31:23.874 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EE:77:F6:F2:B3:AE:73:9F:E4:6D:D4:
  • AF:F4:86:23:7A:E5:14:43:BB:65:C5:2D:4D:38:F8:3C:
  • 93:98:07:D4:05:02:21:00:D9:A5:00:A2:45:94:7B:37:
  • 8E:F6:A3:ED:05:A5:E1:8B:7D:99:E2:16:98:DC:E8:C1:
  • AF:81:2F:52:DA:E8:6C:F1