SSL-Tools

SSL check results of mail.janbro.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.janbro.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 Mon, 05 Aug 2024 08:53:41 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.janbro.de
2a03:4000:6:7157:14f6:69ff:fe64:2e79
 10
supported
mail.janbro.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
mail.janbro.de
37.120.175.172
 10
supported
mail.janbro.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.janbro.de

Certificate chain
  • mail.janbro.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.janbro.de
Alternative Names
  • autoconfig.broermann.family
  • autoconfig.janbro.de
  • autodiscover.broermann.family
  • autodiscover.janbro.de
  • mail.janbro.de
  • mta-sts.mail.janbro.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-08-05
Not valid after
2024-11-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BC:6C:95:10:72:F0:22:7D:57:06:63:55:78:0F:EB:AD:FF:B9:81:A1:9B:C7:5D:C9:DE:3A:CC:05:24:28:CA:9A
SHA1
89:1A:F4:61:69:95:6E:7C:6F:21:64:3E:02:AD:22:C0:80:CA:A5:D6
X509v3 extensions
subjectKeyIdentifier
  • 9C:62:D3:CB:AB:F8:64:0A:3F:17:C9:D0:91:7A:97:EB:BD:1C:BB:30
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Aug 5 07:49:55.688 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:06:82:4F:69:5F:9D:46:66:2B:ED:F3:55:
  • F9:52:6E:92:54:74:85:E1:5B:23:BF:3A:C1:8C:0D:08:
  • 15:4D:D1:08:02:21:00:B3:9F:20:9C:47:23:87:F6:6F:
  • F1:10:53:75:4C:7F:D9:AA:81:B4:FE:F9:B1:E2:65:7D:
  • F3:37:3D:62:2D:60:8D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Aug 5 07:49:55.684 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A8:E4:3F:94:D2:AA:05:87:D2:0B:D1:
  • 5A:3D:60:EC:A2:D8:3A:B3:1E:B8:7E:11:4A:E1:E8:A5:
  • 82:76:DF:81:0B:02:21:00:BA:FB:A2:9F:AF:71:D5:68:
  • 11:FE:45:0B:4A:7B:F3:77:23:A3:D6:14:68:58:E5:2A:
  • 6F:BC:3B:74:84:50:F7:71