DMARC Audit Checklist for Small Businesses

 If you manage a small business and your team relies on email, implementing a DMARC audit is no longer a luxury—it's a core necessity. The latest requirements from Google, Microsoft, and Yahoo demand email authentication or risk your legitimate emails getting blocked or flagged as spam. Beyond compliance, a DMARC audit offers powerful protection against email spoofing, fortifies your brand’s reputation, and ensures critical communications reach your customers’ inboxes without disruption.

As Toronto’s trusted cloud services partner, Interlock IT has guided countless businesses through DMARC audits, configuration, and enforcement. Drawing on our expertise, this guide will walk you through a proven, actionable checklist to help you fix spoofing risks, improve deliverability, and pass all sender requirements—especially if you use Google Workspace or Microsoft 365.

What is a DMARC Audit?

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email security standard that helps protect your domain from being used in phishing or spoofing attacks. A DMARC audit reviews your entire email authentication setup—SPF, DKIM, and DMARC—for gaps, misconfigurations, or risks. For small businesses, this audit is essential to identify weaknesses before they turn costly or result in undelivered communications.

Why is a DMARC Audit Urgent for Small Businesses?

Email providers now require DMARC for senders, especially anyone dispatching large email volumes. Even if you only send a few hundred emails a day, more advanced spam filters make authentication a must for consistent deliverability. Without DMARC, cybercriminals may impersonate your business—eroding trust and causing potential financial harm. Many businesses also remain unaware of hidden authentication issues until their emails begin going to spam or are blocked entirely. Proactively auditing now prevents downtime and future headaches.

10-Step DMARC Audit Checklist for Small Businesses

1. Assess Your Existing Email Authentication

• Review your DNS for existing SPF, DKIM, and DMARC records.
• Document whether your records are present, correct, and aligned across every domain you use for business email.

This step forms your baseline for the audit and reveals typical gaps—like missing DKIM signatures or an incorrect DMARC policy.

2. Inventory All Email Sending Sources

• List your main email platform: Google Workspace, Microsoft 365, or on-premise server.
• Identify third-party apps or services sending email on your behalf (for example: marketing tools, CRMs, invoicing or notification systems).
• Contact each provider to get their official SPF and DKIM requirements.
• Document every domain, service, and method used to send business email.

Missed senders are a frequent cause of failed authentication after DMARC enforcement. Taking a full inventory up front prevents future delivery surprises.

3. Validate and Optimize Your SPF Records

• Ensure all legitimate sources are included in your SPF record.
• Watch for the 10 DNS lookup limit
• Publish the SPF record in your DNS, test for errors, and keep a record of every authorized sender.

Example SPF record for Google Workspace and Salesforce CRM
 v=spf1 include:_spf.google.com include:_spf.salesforce.com ~all

4. Enable DKIM Signing Everywhere

• Enable DKIM in your main business platform’s admin console.
• Request DKIM setup info from any third-party email senders.
• Publish DKIM records to your DNS and confirm alignment with your domain (not subdomain, unless required).
• Establish regular DKIM key rotation.

Proper DKIM setup is vital—many businesses find DKIM is missing for one or more important senders.

5. Publish an Initial DMARC Policy in Monitoring Mode

• Start with DMARC set to monitoring: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
• Publish in DNS for your primary email domain.
• Configure the designated inbox to receive aggregate DMARC reports.

Monitoring mode lets you see authentication reports without any risk of email delivery being affected.

6. Monitor & Analyze DMARC Reports

• Review aggregate reports weekly.
• Identify failed authentication attempts, unauthorized senders, and any anomalies.
• Document trends—such as percentage of email passing DMARC and recurring failures by sender or region.

Many businesses discover unknown email sources or attempts at spoofing during this phase.

7. Fix Authentication Issues Promptly

• For authorized senders with failures, update SPF and DKIM as needed.
• For unknown or malicious sources, take steps to block them and review your app integrations for unused or legacy connections.
• Ensure all changes are retested using monitoring tools and DMARC data.

Closing these gaps is essential before moving to enforcement—prevents business email from being caught in spam or rejected.

8. Plan Out Your Transition to Enforcement

