TLS/STARTTLS check malfunction #138
Comments
|
I have the same problem and I believe the issue is related to SSL certificate verification. I just ran a quick test by temporarily disabling hostname verification and certificate verification, and the result is correct. |
seanthegeek
added a commit
that referenced
this issue
Jul 16, 2024
- Fix TLS/STARTTLS check (Fixes issue #138) - Consider `tls: true` if `starttls: true` - Handle records not existing if ignoring unrelated records (PR #131 fixes #130) - Query the base domain if a DMARC record is not found at the subdomain (PR #132) - Do not accept `include=` in the SPF record (PR #134 fixes issue #134) - Fix DNSSEC cache (PR #136 Fixes issue #137) - Fixed checking whether there is some text after `all` SPF directive (PR #139)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
While scanning the MX Domains of google.com with the command
checkdmarc google.com, the output shows that starttls is not supported, as seen in the screenshot belowOther online ssl-tools like ssl-tools.net show that starttls is supported on the
smtp.google.comdomain.The text was updated successfully, but these errors were encountered: