
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: SECURE
Publish an MTA-STS DNS record and host a policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.
DKIM is only configured for third-party services, not your primary email platform (Google Workspace). Enable DKIM signing in Google Workspace settings to cover all outbound mail.
Rotate your DKIM keys to use 2048-bit RSA. Most email providers support this in their admin console.
Publish a TLS-RPT DNS record to receive reports about TLS delivery failures to your domain.
Since DNSSEC is already active, you can add TLSA records for your MX hosts to enable DANE. This cryptographically pins TLS certificates for mail delivery.
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.
11b8c28a8164a94e61f5921c8b3e62eda73cb76f666e39e6fdf9975671489f578e68bc710c6cea0a7fc9f62e609f5a4428fca06cdeddaf90b6c0ae29d70adef5
