Most owners look up DMARC Canada guidance the morning a client forwards an invoice that shows their own domain in the From line and that nobody in the office sent. The banking details are new. The client wants to know whether to pay.
That is how most Toronto firms meet this subject. Nobody plans an email authentication project. A forged message reaches a customer first, and the questions start afterward.
Here is the part people get wrong. Having a DMARC record is not the same as being protected. A record set to p=none asks receiving mail systems to deliver every message, forged ones included, and a domain can sit at that setting for years.
Why Anyone Can Send Email as Your Domain
Email was built without a check on the From line. The Canadian Anti-Fraud Centre describes the result on its spear phishing page: the sender’s address appears to be the actual email address of the source the fraudster is pretending to be, a tactic known as spoofing.
The same page lists the versions that reach businesses. In the supplier swindle, a spoofed email tells a business that payment details have changed and provides new banking information. In the payroll spoof, an email that appears to come from an existing employee asks for a change to direct deposit information.
Size does not keep a domain off the list. In its work on Government of Canada domains, the Canadian Centre for Cyber Security says it has observed a continuous low level of spoofing affecting seemingly any domain with a web or DNS presence. Its implementation guidance says this activity is not assessed to be targeted and should be expected for any domain.
What the DMARC Canada Guidance Says
The main DMARC Canada guidance is a public document from the Canadian Centre for Cyber Security, Implementation guidance: email domain protection, numbered ITSP.40.065 v1.1. It took effect on August 12, 2021. It is written for system owners who want to protect their domains from email spoofing.
It names three protocols that act jointly:
- SPF, the Sender Policy Framework: a DNS record that lists the IP addresses allowed to send email on your domain’s behalf.
- DKIM, DomainKeys Identified Mail: a cryptographic signature on each message, checked against a public key you publish in DNS.
- DMARC, Domain-based Message Authentication, Reporting, and Conformance: a DNS record that tells receiving systems what to do when a message fails, and gives them a way to report back to you.
The guidance is blunt about the first two on their own. It says SPF and DKIM share a limitation that makes them ineffective against moderately sophisticated threat actors, because both rely on domain names that are hidden from the user and can differ from the domain displayed in the From field.
DMARC closes that gap with alignment. According to the guidance, for an email to pass DMARC validation it must pass either SPF or DKIM, and the domain used in those checks must align with the one in the From field.
The three policies
When a message fails, the receiving system applies the policy in your DMARC record. ITSP.40.065 describes the three options this way:
- None: the email is delivered. This is monitor only.
- Quarantine: the email is delivered but is marked as suspicious.
- Reject: the email is rejected.
Then comes the sentence that matters most. The Canadian Centre for Cyber Security says policies of none and quarantine can help you gather information and configure your systems, but only a policy of reject at 100% will prevent all illegitimate messages from being delivered.
DMARC Canada Requirements for Federal Departments
There is a written DMARC Canada requirement, and it is addressed to federal departments. The Government of Canada’s Email Management Services Configuration Requirements tell departments to ensure that the sender or recipient of government email can be verified using SPF, DKIM and DMARC.
The list is short and specific. Departments need a minimum DMARC policy of p=none with at least one address defined as a recipient of reports, and then a policy of p=quarantine or p=reject applied in a phased manner. They must also authorize all sending IP addresses in SPF, apply DKIM signatures to all outbound messages, and add the Canadian Centre for Cyber Security as an aggregate report recipient.
Those requirements are written for departments, not for private companies. They are still a fair benchmark. This is the bar the federal government set for its own mail, and you can hold your domain against it when a customer asks what you do about spoofing.
The Standard Changed in May 2026
Many explanations of DMARC still describe RFC 7489, the March 2015 document that the Canadian guidance cites as its formal definition. The RFC Editor’s record for RFC 7489 now marks it obsolete. Its replacement, RFC 9989, was published in May 2026 as an Internet Standards Track document of the Internet Engineering Task Force.
Three points in RFC 9989 matter to a business owner:
- The percentage tag is gone. The old pct tag asked receivers to apply a policy to a share of failing mail. RFC 9989 says operational experience showed the tag was usually not accurately applied unless the value was 0 or 100, and it introduces a test mode tag named t in its place.
- Reject needs DKIM. The RFC says domains that publish p=reject must not rely solely on SPF and must apply valid DKIM signatures to their messages.
- Mailing lists need care. The RFC says domains whose users might post to mailing lists should not publish p=reject. Any that still want to should first publish p=none for at least a month, then p=quarantine for an equally long period, and compare the results.
The DMARC Canada guidance predates this change, and its sample records still show pct=100. The order it teaches is none, then quarantine, then reject, and RFC 9989 describes the same order.
A DMARC Canada Checklist for a Small Office
ITSP.40.065 lays the work out in four phases: assess, deploy, enforce and maintain. This DMARC Canada checklist follows that order.
- List every domain and every sender. The guidance starts with all domains and subdomains your organization sends email from. Add every outside service that sends as you, such as invoicing, payroll and newsletters.
- Publish a first DMARC record at p=none. The guidance says you can do this even before deploying SPF or DKIM, that the record does not impact mail delivery, and that aggregate reports should begin to arrive within 24 hours. It recommends a dedicated mailbox for them instead of a named individual.
- Read the reports and sort the senders. The guidance sorts outside sending addresses into authorized senders, forwarders or relays, and possible spoofing. Aggregate reports come in XML, and it says they should be processed by an automated system.
- Publish SPF and turn on DKIM for every sender. Watch the SPF limit of 10 DNS lookups per record. The guidance warns it can be exceeded by accident when third party records are referenced.
- Move to quarantine, then to reject. At each stage the guidance asks you to monitor the reports, confirm that legitimate messages are not quarantined, correct any errors, and only then progress.
- Protect the domains that send nothing. The guidance recommends SPF and DMARC records on non-mail domains, set so that any message claiming to come from them is rejected.
- Keep it maintained. Monitor the reports for new senders and a rise in failures. The guidance also says to rotate DKIM keys annually and to confirm that third party senders do the same.
One caution from the same document. It does not recommend requesting forensic reports, which are copies of failed messages, because they may contain personally identifiable information.
What DMARC Does Not Stop
Following the DMARC Canada guidance to the end still leaves two gaps. DMARC protects the exact domain in the From address and nothing else.
The first gap is the display name. RFC 9989 says display name attacks, where a well-known name sits in front of an arbitrary address, are out of scope for DMARC. The second is the lookalike domain, which the Canadian Centre for Cyber Security’s phishing guidance calls typo squatting: domain names registered as common misspellings of well-known websites.
So the human check stays. That phishing guidance reminds staff that addresses can be spoofed and that a known sender is not necessarily a trusted sender. For an unusual request, the Canadian Anti-Fraud Centre says to look up the person’s email or phone number in your work’s directory and verify with them.
The Evidence Question
The gap is rarely knowledge. Many owners have already heard that they should have DMARC. What they cannot do is show, today, what policy the domain publishes, which services send in its name, and when the reports were last read.
That proof is simple to hold once the work is done. The record is public in DNS, the policy is one line, and the report history lists the sources that used your name. When a customer’s security questionnaire asks about spoofing, you answer with the record and the date you reached reject.
Where Secur-IT Data Fits
Our email security service includes domain authentication with SPF, DKIM and DMARC to stop attackers spoofing your domain. It also covers advanced threat filtering, impersonation and business email compromise protection, and user awareness, which are the layers DMARC leaves open.
If you want the wider picture first, our guide to email security in Canada explains how phishing and business email compromise work.
For small offices, the questionnaire-based assessment is free. On-site assessment is quoted after a short scoping call.
Frequently Asked Questions
Q: What is the DMARC Canada guidance?
The main DMARC Canada guidance is ITSP.40.065 v1.1 from the Canadian Centre for Cyber Security, in effect since August 12, 2021. It explains how to implement SPF, DKIM and DMARC, and it says only a reject policy applied to all failing mail will prevent all illegitimate messages from being delivered.
Q: Is DMARC mandatory in Canada?
The DMARC Canada requirements published on canada.ca are addressed to federal departments. They call for SPF, DKIM, and a DMARC policy that starts at p=none and moves to p=quarantine or p=reject in a phased manner. Private businesses can use them as a benchmark.
Q: Does a p=none record protect my domain?
No. The Canadian Centre for Cyber Security describes none as monitor only, which means the email is delivered. It is the right first step because it starts the reports, and the wrong place to stop.
Q: Is RFC 7489 still the DMARC standard?
No. The RFC Editor marks RFC 7489 obsolete. RFC 9989, published in May 2026 as an Internet Standards Track document, replaces it and removes the pct tag.
Q: Does DMARC stop all phishing?
No. RFC 9989 says display name attacks are out of scope for DMARC, and a lookalike domain is a different domain from yours. Filtering and staff verification still have to cover those.
If you want to know what your domain publishes today and which services send in your name, our team at Secur-IT Data can walk you through it.
References
- Canadian Centre for Cyber Security: Implementation guidance, email domain protection (ITSP.40.065 v1.1)
- Government of Canada: Email Management Services Configuration Requirements
- Internet Engineering Task Force: RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC)
- Canadian Anti-Fraud Centre: Spear phishing
- Canadian Centre for Cyber Security: Don’t take the bait, recognize and avoid phishing attacks (ITSAP.00.101)
Ready to Strengthen Your Cybersecurity?
Secur-IT Data Solutions is a Toronto-based MSSP providing enterprise-grade cybersecurity for Canadian businesses. Whether you need OT security, AI threat protection, penetration testing, or full managed security services, our team is ready to help.
Talk to our team:
- 📞 Call us: +1 (647) 948-6768
- 📧 Email: info@securitdata.ca
- 🌐 Book a scoping call →

Krikor Tengerian is the CEO and founder of Secur-IT Data Solutions, a Toronto-based cybersecurity firm focused on helping Canadian organizations secure their infrastructure and critical systems. With over 25 years of experience across cybersecurity and IT infrastructure, he has supported organizations in hardening networks, protecting critical workloads, and aligning security controls with business and regulatory requirements.
Krikor actively shapes the direction and themes of Secur-IT’s educational content, collaborating with AI tools to structure, refine, and expand articles while providing the real-world context, use cases, and review to keep them accurate and practical for readers. He regularly shares insights on OT security, threat detection, incident response, and Canadian cybersecurity compliance to help industrial and commercial organizations better understand and reduce their cyber risk.




