SSL check results of patrickbrosi.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for patrickbrosi.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

Report created Sat, 21 Dec 2024 11:35:03 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.patrickbrosi.de
159.69.13.127
10
supported
patrickbrosi.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=patrickbrosi.de

Certificate chain
  • patrickbrosi.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • patrickbrosi.de
Alternative Names
  • cal.patrickbrosi.de
  • dont.watch
  • git.patrickbrosi.de
  • mail.patrickbrosi.de
  • patrickbrosi.de
  • piwik.patrickbrosi.de
  • tiles.patrickbrosi.de
  • tracker.patrickbrosi.de
  • webcal.patrickbrosi.de
  • wiki.patrickbrosi.de
  • www.dont.watch
  • www.patrickbrosi.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-12-02
Not valid after
2025-03-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C6:78:43:73:D0:7A:89:BC:75:15:15:46:36:AB:0B:3B:2D:38:21:F0:D7:AC:8D:3E:97:A7:B4:BE:DA:18:14:64
SHA1
9F:9F:83:20:B2:88:BC:DE:2A:B3:BC:B0:66:5F:52:FE:80:B8:AE:A8
X509v3 extensions
subjectKeyIdentifier
  • 36:36:3D:48:65:02:83:39:FC:F1:1B:F5:E0:7F:94:70:C2:2F:75:EF
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 : 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 : Dec 2 11:24:51.620 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5A:44:24:8C:7B:70:12:F2:E9:93:F2:C0:
  • A3:2A:D6:DA:24:B1:A8:60:C0:5A:26:14:84:FF:44:20:
  • 2F:55:53:27:02:21:00:B6:50:BE:11:A9:07:94:B1:48:
  • CB:AF:6B:31:96:0D:9A:65:FF:05:D2:82:DC:F7:36:62:
  • B3:8C:7B:17:11:5B:CF
  • 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 : Dec 2 11:24:51.619 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CA:E8:8D:36:0B:41:FF:75:26:1A:D5:
  • 0C:2A:D5:5C:22:4C:6E:6E:8B:FE:34:68:6E:A6:90:98:
  • 51:1D:5A:E9:47:02:21:00:D7:A0:8F:91:A3:55:92:05:
  • DC:E4:57:47:96:44:D0:7D:AC:3D:D3:14:64:2E:7D:6A:
  • 1F:27:B0:C7:4E:73:F1:29