SSL-Tools

SSL check results of mail.goldway.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.goldway.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 Sat, 21 Dec 2024 09:51:31 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.goldway.de
217.86.142.209
 -
supported
gwfw.goldway.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.goldway.de
217.7.211.209
 -
supported
gwfw.goldway.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=gwfw.goldway.de

Certificate chain
  • gwfw.goldway.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)
  • gwfw.goldway.de
Alternative Names
  • gwfw.goldway.de
  • mail.goldway.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-12-21
Not valid after
2025-03-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D8:5D:92:66:4D:2E:E7:C3:B4:C5:38:A8:38:50:12:58:80:EE:DF:43:D5:35:5C:3A:F1:87:76:4E:C8:AD:A2:73
SHA1
4C:28:3A:2A:02:71:13:A6:E8:8B:E5:F7:BE:0E:38:DD:53:8E:32:87
X509v3 extensions
subjectKeyIdentifier
  • 33:DB:C5:05:26:C9:FA:6D:92:63:D1:ED:38:62:B5:86:13:12:14:12
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Dec 21 09:12:54.224 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D8:5F:55:BE:CF:93:93:7A:57:21:FC:
  • CF:B8:FA:2A:0E:10:A0:5D:3E:A8:04:A7:76:AB:5A:D6:
  • 89:92:6B:43:5D:02:20:2F:3D:13:87:3E:4E:F3:09:E2:
  • 12:76:54:9E:D8:1A:17:89:19:82:87:27:6C:FB:7C:91:
  • 58:CE:3B:0B:43:4E:82
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Dec 21 09:12:54.258 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FE:D7:8C:33:D6:39:90:67:54:6F:44:
  • C4:16:34:18:3C:FD:C4:D8:57:4D:EF:46:E0:19:41:6C:
  • BB:84:5F:12:3B:02:21:00:CD:93:E3:5A:E5:01:5B:B8:
  • 09:FB:12:B6:C4:EB:88:CD:73:10:8C:54:51:74:94:2C:
  • 23:CB:89:44:0C:07:65:95