SSL-Tools

SSL check results of schallert.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for schallert.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, 07 May 2024 18:54:33 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.schallert.com
2a0b:5cc0:0:200::66
 10
supported
mail.schallert.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.schallert.com
185.210.224.66
 10
supported
mail.schallert.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Host TLS Version & Cipher
mail.schallert.com (IPv6:2a0b:5cc0:0:200::66)
TLSv1.3 TLS_AES_256_GCM_SHA384
mail2.schallert.com (185.210.224.67)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.schallert.com

Certificate chain
  • mail.schallert.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)
  • mail.schallert.com
Alternative Names
  • mail.schallert.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-07
Not valid after
2024-07-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
81:EE:2C:03:9D:3D:15:BE:6E:3F:7A:FC:9F:6E:EC:DE:42:E2:D6:CD:3E:24:2D:E6:21:0C:88:36:C1:2B:24:86
SHA1
CE:01:5E:C7:59:D7:08:BF:89:07:09:CC:18:7C:96:B5:2D:D2:07:55
X509v3 extensions
subjectKeyIdentifier
  • A4:F8:2F:31:2E:FE:76:9D:B5:12:14:50:86:83:3E:48:9F:DF:52:21
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 7 19:00:46.911 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3D:3D:58:39:7F:0C:11:01:4A:A5:31:DD:
  • A0:EF:A2:7A:65:07:78:68:07:06:6C:76:5F:22:B1:F7:
  • 1D:07:78:DA:02:21:00:95:DA:20:83:D4:39:96:D0:C8:
  • 31:B7:46:42:AB:1D:4C:AF:45:E5:D7:2B:AB:E5:7A:78:
  • E5:04:4E:52:18:83:97
  • 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 7 19:00:46.929 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:74:FD:F1:71:13:46:CD:D8:C8:63:F0:32:
  • AF:7E:B3:86:51:B4:DC:75:68:C5:E1:E1:F8:C4:EA:06:
  • 91:F7:9F:72:02:21:00:B8:00:09:23:81:AF:6F:D5:57:
  • CF:6F:D6:DE:43:B6:49:71:CE:43:A2:38:BE:36:8E:65:
  • F5:3C:FF:5A:81:6D:4A