SSL-Tools

SSL check results of nebuk.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for nebuk.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, 22 Oct 2024 08:44:14 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.ghostdub.de
95.216.78.222
 10
supported
mail.ghostdub.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 @nebuk.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.ghostdub.de

Certificate chain
  • mail.ghostdub.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)
  • mail.ghostdub.de
Alternative Names
  • ghostdub.de
  • imap.ghostdub.de
  • kanojo.de
  • mail.ghostdub.de
  • mail.ram.en.it
  • matrix.ghostdub.de
  • nebuk.de
  • rakka.de
  • ram.en.it
  • smtp.ghostdub.de
  • xorn.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-22
Not valid after
2025-01-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C3:6F:13:29:F5:51:11:5E:97:2F:0C:C0:6B:B3:A6:E6:09:29:04:3F:6F:0B:29:52:AC:03:BB:29:3A:AA:49:DA
SHA1
53:FE:4E:09:06:EE:C1:8B:BC:6E:42:E4:DF:DE:9F:AD:7A:76:CF:BC
X509v3 extensions
subjectKeyIdentifier
  • 2E:57:F7:DE:75:42:62:38:19:E9:85:DD:DC:AE:B1:3F:6A:76:3E:A7
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 : 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 : Oct 22 08:39:40.718 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F7:5F:46:EE:AC:76:DC:D9:43:43:22:
  • 22:CF:F7:5F:52:08:91:0C:21:34:91:E6:FD:A6:67:99:
  • D1:24:5F:3E:03:02:20:42:08:83:10:87:80:DC:6F:B1:
  • E4:34:0B:6A:08:1D:35:22:DD:E0:89:42:20:F7:08:9A:
  • 02:AC:65:16:6A:F0:66
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 22 08:39:40.785 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D8:89:09:A2:7E:80:F9:F2:4C:EE:91:
  • 0A:36:37:E3:6B:90:D6:2E:68:4B:EA:9B:BA:29:4F:5E:
  • BC:64:F9:FF:D5:02:20:46:39:6C:8F:E0:51:6E:49:CC:
  • 93:C7:9B:9E:BC:AA:4C:31:08:77:7D:4B:AB:1F:4B:00:
  • CC:80:69:ED:13:21:0A