Domains
Typo and lookalike domain finder
Generate the lookalikes of your domain and see which are already registered or resolving.
Free, no accountLive check
Result
Fill in the form and press Find lookalike domains. The verdict and the detail appear here.
What this is
This typosquatting checker builds the names a person could plausibly type or misread instead of yours - a dropped letter, two letters swapped, a neighbouring key, a character that reads the same, your exact name under another ending - and then asks the network which of them are already resolving or registered.
A lookalike domain is only useful to someone else if a reader fails to notice it. That is why the ending swap and the character that reads the same sit at the top of the list here: acme.co and acrne.com contain nothing a glance at a URL bar would catch, while a neighbouring-key slip like axme.com is caught by anyone who reads what they typed.
Two states matter and they are not the same. A permutation answering with an A record has something served from it today. A permutation with a registration record and no A record is held by someone who has pointed it nowhere, which is a decision that can be reversed in minutes.
The open-source incumbents here are good and free. dnstwist generates far more permutation classes than this, including Unicode homoglyphs, and can hash each lookalike’s page and screenshot to score how closely it copies yours; CIRCL runs a public Typosquatting Finder with selectable algorithms. What neither does is register the names you decide to hold, which is the step this page is built to hand you.
How to read the result
The table is ordered closest first, and the "How it differs" column says which permutation class produced each name, so you can see at a glance whether the taken ones are the invisible kind or the kind a reader would catch.
Read "State" literally. "Answers with an address" means an A record came back, not that a copy of your site is there. "Registered, no address" means a registry holds a record and the name resolves to nothing. "No registration record" is the registry’s own 404 and is the one you can act on by registering the name yourself.
When more permutations are generated than a run checks, the whole list is offered as a file. That list is the thing to keep: re-running this in six months and comparing is how a newly registered lookalike gets noticed before it is pointed at anything.
This check belongs on the same schedule as the rest of a portfolio review; our guide Holding a domain portfolio: renewals, status codes and the names that attack yours covers where it fits alongside tracking your own renewals and reading EPP status codes.
Common mistakes
What goes wrong most often, and how to tell.
- Registering every permutationA four-letter name generates dozens of plausible misspellings and a longer one generates hundreds. Holding all of them costs a renewal every year for names nobody would ever type; holding the ending swaps and the homoglyphs costs very little and covers the permutations a reader cannot see.
- Ignoring a registered name because it resolves to nothingA name held with no A record is the quietest state a lookalike has, and the one that changes without any announcement. An MX record on it is enough to start collecting email meant for you, and no page needs to exist for that to work.
- Treating an A record as proof of phishingMost resolving lookalikes are parking pages a registrar put there by default. Deciding what a name is doing needs someone to look at it, and a dated record of what was served is also what a dispute would turn on.
- Checking once and calling it doneThis is a snapshot of one afternoon. Permutations are registered and dropped continuously, so the useful habit is a saved list and a repeat check, not a single clean result filed away as settled.
Questions
What people ask about this tool.
- The ones a reader would not notice: your exact name under a different ending, and the homoglyph permutations where one character has been replaced by something that reads identically. A neighbouring-key slip is caught by the person who made it, so it matters far less than a name that looks right.
- Comparing two sites means fetching both, normalising the HTML and hashing it, or rendering screenshots and comparing perceptual hashes. dnstwist does exactly that with ssdeep, tlsh and pHash, and it is the right tool for it; this page stops at which permutations exist and who holds them.
- No. Only ASCII substitutions such as rn for m or a zero for an o are generated here. A domain registered with a Cyrillic character in place of a Latin one is encoded as punycode and needs a curated Unicode confusable table to generate, which dnstwist maintains and this does not.
- Under paragraph 4(a) of the UDRP a complaint must establish three things together: the name is identical or confusingly similar to a mark you have rights in, the registrant has no rights or legitimate interests in it, and it was registered and is being used in bad faith. Evidence of what the name serves, with dates, is what the third point rests on.
- A run asks at most twenty lookups, the same ceiling the availability checker uses for names. A lookalike that answers with an address costs one lookup; one with no address costs two, a DNS query and then a registry query - so a run where most names are unregistered checks about half as many as one where they all resolve. A lookup is a question, not always a single request: a DNS question goes to a second public resolver if the first one does not answer, which is the one case a run sends more requests than it asked questions. The findings say how many of the generated names were checked, and the full list is offered as a file so the remainder can be checked in bulk or kept as a watch list.
Sources
Every fixed value here comes from the provider’s own documentation. These pages change, so each says the day it was last read.
- elceef (GitHub), “dnstwist: domain name permutation engine” read 13 October 2026
- CIRCL, “Typosquatting-finder” read 13 October 2026
- WIPO, “WIPO Guide to the Uniform Domain Name Dispute Resolution Policy (UDRP)” read 13 October 2026
Use it from the API
The same check, as one request.