SSL-Tools

SSL check results of karatsbichl.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for karatsbichl.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 Tue, 23 Apr 2024 22:35:55 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
ns2.karatsbichl.com
2a01:4f8:c2c:a036::2
 10
supported
*.karatsbichl.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s
ns2.karatsbichl.com
78.47.76.193
 10
supported
*.karatsbichl.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s

Outgoing Mails

We have received emails from these servers with @karatsbichl.com sender addresses. Test mail delivery

Host TLS Version & Cipher
ns2.karatsbichl.com (IPv6:2a01:4f8:c2c:a036::2)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=*.karatsbichl.com

Certificate chain
  • *.karatsbichl.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.karatsbichl.com
Alternative Names
  • *.karatsbichl.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-09
Not valid after
2024-07-08
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
61:2F:E3:3B:D5:84:D3:2A:A8:9B:C4:93:7D:15:B6:C1:E9:CD:36:96:F1:A3:3A:52:EB:A1:8F:55:56:E2:AF:37
SHA1
5B:A0:B0:27:38:B6:D0:90:CA:0A:5A:94:FC:07:5C:13:F7:73:2B:8B
X509v3 extensions
subjectKeyIdentifier
  • 29:B2:8C:B1:70:99:07:CF:6B:C4:3B:D0:5E:2A:58:F5:E0:C1:65:32
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 9 20:35:19.376 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F5:E6:77:54:CA:A5:6C:F2:9E:06:FE:
  • 60:29:3F:6A:57:C0:1B:9D:66:68:D7:D6:16:FC:37:19:
  • 87:55:98:E5:81:02:21:00:9D:83:9B:E7:4F:ED:0F:E7:
  • 97:0E:77:BD:37:0C:11:17:65:35:E9:C7:6E:97:4A:CB:
  • 6A:BB:17:42:34:51:A5:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 9 20:35:19.459 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:37:5A:D2:FE:A8:F4:8B:0C:38:CD:9A:BF:
  • 31:07:39:CB:0A:E4:D6:54:D9:E7:15:C6:23:46:F1:12:
  • E6:63:C1:F0:02:21:00:9B:EB:F1:4A:DE:1E:B4:C6:6C:
  • 41:6E:85:44:C8:79:9D:E0:3A:B5:C4:5D:27:1F:70:CC:
  • 65:E1:A2:34:E2:27:27