SSL check results of reddevilsystems.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for reddevilsystems.eu 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 Thu, 04 Apr 2024 16:52:48 +0000

The mailservers of reddevilsystems.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @reddevilsystems.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.reddevilsystems.eu
24.134.99.117
20
supported
reddevilsystems.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @reddevilsystems.eu sender addresses. Test mail delivery

Host TLS Version & Cipher
smtp.reddevilsystems.eu (24.134.99.117)
TLSv1.2 AES128-SHA256

Certificates

First seen at:

CN=reddevilsystems.eu

Certificate chain
  • reddevilsystems.eu
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • reddevilsystems.eu
Alternative Names
  • reddevilsystems.eu
  • smtp.reddevilsystems.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-04
Not valid after
2024-07-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BC:BF:1F:F1:50:6D:3F:33:A2:D5:34:93:DC:31:4C:00:17:48:CF:6C:36:80:6A:31:B4:E3:67:CA:96:FC:27:D8
SHA1
4A:B8:A0:2C:EF:16:51:5F:69:B6:B8:CB:86:68:11:3F:8E:DC:8A:57
X509v3 extensions
subjectKeyIdentifier
  • 85:4C:A9:55:01:E8:EC:A2:49:4E:02:F0:76:EF:4D:80:ED:93:75:EC
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 4 16:28:03.207 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:43:02:1F:38:21:34:88:87:30:F3:FE:5D:6B:0B:D1:
  • 4F:4B:80:6A:59:8A:44:A7:D1:AF:D5:C3:10:7A:72:C1:
  • 95:7F:EC:02:20:16:00:02:AC:B8:BD:F8:B5:98:44:BB:
  • 0A:50:8B:D5:FC:9B:45:AB:19:F1:41:E2:12:D9:C9:A0:
  • D9:BF:51:23:97
  • 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 : Apr 4 16:28:03.244 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1F:7A:CD:EB:C9:96:58:BE:78:06:AF:1E:
  • 34:70:DE:47:56:17:E8:BC:AF:AE:10:B1:B9:05:85:3A:
  • BC:44:31:8D:02:20:60:06:44:C3:24:D8:48:C9:B7:36:
  • 69:24:5C:6F:B6:B4:BB:ED:CF:CF:5B:F5:7C:BB:11:11:
  • F6:55:A3:0A:EE:79