SSL-Tools

SSL check results of kanzleimiltenberg.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for kanzleimiltenberg.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 Fri, 29 Nov 2024 01:31:12 +0000

We can not guarantee a secure connection to the mailservers of kanzleimiltenberg.de!

Please contact the operator of kanzleimiltenberg.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/kanzleimiltenberg.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
panel1.13bit.de
fe80::5054:94ff:fe68:633a
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
panel1.13bit.de
83.171.238.166
 10
supported
panel1.13bit.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 @kanzleimiltenberg.de address so far. Test mail delivery

Certificates

First seen at:

CN=panel1.13bit.de

Certificate chain
  • panel1.13bit.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • panel1.13bit.de
Alternative Names
  • panel1.13bit.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-26
Not valid after
2025-01-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9C:D9:72:54:0E:4D:B6:F9:8F:9C:60:C8:21:1B:88:5B:D3:5D:9C:A7:54:B6:75:61:6E:C4:37:90:8B:E9:30:9B
SHA1
7B:F9:77:A2:91:E0:3B:D9:1D:77:89:09:93:E9:48:E0:82:1D:46:B6
X509v3 extensions
subjectKeyIdentifier
  • 9A:9F:BF:15:4C:6A:FD:AF:C1:18:B7:F5:08:4C:54:1F:07:31:3A:F8
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 : 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 : Oct 26 10:34:11.547 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D9:F0:10:42:EE:BE:F8:82:F6:5B:E0:
  • 30:AA:B5:68:0C:DD:CA:09:6C:A9:E0:4B:99:7C:2D:3B:
  • 18:28:D1:3D:64:02:20:39:A0:DE:D0:4B:2E:CC:2B:A7:
  • 94:64:4A:D8:FA:78:CF:8A:0B:73:8D:F6:B1:90:08:41:
  • C2:9F:59:ED:5D:AB:C3
  • 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 : Oct 26 10:34:11.550 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F0:39:67:23:0C:18:7A:A7:44:69:C3:
  • 08:97:83:72:11:58:12:7E:AE:83:22:85:5E:7F:8D:DE:
  • 44:7C:05:C0:01:02:20:60:6E:64:A1:6C:0F:9E:37:B3:
  • EC:2E:A0:43:7B:2B:70:D9:FF:78:6B:99:2F:9E:E6:C0:
  • 7A:17:8A:B1:21:4A:C2