SSL check results of post.jutt.family

NEW You can also bulk check multiple servers.

Discover if the mail servers for post.jutt.family 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

Report created Tue, 01 Oct 2024 22:36:25 +0000

The mailservers of post.jutt.family can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @post.jutt.family addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
post.jutt.family
87.106.199.244
-
supported
post.jutt.family
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s
post.jutt.family
2a00:da00:f419:3900::1
-
supported
post.jutt.family
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

We have not received any emails from a @post.jutt.family address so far. Test mail delivery

Certificates

First seen at:

CN=post.jutt.family

Certificate chain
  • post.jutt.family
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • post.jutt.family
Alternative Names
  • post.jutt.family
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-10-01
Not valid after
2024-12-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9A:BD:16:C1:D2:CC:B3:7C:5D:16:DE:8C:73:B5:7F:5D:48:DD:16:66:A5:DC:CB:58:55:37:D2:2E:67:6B:45:63
SHA1
78:47:6E:DB:3A:76:0B:A5:78:59:D8:46:45:DF:33:4C:DB:13:2E:10
X509v3 extensions
subjectKeyIdentifier
  • 06:8C:00:85:4D:27:F7:85:19:08:F6:6F:A2:B0:39:9C:EA:C4:51:42
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 : Oct 1 20:24:25.977 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C8:CA:13:EE:C0:F8:DB:ED:AC:CE:EA:
  • 6A:69:2E:59:41:F4:C5:D6:47:D7:5B:C1:1D:3D:26:85:
  • AD:FF:8C:43:93:02:20:75:DB:09:D9:3B:E8:0D:DD:9F:
  • 2D:F0:1B:2D:7D:B2:EF:54:AF:B3:5E:4B:4A:4D:30:58:
  • C3:5A:A8:2D:8C:43:79
  • 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 1 20:24:26.062 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AA:C9:AA:3E:0E:4B:4B:13:CD:C7:38:
  • B7:88:C0:8B:EA:C6:48:3D:21:2C:44:E4:5B:34:23:BE:
  • E7:98:0D:39:45:02:21:00:EA:17:08:C8:A6:41:32:BB:
  • A5:9D:36:A8:DC:F8:1B:82:ED:94:ED:EA:8A:8F:40:2D:
  • BA:F2:46:9B:3F:8B:F8:2C