SSL check results of skyadler.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for skyadler.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 Sun, 01 Aug 2021 04:35:38 +0000

The mailservers of skyadler.ru can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
skyadler.ru
62.182.141.188
10
supported
skyadler.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
skyadler.ru
62.182.139.55
10
supported
skyadler.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

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

Host TLS Version & Cipher
skyadler.ru (62.182.141.188)
TLSv1.3 TLS_AES_256_GCM_SHA384
skyadler.ru (62.182.139.55)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=skyadler.ru

Certificate chain
  • skyadler.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)
  • skyadler.ru
Alternative Names
  • skyadler.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-07-18
Not valid after
2021-10-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C7:F9:79:5F:35:28:EF:72:CA:7A:44:81:41:C8:BB:12:92:A6:82:6E:93:47:1B:18:1B:C1:34:9C:0D:D1:7A:62
SHA1
C6:15:EE:55:75:CE:9E:1F:BA:9A:37:A8:2A:10:75:D2:B4:FF:23:01
X509v3 extensions
subjectKeyIdentifier
  • C5:88:2B:70:7B:EB:C1:B7:56:4C:DC:BD:B7:14:1B:B3:CF:47:28:A9
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
  • 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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Jul 18 19:45:19.199 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3B:A1:42:6A:0F:C1:B3:D8:C2:54:20:38:
  • D3:C3:5E:85:60:8E:C3:AE:D9:D5:9D:AC:88:23:C8:7F:
  • 03:6D:F3:33:02:21:00:B0:D8:F0:27:99:5E:E5:3F:A2:
  • 36:8E:7C:C1:A1:D1:DE:C1:49:50:C7:DD:0F:89:7D:F7:
  • 47:22:A1:EB:EB:11:34
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Jul 18 19:45:19.183 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:71:60:55:04:95:22:B1:E3:22:48:D5:F7:
  • 85:C0:4E:3C:EA:71:43:F4:9F:EE:CD:6B:51:C5:B9:84:
  • E9:99:84:D8:02:20:51:C0:AF:9F:12:B1:23:D7:7F:76:
  • D3:54:A4:13:C3:10:4B:83:45:7F:0C:31:BB:CE:15:E6:
  • 59:29:12:34:DF:E3