SSL-Tools

SSL check results of meh.cat

NEW You can also bulk check multiple servers.

Discover if the mail servers for meh.cat 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 Wed, 03 Sep 2025 13:52:44 +0000

The mailservers of meh.cat can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @meh.cat addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.comellas.dev
2a01:4f8:c013:b433::1
 10
supported
mail.comellas.dev
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
23 s
mail.comellas.dev
157.90.154.169
 10
supported
mail.comellas.dev
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
90 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.comellas.dev

Certificate chain
  • mail.comellas.dev
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.comellas.dev
Alternative Names
  • imap.comellas.dev
  • mail.comellas.dev
  • smtp.comellas.dev
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2025-07-31
Not valid after
2025-10-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F4:23:88:05:FD:15:D9:21:1F:D4:4B:56:33:7A:E9:EE:12:7E:3D:96:FB:06:BF:AB:D0:E0:41:D8:A5:0C:35:86
SHA1
E9:C4:BC:F6:CF:F2:14:4F:AF:D8:27:51:F1:13:7D:6D:72:0B:23:5D
X509v3 extensions
subjectKeyIdentifier
  • EE:CC:61:D6:E2:41:BE:8A:BF:E9:07:7E:DE:59:92:6A:64:E1:93:F0
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e6.c.lencr.org/11.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jul 31 14:49:52.274 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7F:D8:4A:7B:0B:D5:6E:C1:BC:A5:32:A4:
  • DE:52:6E:FB:E7:60:1C:EE:8C:47:9F:51:E7:B9:90:29:
  • F9:D3:88:95:02:21:00:D7:1F:60:6C:4A:F0:AA:DA:7B:
  • 99:3F:41:7C:C1:C3:32:D7:21:AE:92:36:41:A8:AB:BE:
  • AC:8E:C7:EF:8A:B5:15
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jul 31 14:49:52.293 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6F:57:D8:5D:F4:94:98:FD:0E:0B:10:D6:
  • 55:44:B4:30:C0:A2:B1:AA:BC:B3:8F:BB:D3:B4:76:64:
  • F5:D3:23:6C:02:20:69:11:C1:3A:0F:B1:AE:E3:4E:4C:
  • B0:90:09:AF:3A:73:DD:47:95:D4:6F:BB:45:54:25:94:
  • 56:11:38:B3:BE:EC

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.comellas.dev
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid