SSL-Tools

SSL check results of nachbaur.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for nachbaur.eu 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 Tue, 09 Feb 2021 15:53:05 +0000

The mailservers of nachbaur.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @nachbaur.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.nachbaur.eu
2a05:8b81:1000:ac::d5e3
 10
supported
mx1.nachbaur.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
12 s
mx1.nachbaur.eu
185.82.20.46
 10
supported
mx1.nachbaur.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
12 s

Outgoing Mails

We have received emails from these servers with @nachbaur.eu sender addresses. Test mail delivery

Host TLS Version & Cipher
unknown (IPv6:2a05:8b81:1000:ac::d5e3)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mx1.nachbaur.eu

Certificate chain
  • mx1.nachbaur.eu
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • mx1.nachbaur.eu
Alternative Names
  • mx1.nachbaur.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-09
Not valid after
2021-05-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
76:DE:C2:92:FA:25:E8:72:3D:50:0D:AF:E2:88:35:6A:D0:BD:5C:B0:43:83:D0:DC:75:48:68:23:E9:BD:63:1E
SHA1
EE:FB:51:52:A2:D7:14:64:B3:42:7E:D9:4D:FA:EC:25:38:7C:41:4C
X509v3 extensions
subjectKeyIdentifier
  • 28:59:11:61:96:23:BD:D4:9E:F3:AB:5F:ED:FE:E0:61:84:35:2D:A9
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Feb 9 13:49:35.683 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1E:6E:F0:91:DB:D7:5A:9E:E1:66:AD:DE:
  • BE:9A:CC:63:BB:40:1F:78:32:F4:DC:3D:E8:AE:8D:53:
  • C7:BE:F3:42:02:20:79:DF:36:7E:7F:D7:14:EF:6C:93:
  • BF:28:FF:76:32:5A:61:BC:02:2B:F3:06:5D:5A:EB:D1:
  • 49:F5:C4:F4:2C:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Feb 9 13:49:35.712 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:00:D1:53:88:61:79:46:D4:84:AC:24:DD:
  • 12:C1:6A:47:A1:6F:76:4E:C9:6F:76:99:82:7E:70:2F:
  • 79:2A:AD:79:02:21:00:F7:14:65:F9:03:FD:F2:2C:3B:
  • C0:99:3C:EA:9A:C2:C9:20:62:B1:59:FD:A3:46:0C:F2:
  • C2:19:64:76:A1:CE:B6