• Once at least 95% of legitimate email passes DMARC in monitoring mode (usually within 60 days), prepare your enforcement timeline.
• Introduce enforcement in stages: quarantine a small percentage, then full; finally reject all non-compliant email.
• Monitor for issues and confirm that business-critical messages deliver reliably at each stage.

This staged approach protects against accidental disruption of legitimate communications.

9. Enforce Gradually: From Quarantine to Reject

• Increase enforcement % over weeks (start with p=quarantine; pct=10, then raise to 50, 100; later switch to p=reject).
• Pause at each step to monitor effects and troubleshoot if needed.
• Update stakeholders about each enforcement stage and any troubleshooting actions.

Give your team time to react and adjust integrations or workflows if something stops working.

10. Maintain Ongoing Reviews and Monitoring

• Set up weekly and monthly checks on DMARC reports, deliverability, spoofing attempts, and changes in your email setup.
• Update your inventory as you add new marketing tools, billing systems, or platforms that send email.
• Review and rotate SPF/DKIM keys and policies periodically to keep protection strong.

Continued vigilance ensures new risks are quickly managed and deliverability remains strong.

Best Practices for a Successful DMARC Audit

• Document every step, including DNS changes, third-party contacts, and internal decisions.
• Assign ownership—designate a person or team to oversee email authentication.
• Test any new service or integration in a staging environment first.
• Communicate changes to your team and educate users on what to expect if DMARC rules block certain emails.
• Lean on a proven expert like Interlock IT when faced with complex configurations or multi-vendor integrations.

Common Challenges and Solutions

• Overlapping or forgotten senders: Vendors and marketing tools often get added without IT oversight. Regular DMARC monitoring surfaces these so changes can be made before disruptions occur.
• Exceeding DNS lookups in SPF: Flatten records or use tools that consolidate multiple vendor IPs when possible.
• Old or non-compliant vendors: Ask vendors about DMARC, SPF, and DKIM alignment support. If they don’t support it, consider replacements.

When to Call in an Expert

Many small businesses manage basic DMARC configuration in-house, but complexity grows as more platforms and providers are added. If you use Google Workspace or Microsoft 365 alongside CRMs, billing systems, or marketing automation software, consider engaging Interlock IT. As a certified deployment partner, we specialize in customized DMARC audits and provide tailored support so you never hit costly deliverability roadblocks. Our approach is always focused on clarity, efficiency, and protecting your brand’s reputation.

Frequently Asked Questions: DMARC Audits for Small Business

What happens if DMARC is not configured?

Emails from your domain may be easily spoofed by attackers, and legitimate marketing or customer emails could be sent to spam, rejected, or not delivered at all—especially by Gmail, Outlook, and Yahoo. This can harm business relationships and compromise your reputation.

How long does a DMARC audit take?

For most small businesses, a full audit and staged DMARC rollout can be completed in 4 to 16 weeks, depending on complexity and how many third-party integrations are involved.

What tools can help with DMARC monitoring?

Automated tools are available to collect, parse, and visualize DMARC aggregate reports, but even simple inbox monitoring is effective for most small businesses. For advanced environments, many businesses turn to Interlock IT for ongoing monitoring services.

Is Google Workspace or Microsoft 365 better for DMARC compliance?

Both platforms offer built-in support for SPF, DKIM, and DMARC, which simplifies compliance. The key is correct configuration across all sending sources—not which provider you use.

How do I know if my emails are being spoofed?

DMARC aggregate reports will show attempts by unauthorized IP addresses to send emails from your domain. Regular monitoring helps you detect and react quickly.

What if a third-party vendor can't support DMARC or DKIM alignment?

You should ask your vendor for a roadmap to compliance. If they cannot provide a solution, it’s best to evaluate alternatives that can help keep your email secure and deliverable.

Conclusion

Proactive DMARC auditing is one of the most impactful ways to increase security, maintain email trust, and ensure continued business growth. At Interlock IT, we’ve seen firsthand how the right DMARC strategy turns email from a risk into an asset. If you’re ready to take the next step, need help with complex setups, or want full confidence passing sender requirements, connect with our cloud services team today. Together, we’ll ensure your business communications are secure, delivered, and trusted—every time.

