SSL-Tools

SSL check results of radioframe.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for radioframe.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 Tue, 23 Feb 2021 14:59:51 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.radioframe.net
51.15.113.77
 1
supported
mail.radioframe.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

We have received emails from these servers with @radioframe.net sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.radioframe.net (51.15.113.77)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.radioframe.net

Certificate chain
  • mail.radioframe.net
    • 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)
  • mail.radioframe.net
Alternative Names
  • mail.radioframe.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-07
Not valid after
2021-04-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B7:66:9C:FB:0F:C7:8E:4A:9B:22:3F:22:EC:43:3E:CA:40:7D:67:E8:A4:0A:DB:4A:4D:C5:ED:32:AE:81:67:FB
SHA1
83:71:5F:08:3A:EA:5E:5F:6D:09:4B:82:38:11:EA:99:EE:92:FE:31
X509v3 extensions
subjectKeyIdentifier
  • CF:66:2C:E5:D9:05:90:CD:F4:C1:12:05:B1:28:64:AB:80:9D:78:EA
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 : Jan 8 00:44:06.247 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:21:21:9E:6C:EF:49:F8:C3:79:54:43:C1:
  • C6:C9:42:81:99:B5:3F:B9:BC:33:BF:A0:46:E0:41:4D:
  • 04:67:27:06:02:20:2E:56:7E:89:D2:46:C6:22:1A:93:
  • D9:54:FD:4D:F3:EE:5A:FD:C8:81:F3:28:81:2E:C6:4C:
  • 59:49:92:38:47:0E
  • 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 : Jan 8 00:44:06.315 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:23:32:CC:67:EB:66:24:B0:D0:F9:F9:BB:
  • F5:20:F4:39:17:E1:6F:D7:BD:18:99:69:FF:24:B2:A8:
  • 97:AA:86:0C:02:21:00:A9:BA:DD:9E:3C:1A:5C:2E:F3:
  • 70:E3:0B:91:1C:FC:79:BE:CD:17:EC:27:56:E3:5F:05:
  • B6:6B:73:64:B4:C8:B5