SSL-Tools

SSL check results of buerkle-og.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for buerkle-og.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 Thu, 25 Apr 2024 04:10:36 +0000

The mailservers of buerkle-og.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @buerkle-og.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.buerkle-og.de
2a01:4f8:1c17:7adf::1
 32767
supported
mail.buerkle-og.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mail.buerkle-og.de
167.235.203.3
 32767
supported
mail.buerkle-og.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.buerkle-og.de

Certificate chain
  • mail.buerkle-og.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.buerkle-og.de
Alternative Names
  • autoconfig.buerkle-og.de
  • autodiscover.buerkle-og.de
  • mail.buerkle-og.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-24
Not valid after
2024-07-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
77:73:7B:39:E0:F6:FE:E8:7E:67:6F:28:41:F1:0C:94:86:A3:58:69:5C:5B:20:C6:D3:DC:B0:F1:4A:8E:EC:C5
SHA1
31:05:97:11:70:F7:05:21:69:A4:4C:ED:0C:46:6C:DC:1A:89:76:EE
X509v3 extensions
subjectKeyIdentifier
  • F1:D1:BB:CC:33:22:BD:65:0F:E4:7C:0E:A4:CD:49:52:70:1A:06:35
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.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 : Apr 24 17:16:46.404 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:31:66:E3:8D:4B:F8:59:4A:48:0E:F8:E2:
  • 82:A1:CD:C8:51:B5:DD:EC:63:E6:83:79:2A:D7:FA:79:
  • 11:BD:85:F0:02:20:1C:88:62:A6:EA:70:4F:D9:AE:A5:
  • 76:D5:97:1F:11:30:E0:23:FA:39:22:86:9E:42:9D:3F:
  • A3:AE:87:71:92:65
  • 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 : Apr 24 17:16:46.399 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DF:15:EA:80:A0:1F:03:D9:41:26:A9:
  • 73:D1:EB:5B:BC:FF:03:FE:74:73:29:92:93:7A:11:FC:
  • 34:C9:A3:C0:AB:02:20:52:7E:3E:45:D5:C2:B2:24:F8:
  • BC:90:92:78:05:D3:AE:53:A2:B7:3A:A6:66:C8:E6:06:
  • 1F:56:99:29:D8:53:E3