SSL-Tools

SSL check results of bnyarcher.zendesk.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for bnyarcher.zendesk.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

JSON Refresh

Report created Tue, 15 Jul 2025 15:12:55 +0000

The mailservers of bnyarcher.zendesk.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @bnyarcher.zendesk.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail-pod-19.int.zendesk.com
54.204.201.169
 10
supported
zendesk.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s
mail-pod-19.int.zendesk.com
3.234.90.190
 10
supported
zendesk.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s
mail-pod-19.int.zendesk.com
52.204.79.27
 10
supported
zendesk.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=zendesk.com

Certificate chain
  • zendesk.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • zendesk.com
Alternative Names
  • *.int.zendesk.com
  • *.zendesk.com
  • zendesk.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-06-18
Not valid after
2025-09-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C9:78:46:9B:A6:9A:B0:7F:F0:DB:00:33:DA:10:FB:EC:07:17:AF:75:B3:78:2F:FA:6E:57:BA:7E:E9:5A:58:37
SHA1
DE:C4:D8:34:36:14:90:7C:30:2A:AB:9C:1F:C2:48:20:D4:2D:C2:7C
X509v3 extensions
subjectKeyIdentifier
  • BC:2B:66:88:B8:1E:26:14:83:13:27:42:BE:FB:F1:9A:3A:E3:03:CA
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e5.c.lencr.org/18.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Jun 18 13:39:54.261 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:61:20:0C:34:2A:B0:8B:65:D2:39:76:59:
  • 97:63:21:4C:DE:5C:E7:9B:1F:74:53:28:66:75:B4:B5:
  • 55:43:72:85:02:21:00:B4:C2:77:E4:D2:AD:22:C7:75:
  • 76:B8:35:BA:BE:13:66:04:F4:7A:B6:A0:2D:CD:81:30:
  • 64:95:83:EC:A7:BB:A8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Jun 18 13:39:54.315 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:75:80:2C:4D:FD:74:D7:83:C4:76:03:3D:
  • D5:A7:9E:51:3B:8C:77:7E:74:70:F5:75:54:FB:11:E8:
  • 1E:26:38:E7:02:20:78:4A:F4:67:98:60:01:DF:C3:7F:
  • AF:11:D4:B3:90:02:D7:83:9D:05:43:3C:23:79:F9:42:
  • CE:8A:D6:C3:A2:6B