DMARC Enforcement in 2026: When to Move From p=none to Quarantine or Reject

 By 2026, DMARC enforcement has shifted from an industry recommendation to an operational necessity, especially for small and medium-sized businesses using platforms like Google Workspace and Microsoft 365. Email providers—including Google, Microsoft, and Yahoo—now consider DMARC policies essential for both email delivery and brand security. If your organization still operates with a p=none DMARC policy, it’s time to advance: the risk of email spoofing, phishing, and rejected legitimate messages has never been higher. The strategic move from monitoring (p=none) to active enforcement (quarantine or reject) is no longer optional in a landscape of evolving cyber threats and compliance expectations.

The right timing for advancing your DMARC policy is clear: once you’ve mapped all email sources and achieved high authentication pass rates, transitioning to p=quarantine, and ultimately p=reject, will maximize your protection without sacrificing deliverability. Businesses partnering with Interlock IT receive expert-guided audits and tailored recommendations that minimize risk and disruption—well aligned with Google Workspace and Microsoft 365 integrations.

Understanding DMARC Enforcement in 2026

DMARC (Domain-based Message Authentication, Reporting, and Conformance) unifies SPF and DKIM email authentication techniques to verify sender legitimacy. It prevents common attacks such as email spoofing and business email compromise (BEC) by expressing a clear policy to receiving servers on how to handle unauthenticated messages. The three primary policy modes are:

• p=none: Monitoring only. No action is taken on failing emails.
• p=quarantine: Suspect messages go to spam or quarantine folders.
• p=reject: Failing emails are outright rejected by recipient servers.

Email providers in 2026 expect organizations to rapidly progress from p=none to quarantine or reject. Monitoring-only setups are now synonymous with inadequate security, and senders who don’t enforce risk degraded reputation and potential blocking.

Concise Definition: What is DMARC Enforcement?

DMARC enforcement is the process of instructing receiving mail servers how to handle emails that fail SPF or DKIM authentication, typically through the policy in your DNS record. While p=none collects data on authentication failures, p=quarantine and p=reject actively prevent unverified (and likely malicious) emails from reaching inboxes.

When to Move Beyond p=none
Your organization should advance from p=none to a stricter policy when:

• You have identified and validated all your legitimate email-sending sources (marketing tools, CRMs, automated platforms).
• SPF and DKIM alignment is above 90% for all outgoing mail.
• You have confirmed, via DMARC aggregate reports, that unauthenticated emails reflect only malicious or unauthorized sources—never mission-critical business emails.
• You are ready to systematically test stricter enforcement (using pct tag to phase in quarantine/reject gradually).

This approach ensures smooth email delivery while securing your domain against phishing attempts and spoofing. Our complimentary DMARC audit can quickly clarify your exact risk profile and readiness for enforcement.

Transitioning from p=none to Quarantine or Reject

1. Map Your Email Ecosystem
   Identify every email source (Google Workspace, Microsoft 365, CRM systems like Copper or Xero, helpdesk platforms such as Hiver). List all sending domains/subdomains, including those used by third-party vendors.
2. Enable DMARC Reporting
   Add the rua tag to your DMARC record for aggregate reports. Review data for at least 14 days to recognize all authentic senders and sources.
3. Align SPF and DKIM
   Correct misalignments that can cause legitimate mail to fail DMARC. Update SPF records to include all senders. Ensure DKIM is configured per domain and platform. This step may involve technical adjustments that Interlock IT regularly handles for clients on both Google Workspace and Microsoft 365.
4. Test with Quarantine (p=quarantine; pct=10)
   Begin with a small percentage (e.g., 10%) of traffic under quarantine. Monitor closely for issues, particularly around transactional and operational messages. Gradually increase pct until all legitimate traffic passes without being quarantined.
5. Move to Reject (p=reject)
   When 100% of legitimate emails are successfully authenticated under quarantine, confidently switch to reject. Continue to monitor aggregate (rua) and forensic (ruf) DMARC reports for ongoing assurance.
