SSL-Tools

SSL check results of xamdan.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for xamdan.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 Sun, 09 Aug 2026 00:30:52 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.xamdan.ru
89.188.118.47
 10
supported
mail.xamdan.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mail.xamdan.ru
89.188.118.47
 20
supported
mail.xamdan.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 @xamdan.ru address so far. Test mail delivery

Certificates

First seen at:

CN=mail.xamdan.ru

Certificate chain
  • mail.xamdan.ru
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.xamdan.ru
Alternative Names
  • mail.xamdan.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-08-03
Not valid after
2026-11-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
9F:0A:E9:DD:AE:D0:29:BA:39:0F:BD:EC:39:CD:42:D5:0B:5C:D5:F4:D7:4A:F9:A7:72:7F:CA:33:5A:93:1D:DD
SHA1
58:6F:80:A5:FF:D8:17:69:A6:2B:C4:7F:86:C1:93:41:EF:31:1A:CB
X509v3 extensions
subjectKeyIdentifier
  • 97:CC:32:A0:69:BF:64:53:8C:6A:1F:FC:45:BB:47:F6:21:B8:35:4A
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/42.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : C2:31:7E:57:45:19:A3:45:EE:7F:38:DE:B2:90:41:EB:
  • C7:C2:21:5A:22:BF:7F:D5:B5:AD:76:9A:D9:0E:52:CD
  • Timestamp : Aug 3 07:51:45.648 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:19:82:5E:0A:71:80:09:56:E0:8A:6F:EB:
  • 0A:5A:F7:81:C0:02:EA:A8:74:A9:C2:F1:F6:58:D1:A0:
  • 57:E0:B0:B2:02:21:00:85:E6:0B:32:11:FA:FA:2D:AB:
  • 71:1C:9F:2F:22:94:0B:B1:EB:D5:9F:58:55:57:D4:DC:
  • 99:0A:48:AD:D1:2F:55
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:AF:86:3D:3B:3E:E5:9F:A5:77:DE:A8:24:5D:36:B0:
  • D9:ED:22:A2:23:F4:61:77:41:22:94:52:EE:95:50:5F
  • Timestamp : Aug 3 07:51:45.756 2026 GMT
  • Extensions: 00:00:05:00:0F:9C:B9:58
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:53:0F:28:49:96:C2:83:05:2C:11:C5:09:
  • DC:41:86:A8:51:34:31:B5:4F:E0:DC:47:8C:CC:05:E4:
  • 52:19:6D:FF:02:21:00:8D:CC:AB:DE:83:72:AD:E8:00:
  • EE:4D:63:D1:CA:8E:88:0A:87:A4:93:96:E8:21:46:6B:
  • C3:77:47:1A:A3:FC:8B