What Requires Attention
The BIG Questions
Domain Overview
Technical Findings
Email Authentication
Mail Transport Security
DNS Security
Brand & Certificate Controls
Priority Actions 4 total Achievable: Low Risk
Change your DMARC policy from p=none to p=quarantine (then p=reject). Review your DMARC aggregate reports first to ensure legitimate senders pass authentication.
Publish an MTA-STS DNS record and host a policy file at https://mta-sts.ietf.org/.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 web services (HTTPS). Your email transport already uses DANE, which validates mail server certificates via DNSSEC without relying on CAs — so CAA is primarily relevant to your web-facing certificates.
Your domain has DNSSEC + DANE — the strongest email transport security available. TLS-RPT adds operational visibility by reporting when sending servers fail DANE validation or encounter STARTTLS issues delivering to your MX hosts. It does not add security — it monitors the security you already have.
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.
4a9f715b0535c050ff0e9e724cac014566540778dcd4b6b9d4331d87de59d25e474c34fceccdfb3edf9cac039716e60fa17006842f78dc29686ca1e753b632f7