Which Lookalike Domains Should You Register Defensively?
Published 2026-11-14 · Reviewed 2026-11-14 · 6 min read · By the Ingenious AI team
Is someone impersonating your domain right now?
Run the free DomainGuard scan: lookalike registrations, MX-armed variants, certificate-transparency and CAA checks for your domain, in one report.
Run my free DomainGuard scanThe short answer
Register defensively the variants a customer would plausibly trust or mistype: your brand's common typos and transpositions on your main TLD, your exact name on the other major extensions, your name plus login, secure, and support, and the homoglyph single-swaps you can reasonably hold. You cannot own the whole variant space — nobody can — so buy from the top of a risk-ranked list, redirect everything to your real site, protect the portfolio with registrar lock and auto-renewal, and let monitoring watch the long tail you chose not to buy.
Build the risk-ranked list first
Start from your full permutation picture, not from guesses. Generate the families — typos, omissions, transpositions, combosquats, homoglyphs, TLD variants — and mark which are already registered by others, which are available, and which of the registered ones are armed. The available list, ranked, is your shopping list. Ranking follows the customer's likely behaviour: names one keystroke from yours on the same extension first, because mistyped traffic is guaranteed every single day at any scale.
Next come trust names: your exact brand on .co, .net, .io and any extension your industry treats as normal, then the combos that describe a destination — login, account, secure, support. Homoglyphs rank by simplicity: single-character swaps in scripts your customers' devices render natively. At the bottom sit the exotic combinations you will monitor instead of buying. The list is finite and, for most brands, the top tier costs less per year than a single team lunch — the barrier is almost never price, it is that nobody wrote the list down.
What to do with domains you buy
Redirect every defensive domain to the corresponding real page — typos to your homepage, login combos to your real login — over HTTPS with a proper certificate. A defensive domain that resolves nowhere wastes half its value: the mistyped customer should land in your shop, not on a browser error that sends them searching again (possibly into an ad for the next-best impostor). A domain that redirects also proves use, which strengthens your position in any later dispute about that name family.
Manage the portfolio as one asset: same registrar where possible, registrar lock on, auto-renewal on, renewal payment method monitored, and WHOIS contact details pointing at a role mailbox that survives staff changes. More defensive portfolios are lost to a lapsed credit card and an expired name than to any attacker action — and an expired defensive domain is the cruellest outcome in this field, because the name returns to the market with your own traffic patterns as its selling point.
The expiry trap and registrar hygiene
Treat every domain you own — main brand included — as perishable inventory with an owner. Keep a register: name, registrar, renewal date, cost, purpose. Audit it twice a year, including the test of actually logging into each registrar account; portfolios scattered across forgotten accounts at forgotten registrars are how companies discover, during an incident, that the person who can renew their .co left in 2023.
Enable every protection the registrar offers the portfolio: transfer lock permanently, registry lock on the crown-jewel names, two-factor authentication on the accounts, and change alerts routed to that same durable role mailbox. Your defensive strategy is only as strong as the account security holding it — an attacker who cannot register your typos can still try to steal the ones you own, and registrar-account compromise is a documented route to exactly that.
Where buying stops and monitoring starts
The variant space grows combinatorially — double typos, two-word combos, every TLD on earth — and at some point each additional name defends against a customer error so unlikely that monitoring covers the risk better. That point arrives sooner for invented brand names and later for short, common-word brands whose typo neighbourhood is dense. Let data place the line: in your monitoring, the registered-by-others set shows you which neighbourhoods attackers actually prospect; buy the available names adjacent to their activity, not the abstractly possible ones.
Revisit the line when your brand changes shape: new product names, new markets and languages (which bring new homoglyph and transliteration neighbourhoods), acquisitions whose names join your estate, and any attention spike that raises your name's value to strangers. DomainGuard's reports refresh the registered-versus-available picture continuously, so the defensive list stays a living queue — buy the new top tier each season, and let the tail stay watched rather than owned.
The honest accounting
Defensive registration is insurance with an unusually legible premium: the annual portfolio cost, printed on one invoice, against incident costs that arrive uninvited and unitemised — takedown hours, chargebacks, support burden, the UDRP filing for a name you could have owned for twelve dollars. Our ecommerce and agency guides both land on the same arithmetic from different directions: the top tier of variants costs less than any single incident they prevent.
Just do not let the portfolio become the strategy. Owning fifty variants while sitting at DMARC p=none and checking lookalikes quarterly is buying locks for the windows while the door stands open. Sequence it the way this guide series does: authenticate your mail, monitor continuously, rehearse the takedown — and register defensively as the layer that quietly removes the attacker's best options before the other layers are ever tested.
Five actions to take today
- Generate the full variant list and rank available names: typos on your main TLD, exact name on major TLDs, trust-word combos, simple homoglyphs.
- Buy from the top of the ranked list and redirect every defensive name over HTTPS to the matching real page.
- Consolidate at one registrar with transfer lock, auto-renewal, 2FA, and a role mailbox for all contacts.
- Keep a register of every owned domain — purpose, registrar, renewal date — and audit account access twice a year.
- Let monitoring watch the unpurchased tail, and refresh the buy list when your brand, products, or markets change.
Worked example: Studio Meridian builds a 41-domain shield
Studio Meridian, a fictional agency monitoring 15 domains, applied this ranking to its own brand first. Of 1,900 generated variants, 23 were registered by others and 61 were worth buying: the portfolio cost came to $612 a year, all redirecting to the agency's real site. Two renewals in the first year were caught by the register audit after a card change — names that would otherwise have lapsed unnoticed. Client rollouts copied the template, averaging 38 defensive names per brand, and quarterly reviews since have added a median of 3 names per brand per year as new product names appear.
FAQ
How many defensive domains does a small brand need?
Typically 20 to 60 for the high-risk tier, costing a few hundred dollars a year. The ranked list decides; invented names need fewer, short common-word brands need more.
Should defensive domains have their own websites?
No. A redirect to the real site is better: it captures the traffic, proves use, and costs nothing to maintain. Parked defensive domains with registrar ads can even confuse customers.
What happens if a defensive domain expires?
It returns to the open market, where drop-catchers monitor valuable expiries — your name can be re-registered within minutes and used against the traffic patterns it already has. Auto-renewal and register audits exist to prevent exactly this.
Is it worth buying variants on obscure TLDs?
Rarely at the top of the list. Customers plausibly trust a handful of extensions; the rest is monitoring territory. Exceptions exist for industries where a niche TLD is normal, like .io for developer tools.
Can defensive registration stop phishing by itself?
No. It removes the best names from the attacker's market, but the variant space is larger than any portfolio. It works as one layer alongside email authentication, monitoring, and takedown readiness.