SSL-Tools

SSL check results of ragnarokeurope.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for ragnarokeurope.net 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, 13 Dec 2020 11:47:51 +0000

The mailservers of ragnarokeurope.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @ragnarokeurope.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
4-box.de
2a02:2b80:101:104::322
 10
supported
4-box.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
4-box.de
5.44.107.239
 10
supported
4-box.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=4-box.de

Certificate chain
  • 4-box.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • 4-box.de
Alternative Names
  • 4-box.de
  • webmail.4-box.de
  • www.4-box.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2020-12-03
Not valid after
2021-03-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BD:AF:B8:DD:40:18:89:E5:C7:53:24:C9:10:6F:72:28:5B:94:A0:6E:5F:91:7B:64:D0:D0:79:3D:54:C1:3A:79
SHA1
52:BA:07:B6:5E:40:59:DC:5C:FE:A6:08:E4:3D:51:F9:02:C8:C2:87
X509v3 extensions
subjectKeyIdentifier
  • 78:48:23:B0:FD:59:F0:C7:D5:83:12:4B:F7:B1:FA:C0:70:5E:ED:10
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Dec 3 17:27:28.421 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E7:B9:AA:09:5C:DF:4A:04:A4:82:17:
  • 35:CE:A2:05:4A:4C:FE:F6:F8:4B:D1:91:BE:15:D9:87:
  • 12:E8:04:F6:07:02:20:7C:35:56:4E:CD:1B:14:74:73:
  • 9A:22:E6:06:34:F7:38:D4:17:FB:5E:C7:93:19:78:75:
  • EE:AC:56:89:87:34:4D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Dec 3 17:27:28.497 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AD:D8:5D:52:C7:16:CB:82:CC:9B:8F:
  • 95:A3:CE:1E:C6:4B:DB:89:04:0D:1A:1B:1F:0F:D0:E9:
  • CE:D4:58:AD:FB:02:20:13:2C:5D:AB:A5:62:CB:D5:CF:
  • 96:CF:2A:06:E8:E1:2D:B9:BA:59:8B:22:F6:D3:5B:C6:
  • A9:A0:37:98:14:90:56