How to Update Your DMARC Policy
What DMARC does, how quarantine and reject differ, and how to update the DNS record so spoofed email using your domain gets blocked.

Email is still how most business gets done, and it's still how a lot of attacks arrive. Federal cybersecurity agencies have repeatedly urged email users and administrators to update their DMARC policy. Major mailbox providers like Google have also tightened the rules they apply to inbound mail. If you want your real messages delivered and your brand protected from impersonators, your domain needs authentication.
What DMARC is
DMARC (Domain-based Message Authentication, Reporting and Conformance) is an email validation system. It protects domain owners from spoofing and phishing. You publish a policy in your domain's DNS records. That policy says which mechanisms, such as SPF and DKIM, authenticate your email, and how receiving mail servers should treat messages that fail those checks.
Two policy settings matter most:
- v=DMARC1; p=quarantine: the receiving server quarantines email that fails DMARC validation and treats it as spam.
- v=DMARC1; p=reject: the receiving server rejects and blocks email that fails DMARC checks.
Why the policy matters
A properly configured DMARC policy cuts the risk of spoofing and phishing. Here's what that looks like day to day.
Phishing often depends on faking a trusted domain. With a correct policy, only legitimate mail from your domain reaches your recipients' inboxes, so fewer of those attempts work.
Your brand is on the line too. If attackers send fraudulent messages that appear to come from your domain, customers blame you. A strict policy limits how much anyone else can use your name.
And deliverability improves. Email providers are more likely to trust and prioritize mail from domains with strong authentication, so your legitimate messages are more likely to land where they should.
Updating your DMARC policy
You can usually do this in your domain's DNS settings. The steps:
- Check your domain's DNS records to see whether a DMARC policy already exists. If there isn't one, create it.
- Decide between "quarantine" and "reject." Reject gives the highest level of protection because it blocks messages that fail. Quarantine still offers solid protection by sending suspicious email to the spam folder.
- Open your domain's DNS settings and update the DMARC record. A record with a "reject" policy might look like this: "v=DMARC1; p=reject; rua=mailto:your-email@example.com".
- Watch what happens afterward. The "rua" tag sends you reports on email authentication results, and you can use them to adjust the policy as needed.
Who should make the change
If you run a custom email domain, bring in your IT team or web hosting company. They know how to set the policy correctly and check that it's protecting your domain. If you use a web-based email service like Gmail, the provider manages these settings, so you don't need to do anything.
Email authentication is only one piece of your security. Phishing and impersonation reach your team through other channels too, including voice. While you're tightening things up, read our guides on VoIP security measures that safeguard your conversations and why default cybersecurity settings can be dangerous. You can also browse the full security and IT blog for more practical advice.
Your phone system
DMARC protects your email, and the way you handle inbound calls protects your customer conversations. CallSprout is a cloud business phone system built on a 99.999% uptime network, so the calls your customers rely on are always answered. Our AI Voice Agent picks up every call, transcribes the conversation and routes callers based on what they need and what your CRM already knows about them. That means fewer missed opportunities and a consistent first impression. You can see how the platform and reliability hold up under real-world traffic.
Connected-system features work through your existing CRM or business system and depend on that system offering a compatible API. Availability varies by provider.
Do it before something happens
Don't wait for a breach to find out your domain was open to spoofing. Check your DMARC record this week and update it if it's missing or weak. When you're ready to give your phone calls the same attention, talk to the CallSprout team.


