SSL-Tools

SSL check results of qdp.kz

NEW You can also bulk check multiple servers.

Discover if the mail servers for qdp.kz 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, 23 Apr 2024 05:45:44 +0000

The mailservers of qdp.kz can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @qdp.kz addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.qdp.kz
79.142.55.116
 10
supported
mail.forwarder.kz
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 @qdp.kz address so far. Test mail delivery

Certificates

First seen at:

CN=mail.forwarder.kz

Certificate chain
  • mail.forwarder.kz
    • 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.forwarder.kz
Alternative Names
  • mail.cls-international.com
  • mail.forwarder.kz
  • mail.icac.com.kz
  • mail.logisticsolutions.ru
  • mail.qazmarine.kz
  • mail.qcp.kz
  • mail.qdp.kz
  • mail.uzlogistic.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-08
Not valid after
2024-06-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
25:D9:9B:1C:81:1F:09:B7:B5:C0:99:E2:C2:18:57:88:0D:51:CF:65:27:1B:FD:D5:0D:9C:2A:B8:4C:73:BC:5E
SHA1
E3:DE:B6:A1:7A:54:2E:99:A4:83:75:A9:55:63:8D:D0:49:04:71:66
X509v3 extensions
subjectKeyIdentifier
  • 6B:0B:79:09:49:18:34:28:64:2F:7D:71:F2:58:5B:0C:9B:57:84:C5
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 : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 8 19:01:24.585 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:07:32:ED:B5:86:EF:21:69:6E:1A:5C:1B:
  • 85:89:38:80:99:35:96:8D:71:1C:97:DC:2B:4B:74:C1:
  • 5D:B0:30:98:02:20:22:1A:7E:C5:5B:53:FB:3B:64:AE:
  • 71:E1:CD:F0:9D:99:B2:28:B0:52:32:E0:67:5D:11:CB:
  • 12:09:05:74:B0:E5
  • 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 : Mar 8 19:01:25.079 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D7:A3:25:0F:16:BD:8C:1D:AF:E8:9F:
  • 57:E3:E7:38:B9:DC:04:15:4D:71:FF:58:76:6D:CD:99:
  • 39:A3:9B:43:E7:02:20:61:2C:3D:1B:F4:8E:58:DF:1B:
  • 74:DA:06:34:26:73:75:7F:D3:16:D3:D1:2E:56:36:C7:
  • 66:88:F6:11:5D:5F:CC