SSL-Tools

SSL check results of rndc.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for rndc.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 Mon, 13 Jul 2020 01:45:57 +0000

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

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

/mailservers/rndc.ru

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
void.blackhole.mx
2a01:4f8:1c0c:54b0::2
Results incomplete
0 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
void.blackhole.mx
2a01:4f8:1c17:4376::2
Results incomplete
0 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
void.blackhole.mx
78.47.159.103
 0
supported
example.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
void.blackhole.mx
195.201.28.161
 0
supported
example.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=example.com,O=Example,L=Example,ST=Example,C=US

Certificate chain
  • example.com (Certificate is self-signed.)
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
    • Unknown Authority
Subject
Country (C)
  • US
State (ST)
  • Example
Locality (L)
  • Example
Organization (O)
  • Example
Common Name (CN)
  • example.com
Issuer

Certificate is self-signed.

validity period
Not valid before
2020-06-16
Not valid after
2030-06-14
Fingerprints
SHA256
D4:05:CE:AB:19:E1:DA:73:BC:F8:79:CD:CD:A4:1E:03:7D:A9:2A:1F:98:59:53:E3:C5:C9:9A:C3:BE:DE:9E:24
SHA1
7F:10:8C:1A:14:F7:F2:A0:FE:B2:27:F6:44:F7:C9:E3:29:33:40:2A
X509v3 extensions
subjectKeyIdentifier
  • D7:83:50:1C:48:E4:44:5D:CD:A4:90:10:7D:EF:90:5A:5D:0C:01:75
authorityKeyIdentifier
  • keyid:D7:83:50:1C:48:E4:44:5D:CD:A4:90:10:7D:EF:90:5A:5D:0C:01:75
First seen at:

CN=example.com,O=Example,L=Example,ST=Example,C=US

Certificate chain
  • example.com (Certificate is self-signed.)
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
    • Unknown Authority
Subject
Country (C)
  • US
State (ST)
  • Example
Locality (L)
  • Example
Organization (O)
  • Example
Common Name (CN)
  • example.com
Issuer

Certificate is self-signed.

validity period
Not valid before
2020-06-16
Not valid after
2030-06-14
Fingerprints
SHA256
90:AC:0B:20:B4:8A:9D:F1:BF:41:69:A4:2E:15:7D:27:AF:8D:64:57:72:28:40:94:A3:A3:01:9D:24:9C:34:5F
SHA1
5B:48:50:56:8E:FB:45:35:1D:8B:DD:D6:60:0E:49:F4:2D:2F:32:CA
X509v3 extensions
subjectKeyIdentifier
  • 85:AB:42:B7:07:FA:98:48:4C:80:0A:8A:03:77:68:A4:E4:91:85:66
authorityKeyIdentifier
  • keyid:85:AB:42:B7:07:FA:98:48:4C:80:0A:8A:03:77:68:A4:E4:91:85:66