6. Continuous Monitoring and Maintenance
   Changes in emailing systems, acquisitions, or third-party app adoption may require new SPF or DKIM updates. Quarterly reviews are best practice, and outages can be avoided through proactive audits, like those offered by Interlock IT.
   
   

Key Risks to Avoid

• Switching to quarantine or reject too quickly: This can result in blocked business emails or failed communication with customers and partners. A phased approach, increasing enforcement over 8-12 weeks, is essential.
• Inconsistent SPF or DKIM alignment: Ignoring subdomain mail sources or new tools can break alignment. Forwarding services can alter headers and cause DKIM to fail. Consider ARC headers for forwarding scenarios if needed.
• Missing senders in DMARC reports: Leaving out the rua tag or not reviewing reports thoroughly can cause legitimate sources to be inadvertently rejected.

Interlock IT’s DMARC audits are designed to systematically catch these issues before moving your policy beyond p=none.

Best Practices for DMARC Enforcement

• Start with a comprehensive audit of your email systems and third-party integrations.
• Gather at least two weeks of DMARC aggregate reports before making any changes.
• Align SPF and DKIM for all sending tools. This includes sales/planning tools like Copper CRM, billing systems like Xero, and support platforms like Hiver.
• Use the pct tag for phased deployment of quarantine or reject. This minimizes the impact of overlooked configuration issues.
• Review your domain's DMARC performance quarterly and after any major business system changes.
• Partner with experts who understand both technical implementation and business impact, such as Interlock IT.

Frequently Asked Questions

What happens if I never move beyond p=none?

Your domain remains vulnerable to spoofing and phishing attacks. Many providers will treat your emails with suspicion, damaging your brand reputation and reducing deliverability, especially for bulk and marketing messages.

How often should my organization review its DMARC setup?
Quarterly reviews are recommended, as well as after any major changes to IT infrastructure, new marketing platforms, or third-party connections. Interlock IT offers ongoing audits to ensure compliance and protection.

What’s the risk of moving to p=reject too quickly?
Jumping straight to reject can inadvertently block business-critical email, especially if legacy senders or third-party platforms aren’t properly authenticated. A phased, data-driven approach minimizes that risk.

Can I use DMARC without SPF and DKIM?
No. DMARC relies on both SPF and DKIM as underlying authentication protocols. Both must be set up and aligned with your sending domains for DMARC policies to function properly.

How do I see what sources are sending email from my domain?
Enable DMARC aggregate reporting (rua tag) and regularly review the reports. Interlock IT guides organizations through interpreting this data and acting on it efficiently.

Why choose Interlock IT for DMARC deployment and ongoing management?
As a specialist cloud partner for Google Workspace and Microsoft 365, Interlock IT offers deep technical experience combined with business consulting expertise (led by a CPA). We’re focused on Ontario-based SMBs and deliver cost-effective, reliable audits, migrations, and continuous support.

Conclusion: Secure Your Email and Protect Your Brand

In 2026, businesses must treat DMARC enforcement as a core pillar of email and brand security. Proactively advancing to p=quarantine and ultimately p=reject ensures you stay ahead of evolving threats, compliance shifts, and customer expectations. With Interlock IT’s expertise, you can confidently upgrade your DMARC posture, knowing every sender, integration, and process is accounted for—from CRM to accounting and support desk platforms.

If you’re ready to move your DMARC policy to the next level or want to ensure you’re not at risk, contact Interlock IT for a complimentary audit and experienced guidance on Google Workspace, Microsoft 365, and all facets of cloud email security.

Is Your Domain 100% Secure? A Look Under the Hood

When your email is working fine and your website is live, it’s easy to assume your domain is in order. But as a Google Workspace and Microsoft 365 partner, we spend a lot of time looking "under the hood" of business domains, and what we find is often surprising.

Even for businesses that seem perfectly secure, there are almost always invisible gaps that hackers can exploit. This is where DMARC (Domain-based Message Authentication, Reporting, and Conformance) comes in.

To show you why this matters, let’s look at what we typically find when we begin monitoring a new client’s domain.

1. The "Compliance" Gap

Most business owners assume security is an all-or-nothing game. However, a domain audit often reveals a "Compliance Gap."

