SSL check results of mail.heinz.bz

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.heinz.bz 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

Report created Sat, 09 Mar 2024 14:25:56 +0000

The mailservers of mail.heinz.bz can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.heinz.bz addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.heinz.bz
188.68.51.141
-
supported
mail.heinz.bz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s
mail.heinz.bz
2a03:4000:6:d0a8:88fd:62ff:fe7a:3d6d
-
supported
mail.heinz.bz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.heinz.bz

Certificate chain
  • mail.heinz.bz
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.heinz.bz
Alternative Names
  • mail.heinz.bz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-28
Not valid after
2024-05-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
44:1A:02:80:D1:39:46:4D:F1:6B:21:A3:07:B5:A4:00:F0:BD:E8:9A:D4:6B:2D:5D:7A:D2:D4:D5:D1:F9:9E:C8
SHA1
11:69:37:BA:2E:CF:0E:DB:A6:68:B1:CA:AC:6B:B9:46:77:82:C9:8D
X509v3 extensions
subjectKeyIdentifier
  • E8:6C:ED:78:78:7C:9D:0D:C8:E0:49:B7:B6:83:2E:09:17:47:8E:9F
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Feb 28 05:33:52.067 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D8:C8:8D:C9:F7:A5:8B:E9:BA:FD:68:
  • 1A:E3:43:8E:57:8F:82:5C:25:03:28:01:37:9B:26:BB:
  • 9F:C6:7D:01:71:02:21:00:EC:64:03:3A:D5:D6:FC:25:
  • BB:E6:1C:57:D1:1A:82:F2:D2:D8:C1:32:A1:FA:49:EA:
  • 45:C6:B2:88:AB:02:82:C7
  • 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 28 05:33:52.573 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B5:06:5F:79:54:7C:A1:D9:F7:9E:5D:
  • 2D:44:F7:8D:69:9A:29:45:3F:2F:EE:B9:C1:4B:C5:02:
  • B1:60:2A:03:6E:02:20:53:F2:7C:3C:C3:A0:11:AB:D1:
  • 0D:79:17:5E:B6:31:6E:1E:49:A0:F6:0D:D2:75:C1:12:
  • 96:7D:4C:4B:A1:65:4B