SSL-Tools

SSL check results of allmylife.blog

NEW You can also bulk check multiple servers.

Discover if the mail servers for allmylife.blog 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 Mon, 23 Sep 2024 00:30:35 +0000

The mailservers of allmylife.blog can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @allmylife.blog addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.allmylife.blog
2a01:e0a:2bb:e8e0:9a0e:587c:16e0:f9f0
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
mail.allmylife.blog
82.64.102.228
 10
supported
mail.allmylife.app
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

We have not received any emails from a @allmylife.blog address so far. Test mail delivery

Certificates

First seen at:

CN=mail.allmylife.app

Certificate chain
  • mail.allmylife.app
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.allmylife.app
Alternative Names
  • mail.allmylife.app
  • mail.allmylife.blog
  • mail.mylife.app
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-08-18
Not valid after
2024-11-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E9:BB:BB:BC:05:79:5A:8D:16:D1:10:B5:FB:30:95:DD:8B:75:7E:75:44:3B:58:3C:35:F2:DC:2A:D2:E7:F6:35
SHA1
8E:FC:98:50:DF:65:C3:8C:E6:C5:BF:BC:E4:83:80:85:AD:59:E4:03
X509v3 extensions
subjectKeyIdentifier
  • C5:85:68:19:DE:AE:CC:AF:9D:23:5C:52:24:7E:D0:75:D4:84:B6:30
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 : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Aug 18 11:37:56.880 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:04:3A:FC:49:54:C5:BD:C3:70:5C:1E:2D:
  • A0:3B:E2:F1:E4:0E:55:45:32:B4:25:D0:F4:BF:2C:25:
  • C1:9C:DB:F9:02:21:00:B0:5D:AC:57:F1:EC:67:65:4C:
  • 23:2C:D0:DA:39:9F:08:F6:DE:BF:0D:42:27:D0:6C:03:
  • 1F:59:F4:92:92:46:65
  • 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 : Aug 18 11:37:57.150 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:76:06:0A:C9:1B:7B:36:E6:CD:5C:A4:3E:
  • DE:42:21:83:1C:9D:92:48:C1:86:D1:AB:E3:3F:D7:0A:
  • 0F:DA:B0:AB:02:20:67:5E:D0:D5:E2:E9:F5:30:1D:85:
  • 11:3A:19:BF:9A:7D:E2:8B:EC:A3:A7:01:1A:15:C8:43:
  • B9:CE:D0:FA:1C:EA