SSL-Tools

SSL check results of mail.svetservis.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.svetservis.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 Thu, 25 Apr 2024 06:50:37 +0000

We can not guarantee a secure connection to the mailservers of mail.svetservis.ru!

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

/mailservers/mail.svetservis.ru

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.svetservis.ru
141.0.179.205
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.svetservis.ru
85.113.49.79
 -
supported
smtp.svetservis.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_ECDSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=smtp.svetservis.ru

Certificate chain
  • smtp.svetservis.ru
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • smtp.svetservis.ru
Alternative Names
  • smtp.svetservis.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-25
Not valid after
2024-07-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F1:5C:58:BB:D6:FE:3C:D2:A6:71:3F:9D:63:25:A1:F1:C4:FD:04:E9:93:E8:62:2C:72:A1:B5:6E:1F:5F:E0:D0
SHA1
10:FE:6D:CD:DF:85:10:78:F7:A4:DB:4F:F6:76:2F:24:E0:71:3F:76
X509v3 extensions
subjectKeyIdentifier
  • ED:2A:5B:94:B0:4B:C6:B8:75:CD:2B:B4:56:EE:BA:18:9F:95:07:1D
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 : 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 : Apr 25 06:44:45.952 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BB:15:0E:23:EE:16:0E:98:08:C9:E8:
  • 7A:F4:16:E6:52:4D:DA:2F:0B:4F:E2:D2:88:EA:64:49:
  • 84:6D:5E:B2:FA:02:21:00:90:FD:95:26:7C:B4:DE:BA:
  • 76:E0:C3:2C:D0:5B:7C:34:97:DC:7A:66:AE:E2:04:CD:
  • 95:AD:44:AC:B8:E4:BD:3A
  • 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 : Apr 25 06:44:45.948 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:96:4A:CA:25:73:4D:BB:F0:18:C2:B5:
  • 20:02:F4:80:4A:BC:C8:E4:47:DF:ED:6C:2D:C2:1A:65:
  • 33:C0:78:87:4A:02:21:00:E3:E5:8D:E5:20:21:5B:8E:
  • BB:08:E5:1B:D6:27:D0:8F:21:34:32:4E:5C:18:D0:D7:
  • 79:6A:A5:F0:53:89:09:D9