SSL-Tools

SSL check results of post.paulbrandenburg.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for post.paulbrandenburg.com 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, 22 Feb 2025 01:31:57 +0000

The mailservers of post.paulbrandenburg.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @post.paulbrandenburg.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
post.paulbrandenburg.com
185.16.62.34
 -
supported
post.paulbrandenburg.com
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 @post.paulbrandenburg.com address so far. Test mail delivery

Certificates

First seen at:

CN=post.paulbrandenburg.com

Certificate chain
  • post.paulbrandenburg.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • post.paulbrandenburg.com
Alternative Names
  • post.paulbrandenburg.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-02-15
Not valid after
2025-05-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
74:18:9D:03:47:4B:D0:24:4F:AC:B1:F0:A6:21:E1:E5:1C:1E:78:8F:51:5B:D8:BF:51:F9:43:11:92:7A:0E:C4
SHA1
C3:8D:CD:75:7B:F4:D5:F1:D9:CA:F0:25:01:36:9E:95:BF:AE:27:C5
X509v3 extensions
subjectKeyIdentifier
  • BD:BC:C2:18:24:DA:DA:EF:BB:E7:2F:2F:64:81:F4:68:1C:96:37:5D
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
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 : Feb 15 12:17:34.382 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:37:FA:CF:1A:D7:55:E1:9B:C5:D4:D4:4D:
  • 52:03:82:EC:15:E5:62:C8:8A:32:60:8B:94:FE:EB:A2:
  • 4F:4F:F5:1D:02:20:41:B3:47:4E:EE:A1:69:3E:BE:84:
  • 53:AB:91:BD:22:D1:7E:BC:9B:26:54:3E:6A:6E:F4:22:
  • C7:51:7F:A4:E8:D2
  • 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 : Feb 15 12:17:34.438 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:62:1A:42:70:C9:55:A4:D3:62:6E:A0:F9:
  • A9:11:02:08:98:3A:4E:75:91:D0:C7:2D:42:E2:E7:73:
  • C3:E7:40:59:02:21:00:D6:EB:AE:26:9B:71:6B:9A:A4:
  • CC:12:C7:B8:5D:D4:CE:1E:9D:11:39:EA:20:93:2D:9B:
  • DD:E2:F3:AF:29:96:CA