SSL-Tools

SSL check results of grost16.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for grost16.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 Fri, 21 Nov 2025 01:31:20 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mmxs.majordomo.ru
78.108.80.147
 10
supported
majordomo.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mmxs.majordomo.ru
78.108.80.149
 10
supported
majordomo.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=majordomo.ru

Certificate chain
  • majordomo.ru
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R13
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • majordomo.ru
Alternative Names
  • *.majordomo.ru
  • majordomo.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R13
validity period
Not valid before
2025-10-17
Not valid after
2026-01-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3B:3F:F3:A6:CB:27:B6:F5:75:5E:81:A8:77:4C:8C:4B:6C:E9:7A:20:22:C8:BC:9E:88:EF:83:49:AE:D0:C6:1C
SHA1
DA:D5:F8:51:F3:BD:10:A6:EC:2C:3F:E3:AB:9B:E8:EF:51:3D:C0:27
X509v3 extensions
subjectKeyIdentifier
  • E9:91:A7:EA:90:A9:C2:3E:EE:A8:F5:C8:D9:56:91:4F:31:A1:84:7F
authorityKeyIdentifier
  • keyid:E7:AB:9F:0F:2C:33:A0:53:D3:5E:4F:78:C8:B2:84:0E:3B:D6:92:33
authorityInfoAccess
  • CA Issuers - URI:http://r13.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r13.c.lencr.org/127.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 64:11:C4:6C:A4:12:EC:A7:89:1C:A2:02:2E:00:BC:AB:
  • 4F:28:07:D4:1E:35:27:AB:EA:FE:D5:03:C9:7D:CD:F0
  • Timestamp : Oct 17 09:05:08.556 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:20:E7:C8:36:7A:91:55:1C:D4:09:B6:96:
  • F0:D8:0A:CD:99:1E:28:6B:78:39:C9:01:8E:EE:97:DF:
  • 3D:44:5D:29:02:21:00:DC:2B:FB:62:3D:8F:2B:A7:67:
  • 38:37:57:F8:AD:64:FC:9D:ED:E2:7A:30:60:51:B6:B5:
  • B2:7D:4A:0A:0E:72:BE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CB:38:F7:15:89:7C:84:A1:44:5F:5B:C1:DD:FB:C9:6E:
  • F2:9A:59:CD:47:0A:69:05:85:B0:CB:14:C3:14:58:E7
  • Timestamp : Oct 17 09:05:08.572 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:19:5B:FF:F5:9C:47:44:37:AB:BE:A2:93:
  • 3E:37:7A:13:45:63:C5:FA:30:6A:D5:A9:12:74:99:A9:
  • 88:38:7E:71:02:21:00:BC:52:DA:44:84:42:42:D3:86:
  • 2F:E2:77:B3:00:EB:BE:FF:9E:0D:B2:BE:E3:07:16:FC:
  • 08:0D:34:7E:26:27:C9