What Requires Attention
The BIG Questions
Domain Overview
Technical Findings
Email Authentication
Mail Transport Security
DNS Security
Brand & Certificate Controls
Priority Actions 5 total Achievable: Low Risk
Publish an MTA-STS DNS record and host a policy file at https://mta-sts.example.com/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.
Publish CAA DNS records to restrict which Certificate Authorities can issue TLS certificates for your domain. Specify your preferred CA (e.g., letsencrypt.org, digicert.com). CAA is advisory — CAs must check it before issuing, but absence means any CA can issue.
TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain. Helps diagnose MTA-STS and STARTTLS issues.
DNSSEC is already enabled — you can strengthen email transport security by publishing DANE TLSA records. DANE binds your mail server's TLS certificate to DNS, preventing man-in-the-middle attacks on SMTP connections.
Publish a BIMI DNS record pointing to your brand logo (SVG Tiny PS format). For full support in Gmail, you will also need a Verified Mark Certificate (VMC).
Appendix — Additional Resources
Full technical details including raw DNS records, DKIM public keys, IP/ASN mappings, resolver consensus evidence, and verification commands are available in the Engineer's DNS Intelligence Report.
Verify Report Integrity SHA-3-512 Has this report been tampered with? Verify below
Tamper-evident fingerprint binding this analysis to its data, domain, timestamp, and tool version.
6b02b5ed485acd091bafd7bb9acbc97144388033013b787634817182e0d728674560bf0f620c4de090b7c137afc337dd4fecbc8bc25888223c69695e0ef2a288