What Is Affix Squatting?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
Affix squatting attaches extra words to your exact brand name — a prefix or suffix, with or without a hyphen — so the domain reads as your brand's own login, support, shop or account page. TakedownCoop's generator builds affix candidates both ways, in both spellings: prefix and suffix, plain and hyphenated, then checks each one against DNS and Certificate Transparency.
What is affix squatting?
An affix squat keeps the brand intact and decorates it. Where typosquats rely on the visitor's error, affix squats rely on the visitor's trust in structure: a name that contains the whole brand plus a plausible service word looks like a department of the real business, not an imitation of it.
What is affix squatting?
An affix squat keeps the brand intact and decorates it. Where typosquats rely on the visitor's error, affix squats rely on the visitor's trust in structure: a name that contains the whole brand plus a plausible service word looks like a department of the real business, not an imitation of it.
The scan behind this page works in one pass over your whole street. It generates typosquat, homoglyph, affix and TLD-swap candidates from your domain, checks every one against real DNS resolution, searches Certificate Transparency logs for lookalike certificates, and tries a public, no-login check for fake profiles using your exact brand handle. For affix squatting, that means the first artefact you work from is evidence — what resolved, what holds a certificate, what could not be checked — rather than a screenshot someone sent you.
How the scan ranks and records it
Prioritisation is built into the result list. A hit that resolves and holds a certificate scores 90; resolving without a certificate, 80; registered but not resolving, 50 with a certificate and 40 without; a name seen only in Certificate Transparency logs scores 35, or 30 when it neither resolves nor is registered. You therefore deal with affix squatting in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.
The whole brand, plus one plausible word
Affix squats are the family customers defend least against, because nothing looks misspelled. The added word does the persuading: it tells a story about why this is a different address from the one the customer knows — a dedicated login, a regional shop, an accounts portal. The generator counters by construction, walking its affix list in four shapes per affix: prefix and suffix, each plain and hyphenated, all labelled 'affix-squat'.
For filings, affix squats have a useful property: the brand appears in full inside the infringing name, which makes trademark evidence straightforward to present. The packet's evidence block shows the genuine domain and the squatted one side by side, and the difference is purely the decoration. When an affix squat also carries a certificate and resolves — the 90 profile — the case writes itself.
A worked example, end to end
A fictional bank-alternative for freelancers, Northwall at northwall.io, finds login-northwall.com and northwall-support.com both registered the same week; the support variant resolves to a chat page asking customers to 'verify' wallet details, priority 90. The registrar packet for each name attaches the trademark record and the scan evidence, and the firm's real support page gains a banner pointing to its verified-genuine page — because the fake's whole trick was looking like a department, the genuine departments now carry a checkable door.
Turning evidence into a filing
A complaint says 'this is fake'; a packet proves it. The Pro packet generator turns a confirmed hit into a channel-correct evidence packet — one for the registrar, one for the host, and separate ones for Meta, Google Ads, marketplaces and app stores where they apply — each with a filing checklist written for that channel. The honesty rule is printed in every packet: TakedownCoop prepares the evidence and never claims to submit to a channel it cannot actually submit to. Filing stays with you or your agent, which is also why the evidence has to stand on its own.
- Scan so affix candidates are generated in all four shapes — prefix/suffix, plain/hyphenated
- File first on affix squats that resolve, especially service-word variants aimed at logins or support
- Screenshot any credential or payment request the page makes
- Direct customers to your verified-genuine page from your real service pages
- Watch the dormant affix variants under monitoring — they activate in waves
After you file: tracking the case
What happens next is tracked, not hoped for. Each target becomes a case — domain, fake store, social profile or scam ad — moving through evidence collected, packet built, submitted, provider response, resolved or reappeared. TakedownCoop distinguishes what you attest (that you submitted, that a provider replied) from what is verified by re-scan (that the item is actually gone), and it schedules a recheck seven days after a case is submitted so silence from a provider becomes a prompt, not a dead end.
Where efforts like this usually go wrong
A second failure is overreach — padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.
Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case — evidence, tickets, verified resolution and all — meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.
Keeping it from coming back
Closing the loop matters because clones come back under new names and new accounts. Re-appearance monitoring re-scans and regenerates packets; the verified-genuine page lets a cautious customer verify your real door before paying anyone; and the case timeline — every event, in order — exports as JSON or CSV when a processor, insurer or marketplace asks how you handled it. That is the co-op model applied to affix squatting: walk the street, knock with evidence, keep watch.
Frequently asked questions
How many affix variants does the scanner build?
Four per affix: the affix before and after the brand, each in plain and hyphenated spelling.
Why do affix squats fool people more than typos?
The brand name is spelled perfectly. The added service word explains the different address instead of raising suspicion.
Which affix variants are most dangerous?
The resolving ones impersonating a function — login, account, support, shop — because they ask for credentials, payments or personal data.
Does the full brand inside the name help my case?
Yes. The evidence block puts genuine and squatted names side by side; the only difference is the added decoration.
Keep exploring
TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms