SSL-Tools

SSL check results of radio-today.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for radio-today.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 Fri, 27 Nov 2020 13:57:46 +0000

We can not guarantee a secure connection to the mailservers of radio-today.de!

Please contact the operator of radio-today.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/radio-today.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @radio-today.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
radio-today.de
2a02:c207:3005:4532::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
radio-today.de
95.111.252.67
 10
supported
*.radio-today.de
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
12 s

Outgoing Mails

We have received emails from these servers with @radio-today.de sender addresses. Test mail delivery

Host TLS Version & Cipher
www.radio-today.de (95.111.252.67)
TLSv1.2 AECDH-AES256-SHA

Certificates

First seen at:

CN=*.radio-today.de

Certificate chain
Subject
Common Name (CN)
  • *.radio-today.de
Alternative Names
  • *.frank-fux.de
  • *.radio-today.de
  • frank-fux.de
  • radio-today.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-10-06
Not valid after
2021-01-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CA:0B:82:40:14:88:61:9D:6B:60:F2:25:BB:35:0C:5A:E0:87:C6:69:0D:05:D8:77:FC:5B:F5:9D:BC:78:F6:DA
SHA1
A0:66:5D:30:AC:7A:38:16:A9:52:68:D8:4D:45:5B:BE:45:DF:F9:BD
X509v3 extensions
subjectKeyIdentifier
  • 58:37:E3:EB:A3:C6:2A:EC:7B:8D:CC:5F:54:61:23:9E:90:57:10:1C
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Oct 6 09:27:45.213 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F7:81:6D:6B:0B:12:15:83:2A:37:00:
  • 26:E9:91:11:9A:CC:37:E0:6D:B8:27:E3:9B:A2:07:10:
  • 3A:EF:E5:E8:D2:02:21:00:EA:EE:75:08:C9:E1:87:F6:
  • FE:33:67:AE:83:4D:F2:AE:40:46:DD:A9:24:44:D7:18:
  • 13:C2:E3:8D:7B:10:8B:C4
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Oct 6 09:27:45.184 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E3:66:1A:BE:20:54:73:BF:C9:7E:8E:
  • CA:CD:54:BD:CB:82:56:17:63:45:79:25:8E:A3:91:86:
  • 89:97:11:30:A0:02:20:31:C6:56:2A:5A:19:7B:DE:21:
  • E8:B7:E4:36:58:90:A1:AC:B7:6D:76:44:A8:7A:3B:30:
  • 78:13:D1:4A:55:5D:0D