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
Add a rua= tag to your DMARC record to receive aggregate reports about authentication results. Without reporting, you cannot see who is sending email as your domain or whether legitimate mail is failing authentication.
Publish an MTA-STS DNS record and host a policy file at https://mta-sts.blauw.com/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.
Your DMARC policy is quarantine — spoofed messages are flagged. Upgrading to p=reject blocks them entirely. Review aggregate reports to confirm legitimate senders are aligned.
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.
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.
f58b1c06e38595ad47c20352784c30cbbeb8ff50ee1ee03c28481339438506ca468d838cb4c10c0e60f6f2b4487ac85dc9d6fad3916436d3ef50780f84585651