SSL-Tools

SSL check results of tech-nord.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for tech-nord.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 Wed, 31 Jul 2024 02:49:23 +0000

We can not guarantee a secure connection to the mailservers of tech-nord.ru!

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

/mailservers/tech-nord.ru

Servers

Incoming Mails

These servers are responsible for incoming mails to @tech-nord.ru addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tech-nord.ru
2a0a:2b42:0:2e::
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.tech-nord.ru
141.8.192.207
 10
supported
from.sh
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=from.sh

Certificate chain
  • from.sh
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • from.sh
Alternative Names
  • *.from.sh
  • from.sh
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-06-15
Not valid after
2024-09-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8C:36:6F:96:08:75:FF:0E:F4:72:F2:8F:D8:E8:D1:6B:27:09:70:45:1E:45:02:FF:1B:E2:67:CB:0F:23:0C:25
SHA1
89:FF:E3:37:87:B7:BA:4A:2A:F8:D1:B2:10:4B:A7:CB:0A:6C:D7:FD
X509v3 extensions
subjectKeyIdentifier
  • 4E:9B:98:04:67:EC:29:F0:8B:6A:E0:4A:CB:AB:18:C4:1C:84:49:E8
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.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 : Jun 15 22:08:19.852 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:17:D5:58:9A:A7:02:D4:0A:8D:E8:27:2C:
  • 5B:35:EC:FB:09:B0:26:51:8E:A8:11:19:0C:C7:87:49:
  • 08:5A:39:AA:02:20:16:C8:5B:D7:C6:E4:34:B8:00:6D:
  • 4B:22:9F:94:45:F0:5B:57:DB:BD:0B:3E:B4:EE:C1:98:
  • 95:20:F6:CB:85:47
  • 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 : Jun 15 22:08:19.845 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4C:D6:3C:3F:74:6F:CC:53:D1:B2:1A:E8:
  • E0:58:18:CB:29:8F:4D:83:C0:25:DB:01:8B:8F:7F:D2:
  • F9:22:FA:B6:02:20:7D:F9:BE:F2:11:2B:CA:A7:F6:5C:
  • E1:6B:F5:9D:48:6A:04:92:4B:4F:B0:13:D4:35:BF:71:
  • BF:C8:0C:E6:17:49