SSL-Tools

SSL check results of avemail.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for avemail.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 Tue, 05 Nov 2024 10:43:44 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
avemail.ru
95.165.134.131
 10
supported
avemail.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
avemail.ru
84.23.33.194
Results incomplete
10
supported
not checked
DANE
missing
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
17 s
mail.avemail.ru
95.165.134.131
 20
supported
avemail.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s

Outgoing Mails

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

Certificates

First seen at:

CN=avemail.ru

Certificate chain
  • avemail.ru
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • avemail.ru
Alternative Names
  • avemail.ru
  • cloud.avemail.ru
  • mail.avemail.ru
  • www.avemail.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-27
Not valid after
2024-12-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9B:FC:2D:AC:7B:F2:44:59:E0:C0:B2:AF:34:BF:FB:3F:1C:50:65:4C:0B:37:37:2B:8E:81:FE:62:06:15:85:0D
SHA1
57:51:17:F1:18:1F:CE:1B:8F:5C:D1:69:D0:12:B2:94:51:FF:A1:C3
X509v3 extensions
subjectKeyIdentifier
  • F8:05:D4:23:89:E5:D5:1C:72:6B:F3:15:61:A1:DF:B3:49:88:33:01
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 : Sep 27 06:33:32.534 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D4:B7:B5:1F:F6:CF:FA:24:F7:9E:32:
  • C6:F4:FD:4B:55:F2:06:29:AA:47:A5:00:8B:2C:AD:52:
  • 1F:3A:B6:22:FE:02:21:00:F9:4A:F0:10:74:D7:85:2E:
  • FD:0C:31:D5:40:C6:01:BB:34:25:C2:FF:15:DC:64:86:
  • DD:44:42:D5:25:9B:09:57
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Sep 27 06:33:32.571 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:99:7B:BE:F5:55:87:E9:2B:F4:17:62:
  • 2B:AE:3C:AE:A9:48:07:7C:C8:22:71:C7:66:33:F6:42:
  • 86:38:1B:93:24:02:21:00:D0:0F:D1:7B:FF:3A:46:E0:
  • 3C:6A:24:29:69:BC:DA:6F:51:1D:20:A8:56:F3:CA:9A:
  • BB:0A:D6:AC:4B:87:FF:CC