SSL check results of emx.gbmsefmba.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for emx.gbmsefmba.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 Fri, 17 Jan 2025 01:31:21 +0000

We can not guarantee a secure connection to the mailservers of emx.gbmsefmba.ru!

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

/mailservers/emx.gbmsefmba.ru

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
emx.gbmsefmba.ru
194.50.24.236
Results incomplete
-
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
21 s
emx.gbmsefmba.ru
62.117.121.122
-
supported
*.gbmsefmba.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
4 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.gbmsefmba.ru

Certificate chain
  • *.gbmsefmba.ru
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Unknown Authority

      R10
Subject
Common Name (CN)
  • *.gbmsefmba.ru
Alternative Names
  • *.gbmsefmba.ru
  • *.msk.gbmsefmba.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-12-19
Not valid after
2025-03-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8B:4F:28:EC:F9:36:E1:F3:E8:1B:EE:DE:E5:C8:91:8E:E7:EF:DB:B4:F5:36:DC:10:DD:D1:F6:9A:6C:37:BD:4C
SHA1
EC:4C:29:C9:F5:06:D9:10:BE:03:53:C4:6C:86:BB:6A:30:A7:41:03
X509v3 extensions
subjectKeyIdentifier
  • 86:9C:BB:64:6B:4E:0C:EC:C2:10:B0:EE:1D:43:23:38:94:2C:A8:ED
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Dec 19 09:40:39.192 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:31:52:54:BE:52:AE:F9:0B:BC:E5:11:4C:
  • D8:86:D7:F2:FA:EA:D1:EC:8B:C2:54:41:97:29:D1:53:
  • 32:B5:7A:1D:02:21:00:8C:42:D9:03:5F:F3:DC:7E:33:
  • A4:ED:A8:BD:83:CE:3B:9E:6E:F0:CC:78:2F:73:C9:A9:
  • C3:56:AF:FC:FD:5B:CD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Dec 19 09:40:39.248 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C9:F3:F8:85:28:A3:03:3E:FA:EF:CC:
  • CD:00:97:44:93:61:1F:79:F0:60:B2:53:EB:59:F5:2C:
  • 06:BB:5D:FE:E0:02:21:00:83:DC:6F:D3:C8:30:30:5D:
  • 41:4E:3F:C6:BB:10:80:E5:63:A6:62:5E:72:F4:84:BD:
  • A2:9B:66:6F:65:28:78:1D