← Back to the security guide
Email Spoofing ProtectionHigh risk
SPF record is missing
What does this mean?
Without an SPF record, mail servers receiving email that claims to be "from" your domain have no way to verify it was actually sent by a system you authorized. That makes it easier for scammers to send convincing phishing emails that appear to come from your company.
What are the potential impacts?
- Scammers can send phishing emails that appear to come directly from your company's domain, with no technical hurdle stopping them.
- Employees, customers, and vendors targeted this way often trust the email because it looks like it's really from you, leading to wire fraud, credential theft, or malware installed on a partner's machine.
- Even if you never notice the abuse yourself, your domain's reputation with mail providers can degrade, eventually causing your own legitimate emails to land in spam.
How to fix it
Add a TXT record at your domain's root (not a subdomain) listing which mail servers are allowed to send on your behalf — for example, v=spf1 include:_spf.google.com ~all for Google Workspace. This gets added wherever your domain's DNS is managed; look for "DNS records" or "TXT records" in that dashboard.
Want to see whether this actually affects your site? Run a free scan — no signup required.
Run a free scan