SSL check results of yaltanet.ru

NEW You can also bulk check multiple servers.

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

Report created Thu, 28 May 2020 00:31:32 +0000

The mailservers of yaltanet.ru can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @yaltanet.ru addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.yaltanet.ru
91.205.164.60
10
supported
mail.yaltanet.ru
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
15 s
mail.yaltanet.ru
91.205.164.36
10
supported
mail.yaltanet.ru
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
15 s

Outgoing Mails

We have received emails from these servers with @yaltanet.ru sender addresses. Test mail delivery

Host TLS Version & Cipher
unknown (178.212.64.52)
Insecure - not encrypted!

Certificates

First seen at:

CN=mail.yaltanet.ru

Certificate chain
  • mail.yaltanet.ru
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Unknown Authority

      Let's Encrypt Authority X3
Subject
Common Name (CN)
  • mail.yaltanet.ru
Alternative Names
  • mail.yaltanet.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-08
Not valid after
2020-08-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F5:A4:C1:7B:49:A3:FC:31:80:AA:87:1B:D8:63:DE:F3:1B:86:13:A2:CB:DB:B7:AF:CD:CD:12:F5:59:16:1E:F6
SHA1
B4:2A:7B:E0:2A:4C:46:59:BD:FC:D0:98:46:CD:66:DD:5A:AC:21:3D
X509v3 extensions
subjectKeyIdentifier
  • 61:7F:55:73:AE:F7:A1:A4:47:72:7A:67:EF:80:29:C8:86:DB:90:85
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E7:12:F2:B0:37:7E:1A:62:FB:8E:C9:0C:61:84:F1:EA:
  • 7B:37:CB:56:1D:11:26:5B:F3:E0:F3:4B:F2:41:54:6E
  • Timestamp : May 9 00:36:25.319 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:08:79:87:35:F4:FB:3C:16:CA:11:68:D5:
  • EE:7A:95:D8:C2:93:94:29:FB:38:CE:43:23:C2:20:F0:
  • 48:29:F9:FD:02:20:6E:3C:14:DE:91:B4:1C:62:75:E1:
  • 46:97:29:08:21:E5:9C:69:1F:4B:E0:02:20:A6:A6:58:
  • 33:13:05:70:68:B5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : May 9 00:36:25.303 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:86:2A:89:52:97:62:0A:D0:FD:F0:72:
  • 1F:AA:06:E2:FE:35:5B:2B:8B:5F:C0:93:E8:C6:25:DD:
  • 29:65:B2:02:90:02:20:1A:BC:96:7B:3A:05:2E:35:A8:
  • 43:72:3B:AE:FD:DE:1D:C1:87:51:A1:65:33:BF:DE:65:
  • 46:AA:0A:99:19:7C:95