Customers are confusing a lookalike website with your store
Build the attribution record before you report anything. List the domains and channels your business actually controls, capture the lookalike's exact URLs with observation dates, and keep customer reports of confusion in minimal, non-sensitive form. ICANN explains that registrars maintain abuse contacts and investigation procedures, so identify the lookalike's registrar and use its published channel with your evidence attached. Do not assert fraud, trademark rights or removal as established facts; a report triggers review, not a guaranteed outcome, and legal characterizations belong with counsel.
For: An authorized staff member of a research-only merchant responding to reports that a separate website is presenting the business's identity as its own.
The record starts at home. Write the authoritative list of domains, storefronts and support channels your business controls, with the internal evidence for each. This is the baseline that lets you say, precisely, that a given address is not yours, and it stops the team from hedging later when a customer or platform asks which site is real.
Include the less obvious surfaces: retired domains that still redirect, regional variants, and the email addresses your receipts and support messages genuinely come from. A lookalike often sits one character away from one of these, and the exact spelling on both sides is what the record must preserve.
Capture the lookalike precisely and safely
Observe the other site the way a cautious visitor would. Record its exact URLs, the date and time you viewed them, and which of your identity elements appear there: your business name, logo, product photographs, or copied page copy. Keep screenshots or saved pages in your evidence store with their dates, because the site can change or vanish after a report.
Do not investigate by transacting. Enter no credentials, no card numbers and no personal details on the lookalike, and place no orders to see what happens. Observation of the public pages is enough for an attribution record; anything beyond it creates risk for you and contaminates the evidence.
Record customer confusion without collecting extra data
Customer reports are often what reveals a lookalike, and they are evidence, but they should be minimized. For each report, note the date, what the customer believed they were using, what happened, and the address they visited if they can supply it. Do not ask customers to forward full card numbers, passwords or complete account records, and do not copy such details into the record if they arrive uninvited.
Keep belief and fact separate in the write-up. A customer who paid the wrong site establishes that confusion occurred, not what the other site's operator intended. That distinction matters because the next steps depend on it: the registrar's abuse team reviews what is documented, and counsel evaluates claims the record alone cannot make.
Route the report through the right channel
Identify who provides the lookalike's infrastructure from public records: the registrar for the domain and, where relevant, the hosting provider or platform. ICANN explains that registrars operating under the applicable agreements maintain abuse reporting contacts and investigation procedures, so the registrar's published abuse channel is a legitimate route with your dated evidence attached. Where the site is hosted on a platform, that platform's own impersonation or abuse process applies as well.
Write the report as a factual dossier: your controlled domains, the lookalike's URLs and observation dates, the copied elements, and the customer-confusion reports in summary form. State what you are asking the provider to review. Do not declare the site fraudulent or infringing in the report; those are conclusions the recipient, or a court, reaches. A report creates a review, not a right to removal, and providers act under their own rules and timelines.
Decide the unresolved questions with the right owners
Three decisions usually remain after reporting, and they have different owners. Legal characterizations, such as trademark infringement or fraud, go to qualified counsel with the evidence store. The decision to publish a clarification on your own site, naming the domains you operate so customers can check, belongs to the business owner and should use verified facts only. Follow-up on the abuse report stays with the assigned staff member, recorded by date and response.
If the confusion is reaching your payment provider or appearing in disputes, that provider conversation is its own track with its own evidence. A scoped Prism website-review consultation can help you organize how your genuine storefront identifies the business; confirm scope, responsibilities, fees and terms before work, and understand that no consultation removes a third party's page or guarantees an abuse team's decision.
Impersonation attribution record
Complete one record per lookalike site, adding entries per observed URL and per customer report in your internal store. The record supports a factual report; it does not establish wrongdoing, trademark rights or removal.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Impersonation attribution record. The last column is for temporary notes.
Attribution item
What the evidence must establish
Your record
Domains you control
What the evidence must establishThe authoritative internal list of domains, storefronts and support channels your business operates, with evidence references.
Lookalike URL and date
What the evidence must establishExact addresses observed and when, captured without entering credentials or payment data on the other site.
Identity elements copied
What the evidence must establishYour business name, logo, product images or page copy appearing on the other site, with dated captures.
Customer confusion report
What the evidence must establishA minimal record of what the customer believed and did, excluding card data, passwords and full account details.
Registrar or host identified
What the evidence must establishThe provider responsible for the lookalike's domain or hosting, identified from public records.
Abuse report reference
What the evidence must establishThe channel used, submission date and any case number from the registrar or platform.
Claims reserved for counsel
What the evidence must establishAny fraud, trademark or legal assertion flagged for qualified review rather than stated as established fact.
Follow-up and buyer notice
What the evidence must establishStatus checks on the report and any factual clarification published on your own site about the domains you operate.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
This record supports a report; it does not establish fraud, trademark infringement or a right to removal, and abuse teams act under their own rules.
Legal characterizations of the lookalike belong to qualified counsel, and no report guarantees takedown or a timeline.
Do not enter credentials, card data or test orders on the lookalike site, and keep customer details in the record to the minimum needed.
ICANN: Registrar abuse reports — checked 2026-10-01. Registrars under the applicable agreements maintain abuse reporting contacts and investigation procedures; a report does not prove wrongdoing, establish trademark rights or guarantee removal.