SSL-Tools

SSL check results of denx.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for denx.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 Fri, 16 Apr 2021 07:50:34 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
phobos.denx.de
2a01:238:438b:c500:173d:9f52:ddab:ee01
 50
supported
phobos.denx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
phobos.denx.de
85.214.62.61
 50
supported
phobos.denx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=phobos.denx.de

Certificate chain
  • phobos.denx.de
    • 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)
  • phobos.denx.de
Alternative Names
  • lists.denx.biz
  • lists.denx.de
  • mail.denx.biz
  • mail.denx.de
  • phobos.denx.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-01
Not valid after
2021-05-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5F:08:97:C7:A0:84:A9:99:A9:1D:3D:E1:57:8E:A9:72:1C:6A:9F:DE:5B:1D:54:1F:2B:A1:45:AC:07:9E:57:22
SHA1
8B:AD:5C:20:EC:34:75:11:7A:2F:E8:8C:10:20:FB:F2:20:90:14:91
X509v3 extensions
subjectKeyIdentifier
  • 10:7D:F0:65:94:75:BE:F3:96:0E:28:4F:ED:6E:B3:10:00:72:A8:B7
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Mar 1 20:00:04.486 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E5:FC:82:70:6E:5B:D8:12:F5:61:59:
  • 1B:36:7D:22:0B:04:9F:D0:21:4D:4C:2E:68:D8:EE:31:
  • F3:60:8C:A8:6B:02:21:00:B7:70:E4:DE:A6:A4:30:5A:
  • A8:97:E7:D9:BF:5E:D9:03:A6:8A:1F:31:E1:B7:AF:B1:
  • DB:5E:C7:37:CE:62:1D:F5
  • 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 : Mar 1 20:00:04.523 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FF:8B:7B:E5:43:08:E3:44:04:72:0E:
  • DE:D9:D1:3F:02:73:B2:A3:C8:9E:8A:36:5C:B3:44:C5:
  • A5:09:5B:07:53:02:20:50:58:71:05:3E:24:E2:04:0D:
  • A3:A2:2A:02:2D:AF:3D:B8:21:28:CF:9C:0F:08:EE:04:
  • 77:16:8B:83:A2:1E:79