SSL-Tools

SSL check results of bitwaves.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for bitwaves.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 Sun, 26 Jan 2025 01:31:16 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.bitwaves.de
2a01:238:420b:1c00:dead:beef:dead:1
 10
supported
bitwaves.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.bitwaves.de
85.215.94.44
 10
supported
bitwaves.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=bitwaves.de

Certificate chain
  • bitwaves.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • bitwaves.de
Alternative Names
  • *.bitwaves.de
  • bitwaves.de
  • bitwaves.eu
  • bitwaves.info
  • bitwaves.net
  • www.bitwaves.eu
  • www.bitwaves.info
  • www.bitwaves.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-19
Not valid after
2025-04-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
80:6A:41:99:BD:D4:6B:C8:2B:43:C5:43:F0:BF:E0:6F:CA:F1:6E:84:94:23:E1:44:CF:10:88:F7:F7:8B:F0:7C
SHA1
1A:AA:BB:8A:B4:EA:4C:A6:48:75:23:27:8D:9C:5E:FF:CC:7F:09:FD
X509v3 extensions
subjectKeyIdentifier
  • 8B:7B:39:7F:5F:FD:A0:FA:72:52:0C:6F:DD:C0:46:B3:24:27:07:F6
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
ct_precert_scts
  • 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 : Jan 19 21:33:06.126 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:57:57:09:9B:14:DD:D0:C4:64:55:CC:33:
  • BD:1F:9B:F0:6C:29:82:DE:00:69:7A:B5:4E:73:21:3D:
  • EC:EB:83:33:02:21:00:90:E8:CF:5B:20:2B:4D:75:98:
  • 01:DA:DB:0E:7A:28:E9:BE:77:7E:2E:4A:51:D9:30:1B:
  • F7:3A:5D:38:B4:36:B5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Jan 19 21:33:06.132 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6C:3E:EB:76:44:7C:1E:04:95:49:EC:2A:
  • 95:95:7D:91:CA:75:F2:D6:E7:DF:F9:09:B0:23:16:C0:
  • 65:0C:FE:BF:02:20:70:8B:70:AE:47:FF:9E:AB:62:D9:
  • 3C:DC:5C:01:ED:EE:A0:4C:DC:44:F0:DC:48:DB:12:A7:
  • A2:93:7F:2A:6C:55