SSL check results of connect.newzi.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for connect.newzi.com 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 Fri, 19 Apr 2024 18:36:06 +0000

The mailservers of connect.newzi.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @connect.newzi.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
connect.newzi.com
172.105.96.69
0
supported
connect.newzi.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @connect.newzi.com address so far. Test mail delivery

Certificates

First seen at:

CN=connect.newzi.com

Certificate chain
  • connect.newzi.com
    • remaining
    • 256 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • connect.newzi.com
Alternative Names
  • connect.newzi.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-16
Not valid after
2024-07-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
57:60:DF:78:54:B9:AC:88:90:21:CA:B5:56:C9:58:28:10:70:06:83:10:8F:C6:76:DC:E9:16:E3:C2:C3:44:76
SHA1
17:AB:3A:2B:65:2E:EE:EE:8A:4A:34:28:0A:CC:DC:95:69:51:99:B5
X509v3 extensions
subjectKeyIdentifier
  • 2D:40:9C:82:D7:DF:CC:71:B4:66:FA:37:9D:E1:23:12:51:52:06:BB
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 : Apr 16 20:57:29.774 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8C:67:27:CA:7E:0C:88:86:E8:A9:25:
  • 9A:8D:D3:CC:11:C7:03:77:E8:13:02:2E:76:6A:26:75:
  • 26:8F:98:BD:E7:02:21:00:AD:5C:29:ED:97:39:E7:EF:
  • 9F:D2:AF:4E:60:72:55:3E:31:B9:21:6F:2D:C7:EB:4E:
  • 17:28:94:2D:06:D7:25:7A
  • 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 : Apr 16 20:57:29.785 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F1:5B:BB:29:25:04:72:78:EF:42:57:
  • B3:EF:6C:6A:05:BF:9F:92:B3:79:BE:D4:38:7F:7E:BB:
  • A8:40:B6:40:2C:02:21:00:8C:21:1A:D5:EC:BC:A5:70:
  • 37:41:B0:6E:2C:69:B3:8D:BB:F0:CF:8C:19:7B:78:D5:
  • 06:E8:74:66:5D:A3:D5:E0