We recently monitored a domain that appeared to be doing well with a 95.8% compliance rate. In a school grade, that's an A+. But in cybersecurity, that remaining 4.2% non-compliance represented thousands of emails being sent without proper "ID cards."

These are the emails hackers use to spoof your identity, pretending to be you to trick your customers or vendors into changing payment details or clicking malicious links.

2. The "Deliverability" Gap

This isn't just about hackers; it’s about your own legitimate business tools.

Most modern companies use a mix of services—Outlook for daily mail, Salesforce for CRM, or Mailchimp for marketing. Each of these services needs permission to "speak" on behalf of your domain.

When we audit these services, we often find "Red Bars" in the data. This means a service you pay for is failing security checks. When that happens, providers like Google and Yahoo don't just get suspicious—they send your invoices and project updates straight to your recipient's Spam folder.

DMARC is the Shield

At Interlock IT, we are now recommending a DMARC rollout for all our clients to close these gaps for good. Here is how it protects you:

• Preventing Identity Theft: We move your domain to a "Quarantine" or "Reject" policy. This creates a security gate. If an unauthorized person tries to send an email as you, it’s either blocked entirely or tossed into the junk folder before it can do damage.

• Maximizing Inbox Delivery: We align all your third-party tools (like Klaviyo or Zoho) so that big email providers trust your mail. This ensures your legitimate business emails land in the primary inbox, not the junk folder.

• Total Visibility: You get monthly audits that identify exactly who is sending mail to your domain.

Implementation: Doing it Right

DMARC is a powerful tool, but it's a precision instrument. If it’s set up incorrectly, you can accidentally "lock yourself out" and block your own legitimate emails.

We handle the configuration, testing, and final "lockdown" for a standard one-hour consulting fee (typically around $175). It’s a small investment to ensure your domain is no longer a target.

Is your domain truly secure? Reach out to us for a quick audit. We’ll take a look under the hood and show you exactly where your gaps are before a scammer finds them first.

The Most Popular Brand of 2026 is Microsoft (But Only for Scammers)

 If you check your spam folder right now, it is almost guaranteed what you’ll see: an "urgent" alert from Microsoft. Maybe it says your storage is full, your password expired, or there was a "suspicious login" from another country.

According to the latest Q4 data from Check Point Research, Microsoft is once again the most impersonated brand in the world, accounting for 22% of all phishing attempts globally.

Well, this does not come as a shock. Microsoft and Google (which took second place at 13%) aren't just tech companies, they are the "keys to the kingdom." If a scammer gets your Microsoft login, they don’t just get your email—they get your files, your company’s internal directory, and your identity.

Why These Scams are Actually Working

It’s easy to joke that nobody falls for these, but the reality is that today's attacks are polished, psychological, and incredibly sneaky.

1. The "Lookalike" Trap

One of the sneakiest tactics right now involves "lookalike" domains. Scammers register websites using characters from different alphabets that look identical to the original website. To a computer, a Cyrillic "а" is completely different from a Latin "a," but to your eyes in an address bar, micrоsoft.com looks exactly like the real thing. 

2. Targeting the Kids

One of the most concerning trends we’re seeing is scammers targeting younger audiences through platforms like Roblox. They create fake game pages (like the recent "Skibidi" themed scams) that look identical to the real platform. If they can trick a child into "logging in" to a fake page, they’ve stolen a family's credentials before the parents even know what happened.

3. Exploiting Busy Season

Amazon jumped to the #3 spot recently, fueled by the holiday shopping rush. Scammers know when you’re busy, distracted, and expecting a delivery notification. That’s when they strike.

How to Protect Your Team 

We tell our clients that while software helps, the best defense is a healthy dose of skepticism. Here’s how to stay safe:

• Stop the "Urgency" Reflex: If an email screams that your account will be "deleted in 24 hours," it’s almost certainly a scam. Legitimate companies rarely use that kind of aggressive pressure.
• Look at the Sender, Not the Name: Anyone can change their "Display Name" to say "Microsoft Support." Click on the name to see the actual email address behind it. If it’s support@microsft-security-update.net, delete it.
• Go to the Source: If you’re worried about your account, don't click the link in the email. Open your browser, type office.com or google.com yourself, and log in there. If there's a real problem, you'll see a notification in your dashboard.
• Use an Authenticator App: SMS-based codes are better than nothing, but they can be intercepted. Use an app like Bitwarden or Microsoft Authenticator for a much higher level of security.

