Domain without SPF and DMARC records
SPF says which servers may send mail for your domain; DMARC tells receivers what to do when a message fails SPF/DKIM alignment and gives you reporting. Missing either leaves your domain easy to spoof.
Why it matters
Attackers forge email 'from' your domain for phishing and invoice fraud; without DMARC enforcement, receivers have no instruction to reject it.
A missing or weak DMARC policy also hurts deliverability — legitimate mail is more likely to land in spam.
How to check for it
- dig TXT yourdomain.com for an SPF record (v=spf1 …) and dig TXT _dmarc.yourdomain.com for a DMARC record.
- Check that DMARC isn't stuck at p=none long-term and that SPF lists all senders.
How to fix it
- Publish an SPF record listing your senders, set up DKIM signing, then add DMARC starting at p=none with rua reporting.
- Review reports, then move DMARC to p=quarantine and finally p=reject once legitimate mail passes.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- What's the difference between SPF, DKIM and DMARC?
- SPF authorises sending servers, DKIM signs the message, and DMARC ties them to your domain and tells receivers what to do on failure — you want all three.