SSL-Tools

SSL check results of hitradio-m2c.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for hitradio-m2c.de 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 Wed, 17 Apr 2024 22:41:58 +0000

The mailservers of hitradio-m2c.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @hitradio-m2c.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.hitradio-m2c.de
147.189.171.196
 5
supported
hitradio-m2c.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @hitradio-m2c.de address so far. Test mail delivery

Certificates

First seen at:

CN=hitradio-m2c.de

Certificate chain
  • hitradio-m2c.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • hitradio-m2c.de
Alternative Names
  • admin.hitradio-m2c.de
  • hitradio-m2c.de
  • mail.hitradio-m2c.de
  • webmail.hitradio-m2c.de
  • www.hitradio-m2c.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-10
Not valid after
2024-07-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FC:7E:CF:6E:61:0E:6C:D9:77:FD:4C:80:52:3C:78:BC:3B:C1:41:59:8B:D3:BA:23:8B:7C:FB:BF:33:24:3C:A1
SHA1
78:3F:53:95:F1:3B:F5:A4:0F:88:3E:6A:06:EE:6D:C9:A8:10:FB:56
X509v3 extensions
subjectKeyIdentifier
  • 23:9D:EF:BB:F9:D8:A7:71:71:EF:1A:C7:86:BA:0A:2F:CB:15:0B:51
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Apr 10 23:36:25.094 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BA:5F:96:F8:B8:CB:E5:6F:BE:D2:64:
  • 3B:92:7C:8A:ED:78:90:F7:2D:3B:64:EF:91:E9:92:F7:
  • A1:7C:14:32:B5:02:20:3F:61:A8:28:39:42:77:86:42:
  • 83:AD:97:5A:5D:6A:13:A1:F2:C9:71:66:D0:13:BD:31:
  • 38:8F:18:43:5A:2E:CD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 10 23:36:25.089 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3A:B4:FE:1A:6B:12:B6:04:D9:91:C2:6C:
  • 1C:80:4F:1D:F3:63:FC:D3:F0:4E:C8:1F:69:93:23:C7:
  • 27:07:99:E0:02:21:00:FE:DB:2D:84:CE:64:AC:CF:77:
  • 97:E7:AD:67:AD:19:B8:8C:B3:E3:1F:E4:CE:F7:ED:A4:
  • 1D:A5:37:1D:45:C8:74