SSL-Tools

SSL check results of smartgoods.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for smartgoods.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 Wed, 24 Apr 2024 07:29:51 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail2.ecom-dresden.de
2a01:4f8:c010:a53::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail2.ecom-dresden.de
159.69.122.85
 10
supported
mail2.ecom-dresden.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail2.ecom-dresden.de

Certificate chain
  • mail2.ecom-dresden.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail2.ecom-dresden.de
Alternative Names
  • mail2.ecom-dresden.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-26
Not valid after
2024-05-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BF:F5:50:8E:2D:CD:27:2B:E6:71:96:26:12:C2:86:56:1E:6E:8F:C0:C0:1F:34:CD:91:FB:83:BB:84:20:14:8F
SHA1
35:EC:8E:C3:50:A9:F0:9C:B9:8D:8F:BF:AE:F5:8F:67:F1:6D:A3:13
X509v3 extensions
subjectKeyIdentifier
  • 82:DF:B2:9D:74:95:13:6A:41:09:75:B7:2A:BF:C6:30:9E:FC:5A:A7
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Feb 26 07:47:16.797 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:58:01:58:87:95:88:61:2C:48:8B:3B:58:
  • 19:F5:46:2F:A2:CC:49:24:3C:E6:83:74:BF:D4:47:2F:
  • 92:C4:85:0B:02:20:01:2F:D7:F2:49:FE:C6:6E:C9:C5:
  • A1:D8:9F:B5:57:14:10:6A:F1:DE:9E:1A:AD:04:A3:13:
  • 11:E2:E1:DD:DD:D5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Feb 26 07:47:16.810 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:36:EA:F2:B8:28:5C:E2:7B:E7:79:49:B3:
  • 90:E1:EE:08:6F:84:09:70:06:E5:DF:21:ED:BD:29:DA:
  • AF:B1:4F:FA:02:20:01:D5:A8:45:21:98:A1:65:8F:D5:
  • 91:9D:59:A0:60:E1:14:C2:7A:6E:B1:3B:F1:79:C4:2B:
  • E7:7F:89:2F:31:3D