SSL-Tools

SSL check results of quant-c.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for quant-c.ru 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 Mon, 22 Apr 2024 08:04:31 +0000

We can not guarantee a secure connection to the mailservers of quant-c.ru!

Please contact the operator of quant-c.ru and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/quant-c.ru

Servers

Incoming Mails

These servers are responsible for incoming mails to @quant-c.ru addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.quant-c.ru
2001:470:1f15:17b9::25
Results incomplete
5
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
mx.quant-c.ru
80.255.88.146
 5
supported
mx.quant-c.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

We have not received any emails from a @quant-c.ru address so far. Test mail delivery

Certificates

First seen at:

CN=mx.quant-c.ru

Certificate chain
  • mx.quant-c.ru
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx.quant-c.ru
Alternative Names
  • mx.quant-c.ru
  • smtp.quant-c.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-12
Not valid after
2024-07-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5C:66:2B:5E:9D:B7:84:68:5D:7C:65:F0:DE:3A:32:C8:21:1A:5C:78:F8:B2:4B:17:00:63:1B:4D:C4:79:73:2C
SHA1
5E:89:AA:9E:06:10:48:F3:0A:58:09:30:37:A0:94:AD:04:82:F5:4C
X509v3 extensions
subjectKeyIdentifier
  • DD:5D:D6:32:FA:47:8E:2E:27:86:B0:6D:8E:0C:CA:5B:71:69:2C:01
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 12 10:53:21.841 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5A:82:CF:78:73:00:32:B8:44:8C:7B:5F:
  • 99:D5:1E:35:3B:61:6C:D5:CE:D7:C1:BF:4A:15:89:A8:
  • 61:14:09:91:02:21:00:D9:DD:EB:59:B3:0D:28:DB:8B:
  • 00:F8:60:7B:6E:73:65:B5:1E:20:1B:D0:B1:B7:98:41:
  • 41:7F:2A:00:DF:95:DD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 12 10:53:21.929 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:28:84:E7:76:65:E7:FE:DB:3C:9F:2A:7F:
  • 01:40:55:60:DF:DB:C1:51:EE:55:C0:75:B4:04:50:71:
  • 42:17:CD:88:02:21:00:B0:6B:90:69:34:44:E0:EC:B2:
  • 26:C2:6A:7E:28:E1:6D:BB:27:B6:95:0C:FD:04:B2:CE:
  • 5E:AB:C8:53:D0:1C:2D