What the standard says
DMARC, SPF and DKIM protect your exact domain. The DMARC standard says it can only be used to combat specific forms of exact-domain spoofing, and that it does not address visually similar domain names or the display name people see in their inbox [1]. A DMARC pass only shows that the sender was allowed to use that domain [1]. Someone who registers a near-copy of your domain owns that copy, so they can set up its email and its own checks, and those messages can pass.
The FBI says scammers use slight variations on legitimate addresses so a fake account looks real [2]. The FTC says a scammer sets up an email address that looks like it’s from your company [3]. This falls under business email compromise, which the FBI’s Internet Crime Complaint Center (IC3) describes as a scam aimed at businesses that work with suppliers or regularly send wire transfers, carried out through tricks or break-ins to move money without permission [4]. The common version is a fake invoice, or a note saying a vendor’s bank account has changed.
The official advice is mostly about habits.
Verify by phone. The FBI says to verify payment requests in person or by calling, using a number you look up yourself, not one the message gives you [2]. It also says to confirm any change in account number or payment procedure with the person making the request [2]. IC3 says to use a secondary channel to verify account change requests [5].
Train staff. The FTC recommends teaching staff to spot phishing as part of regular training [3].
Turn on outside-sender warnings. In Microsoft 365, external sender identification adds an External label to messages from outside your organization [6]. Microsoft’s first contact safety tip warns people when they get email from someone they don’t usually hear from [7]. Microsoft’s domain impersonation protection, part of Defender for Office 365, looks for domains slightly similar to yours, but no domains are protected until someone adds them [7]. In Google Workspace, external recipient warnings are on by default and show a banner when someone replies to an outside sender [8].
Report the domain. ICANN, which oversees domain registrars, says to report phishing domains to the registrar first [9]. Registrars must take reasonable and prompt steps to investigate abuse reports [10].
Act fast if money moves. IC3 says to contact your bank right away to request a recall and to file a complaint at ic3.gov [5].
What you’ll hear
“We have DMARC set up, so nobody can send email pretending to be us.”
That’s partly right. DMARC is worth having, and it does stop people from sending as your exact domain [1]. But the standard is clear that it doesn’t cover visually similar domains [1], and a lookalike isn’t your domain at all.
A related claim: “Buy every misspelling and you’re covered.” Registering a few obvious variants can help, but the list of possible near-copies is effectively endless. The fair version: DMARC and a few defensive domains help, and a phone call before paying does the rest.
What the numbers say
These counts come from complaints people chose to file with the FBI’s IC3, a US government agency. They cover businesses of all sizes and every form of business email compromise, including hacked real accounts, not only lookalike domains. We couldn’t find a reliable public figure for lookalike domains alone or for small businesses alone.
21,442 complaints and about $2.77 billion in reported losses from business email compromise in 2024 [4].
That’s roughly one in six dollars of the $16.6 billion in total losses reported to IC3 in 2024 [4].
$55.5 billion in exposed losses across 305,033 incidents worldwide from October 2013 through December 2023 [5].
What we’ve seen
We haven’t run into this yet.
Putting it together
You can’t stop someone from registering a domain that looks like yours. You can make sure a lookalike email never turns into a payment. Make the phone call to a known number a rule, add outside-sender warnings, and keep an eye on lookalikes so you can report them.
What good looks like
A written rule: any new or changed payment details get confirmed by phone, using a number already on file.
The same rule shared with key customers and vendors, so they call you too.
External sender labels or warnings turned on in Microsoft 365 or Google Workspace.
Staff who know to slow down when an email pushes for a fast payment.
A few obvious variants of your domain registered, if it makes sense for you.
Someone watching for new lookalikes and reporting them to the registrar.
Questions for your IT resource
Does a lookalike of our domain exist today, and does it have email set up?
Are external sender labels or warnings turned on for our email?
Should we register any variants of our domain?
Who would report a lookalike to the registrar, and how?
If someone here sent money to a fake account, who do we call first?
Related learning
What is DMARC?
DMARC is a DNS record that tells other mail servers what to do with email that claims to come from your domain but can’t prove it.
Does your business own its domain name?
Your domain name is the address behind your website and email, and it is registered, not bought outright. Keep it registered to the business, renewed well ahead of time and locked against transfers.
Forwarding rules and connected apps: who else can read your email
Mail rules and connected apps can quietly send copies of your email somewhere else or read it in the background. Reviewing them, and limiting who can create them, closes access that a password change alone won’t.
Sources
IETF, RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC), RFC Editor, May 2026. (checked 2026-10-08)
FBI, Business Email Compromise, updated April 2026. (checked 2026-10-08)
Federal Trade Commission, Cybersecurity for Small Business: Business Email Imposters, PDF, undated. (checked 2026-10-08)
FBI Internet Crime Complaint Center, 2024 IC3 Annual Report, covering 2024. (checked 2026-10-08)
FBI Internet Crime Complaint Center, Business Email Compromise: The $55 Billion Scam, September 11, 2024. (checked 2026-10-08)
Microsoft, Set-ExternalInOutlook, Microsoft Learn, updated February 2026. (checked 2026-10-08)
Microsoft, Anti-phishing policies in Microsoft 365, Microsoft Learn, updated August 2026. (checked 2026-10-08)
Google, Control Gmail external recipient warnings, Google Workspace Help, updated October 2026. (checked 2026-10-08)
ICANN, Submitting DNS Abuse Complaints to ICANN: A Step-by-Step Guide, PDF. (checked 2026-10-08)
ICANN, Registrar Abuse Reports. (checked 2026-10-08)
How we rate these. Our judgment from real setups, applied the same way on every page. Cost: $ = no new spend or under $25/month · $$ = a modest monthly tool or a short project · $$$ = new hardware, licensing, or a larger project. Effort: Light = one sitting · Moderate = setup plus follow-up over days or weeks · Heavy = planning, testing and staff changes. Outlined marks show how far it can go for some businesses. N/A = doesn’t apply to this topic. Time to fix: how long the first useful step takes, then how long until it’s fully done. Ratings are typical averages, not quotes. Time to fix: the filled dot is when the first useful step lands, the hollow dot is when it’s fully done. Who can do it: highlighted chips are who can reasonably handle it.