SSL-Tools

SSL check results of privbox.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for privbox.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 Sat, 18 Oct 2025 15:33:07 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.privbox.net
2a03:4000:f:3b9::
 10
supported
mail.privbox.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s
mail.privbox.net
37.120.186.89
 10
supported
mail.privbox.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.privbox.net

Certificate chain
  • mail.privbox.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E8
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.privbox.net
Alternative Names
  • mail.privbox.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E8
validity period
Not valid before
2025-10-01
Not valid after
2025-12-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B8:E0:D1:DD:BF:7A:85:8F:F7:1D:8D:2D:43:48:6C:4A:CC:4F:BA:56:8A:6C:6A:7D:28:23:88:0A:A5:4D:35:02
SHA1
C3:80:9E:24:E5:DC:C9:DD:4E:09:D0:A8:42:AD:27:AD:85:2F:93:AE
X509v3 extensions
subjectKeyIdentifier
  • 9E:50:AF:C6:65:A3:F8:B6:2A:C3:73:35:8E:8D:94:10:07:CE:55:FF
authorityKeyIdentifier
  • keyid:8F:0D:13:A2:F6:2E:7E:D1:50:6C:33:18:38:5D:59:8E:23:72:91:CA
authorityInfoAccess
  • CA Issuers - URI:http://e8.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e8.c.lencr.org/11.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Oct 1 01:45:25.815 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C3:A6:CF:B3:8B:BD:29:A6:7D:71:76:
  • 6E:3E:72:57:A4:83:6A:BB:84:65:FA:E2:A3:EB:12:A7:
  • FD:99:85:08:2A:02:20:55:D2:B9:43:BF:9C:05:40:92:
  • B6:73:D6:6E:B9:9A:B2:FB:6D:61:38:F3:7C:64:D6:97:
  • 6C:B6:24:E1:A3:29:BA
  • 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 : Oct 1 01:45:25.837 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A1:CD:86:F6:02:D9:46:99:2E:53:D0:
  • 4B:89:D1:6D:0F:3E:D9:65:32:48:59:FD:4D:62:19:05:
  • 0E:6D:F3:76:CC:02:20:5D:CE:A2:6E:B2:DC:03:19:A5:
  • F6:10:1E:B9:D6:38:C0:7C:9F:4A:F1:CF:8C:64:FF:DC:
  • 03:5C:56:BB:DC:2E:20

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.privbox.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid