SSL-Tools

SSL check results of technikrebell.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for technikrebell.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 Tue, 15 Apr 2025 20:17:04 +0000

The mailservers of technikrebell.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @technikrebell.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.technikrebell.de
202.61.252.172
 0
supported
mail.technikrebell.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 @technikrebell.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.technikrebell.de

Certificate chain
  • mail.technikrebell.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.technikrebell.de
Alternative Names
  • autoconfig.technikrebell.de
  • autodiscover.technikrebell.de
  • imap.technikrebell.de
  • mail.technikrebell.de
  • mta-sts.technikrebell.de
  • pop3.technikrebell.de
  • smtp.technikrebell.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-04-15
Not valid after
2025-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FE:5B:96:CD:62:04:E0:63:27:79:02:46:9E:C0:46:0F:52:7B:92:1A:FD:D0:4E:10:A9:20:04:AA:DC:71:64:2B
SHA1
8A:30:77:EE:3A:46:66:82:B6:63:3E:2C:88:7D:DA:C6:1A:8A:95:E8
X509v3 extensions
subjectKeyIdentifier
  • 8E:80:23:C0:B9:8F:5C:BC:28:46:EF:16:93:19:CF:AA:97:51:46:17
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/53.crl
ct_precert_scts
  • 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 : Apr 15 18:25:51.933 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:62:37:F4:C5:09:7D:AD:B6:D8:06:D9:13:
  • 4B:B5:90:EA:65:56:EC:7A:F9:18:A9:67:F4:D1:38:80:
  • D8:25:B6:34:02:21:00:C2:59:D9:5D:56:2A:17:7D:46:
  • CA:AC:F6:96:FF:25:4E:DA:BA:26:FC:D3:66:EF:E8:ED:
  • 3D:40:4E:6E:FD:71:21
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Apr 15 18:25:53.905 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D3:7E:A6:5B:49:69:68:CD:7B:7E:7B:
  • C3:CD:4C:6D:41:9B:D3:23:93:AD:6E:67:23:C2:6D:85:
  • A4:81:7F:49:6F:02:21:00:91:5A:07:F0:B2:AD:EF:B0:
  • 19:91:DE:07:FA:2E:ED:C0:A2:29:E8:6B:DF:25:E8:5B:
  • 95:E0:88:4D:F4:DD:94:AC