SSL-Tools

SSL check results of test.computer-frickler.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for test.computer-frickler.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 Sat, 10 May 2025 00:31:49 +0000

The mailservers of test.computer-frickler.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @test.computer-frickler.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
server48.cfrickler.de
2a01:239:3c2:8700::1
 20
supported
server48.cfrickler.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
server48.cfrickler.de
217.154.243.141
 20
supported
server48.cfrickler.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @test.computer-frickler.de address so far. Test mail delivery

Certificates

First seen at:

CN=server48.cfrickler.de

Certificate chain
  • server48.cfrickler.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • server48.cfrickler.de
Alternative Names
  • server48.cfrickler.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-05-01
Not valid after
2025-07-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D2:C6:E5:9B:43:C4:A4:8C:15:E5:C5:18:60:68:21:3F:AE:14:8D:44:C4:9A:FD:17:7D:3B:2D:9B:55:67:20:F8
SHA1
86:5A:1F:16:54:3B:83:EF:7C:F5:3B:69:BB:70:92:E3:23:16:64:06
X509v3 extensions
subjectKeyIdentifier
  • 31:9D:8A:BF:41:66:7F:86:70:8C:C4:40:46:CF:C5:F4:8A:AF:34:7E
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/25.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : May 1 15:24:55.785 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A8:D4:2F:78:DB:E0:E2:CE:D4:0F:64:
  • 44:42:33:9D:55:04:51:90:8B:04:A5:AC:B4:0B:F6:A8:
  • 1E:3B:86:C5:69:02:20:02:F3:45:D7:8C:7D:83:8E:B6:
  • 53:60:29:E3:70:2E:69:F1:B5:E6:5B:70:E9:AE:54:6B:
  • 93:4B:50:9D:B9:C7:27
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : May 1 15:24:55.816 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4E:B7:FD:63:69:C4:1C:6E:86:46:B4:9B:
  • 81:71:D0:1A:79:46:1B:88:49:44:69:7E:C4:74:CE:26:
  • 98:EC:F3:24:02:21:00:C8:ED:1B:60:3F:0B:95:29:D3:
  • BD:AF:EA:0B:1A:34:FB:9B:41:50:92:97:9F:E2:37:1F:
  • 79:5B:F9:7F:C1:94:3F