SSL-Tools

SSL check results of huelsing-cloud.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for huelsing-cloud.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 Thu, 31 Oct 2024 07:40:29 +0000

The mailservers of huelsing-cloud.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @huelsing-cloud.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.huelsing-cloud.de
2a01:4f8:1c17:6dd7::1
 10
supported
mail.huelsing-cloud.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.huelsing-cloud.de
128.140.81.124
 10
supported
mail.huelsing-cloud.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 @huelsing-cloud.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.huelsing-cloud.de

Certificate chain
  • mail.huelsing-cloud.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.huelsing-cloud.de
Alternative Names
  • autoconfig.huelsing-cloud.de
  • autodiscover.huelsing-cloud.de
  • mail.huelsing-cloud.de
  • mta-sts.huelsing-cloud.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-10
Not valid after
2024-12-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4D:C2:E7:4B:8D:8D:75:B0:7D:55:26:1A:D1:7F:CB:84:30:06:1B:58:14:47:94:96:20:28:0F:74:78:2F:CB:24
SHA1
21:A9:7A:4D:F9:38:A0:16:D0:DF:72:49:80:C0:9F:6F:DF:6C:30:0F
X509v3 extensions
subjectKeyIdentifier
  • 60:FC:D5:9C:80:A8:84:3B:90:3F:BD:3D:DD:C8:15:07:5A:BE:ED:90
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 10 05:45:33.912 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7A:51:28:3A:5C:FB:09:CA:51:C0:59:DA:
  • 90:F0:E1:44:D0:6C:37:04:23:0C:9A:90:66:65:7B:E5:
  • E1:6B:76:59:02:20:58:3E:EA:70:96:DA:53:09:4D:C2:
  • D2:3C:31:09:A0:37:79:1E:DB:1B:07:A1:93:74:3C:2D:
  • 1C:96:D5:A3:20:71
  • 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 : Sep 10 05:45:33.904 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2D:43:97:2E:CD:22:00:F0:05:DE:6F:CB:
  • 4F:02:37:00:28:12:67:7A:21:0A:A7:EE:7D:E4:3C:AB:
  • 04:DD:2E:F2:02:21:00:DF:47:28:0C:F6:C9:5E:36:C1:
  • 58:E6:36:A4:38:23:1C:4E:AE:36:58:34:14:5C:6C:22:
  • 84:A2:3A:A0:0A:3F:75