Stopping "Spoofing" with DMARC

While training your team to spot these red flags is vital, there is a powerful technical shield that many businesses are still missing: DMARC (Domain-based Message Authentication, Reporting, and Conformance).

Without DMARC, an attacker with enough skill can send an email that literally appears to come from your address. This is called "spoofing." Imagine a vendor or customer receiving an email from your real address asking them to update their payment details to a new, fraudulent account. Even though you didn't send it, the damage to your reputation and business relationships can be irreparable.

By implementing DMARC, we ensure that:

• Spoofing is Neutralized: Any unauthorized use of your domain is clearly marked, so it gets filtered out before it ever reaches your clients or vendors.
• Deliverability is Guaranteed: Major services like Google, Microsoft, and Yahoo are increasingly blocking emails from domains that don't have these security protocols in place.
• You Get Insight: DMARC generates reports showing exactly who is sending mail on your behalf—identifying both legitimate tools and illegitimate attackers.

The Bottom Line

Phishing works because it exploits our familiarity with the brands we use every day. Our goal at Interlock IT is to build the technical barriers, like DMARC, that keep these threats out—while also arming your team with the knowledge to spot the one or two that inevitably slip through the cracks.

Is your team ready to spot a homoglyph attack? And is your domain protected against spoofing? We specialize in DMARC implementations and securing digital identities. 

Reach out to us for a comprehensive security checkup today.

Finally! You Can Soon Fix That Professional "Identity Crisis" on Gmail

We’ve all seen them—and maybe some of us still own them. Email addresses created in high school or during a weekend whim that seemed like a good idea at the time, but now look a bit out of place in a professional setting.

For years, if you wanted to change your @gmail.com address, you were stuck between a rock and a hard place. You either lived with the embarrassing name or went through the absolute nightmare of creating a new account and manually migrating years of emails, photos, and app integrations.

According to a recent update from Google’s support pages, that’s finally about to change.

What’s Changing?

Google is quietly rolling out a feature that allows users to replace their existing Gmail address with a new one while keeping every single piece of data intact. This isn’t just adding a nickname or a simple alias; it’s a full account transition that doesn't require you to start from scratch.

The Highlights:

• Your data stays put: Your Google Photos, Drive files, and even your YouTube watch history move over automatically. No manual migrations required.
• The "Safety Net" alias: Your old address doesn't just vanish. It stays active as an alias, so if a client emails your old name, it still lands in your new, professional inbox.
• No login headaches: You can still use the original address to sign into your account if you forget the new one.

Why This Matters for Your Professional Brand

In business, your email is often the first thing a person notices. While we always suggest getting a custom domain (like name@yourcompany.com) for the best branding, we know plenty of freelancers and small business owners who run everything through Gmail.

Being able to "professionalize" an old account without losing a decade of archived data is a massive win for productivity.  It saves you what we call the "migration tax"—those three or four hours of tedious labor usually spent trying to move data between accounts without breaking anything.

The Catch (And There's Always a Catch)

Before you go hunting through your settings, keep two things in mind:

First, this is a slow rollout. It first appeared on Google's Hindi support pages, which usually means they are testing it in specific markets before a global launch. If you don't see the option yet, just sit tight—it’s coming.

Second, Google is enforcing a 12-month rule. Once you pick a new address, you are locked in for a full year. You won't be able to change it again during that time, and you can't delete the new address once it's set.

The Interlock Take

At Interlock IT, we love seeing these kinds of updates because they remove a "friction point" that has annoyed users for nearly twenty years.

If you’ve been dreading an email cleanup because you were scared of losing your data, your window is finally opening. Keep an eye on your account settings, and once this hits our region, we highly recommend taking ten minutes to finally retire that old handle for good.

Need a hand managing your team’s email or moving to a more secure, professional setup? Reach out to us—we handle the technical heavy lifting so you don’t have to.