Scammed on a Website? How to Build the Evidence Pack
A website scam leaves a specific kind of trail: a domain that was registered recently, a listing that promised something, a payment that went somewhere, and a conversation that stopped. Assembling those four things into one document is what turns a complaint into a case.
Prove the promise, not the disappointment. A reviewer needs to see what the site said it would do, and that it did not do it.
The Short Version
- Four pillars: the domain record, the payment record, the listing as it was, and the message thread.
- Capture the domain's registration date and hosting details — a site registered weeks ago is itself evidence.
- Keep the listing exactly as it appeared, with the URL and date visible.
- Build a dated timeline; it is the document every reviewer reads first.
- Package as one PDF with a contents page, and keep a copy for each body you report to.
What Actually Proves a Website Scam
There is a difference between knowing you were scammed and being able to show it. The gap is closed by four categories of evidence, each answering a different question.
| Pillar | Question it answers | What it looks like |
|---|---|---|
| The domain record | Was this a real business or a disposable site? | Registration date, registrar, hosting, and how long it has existed |
| The payment record | Did money actually move, and to whom? | Statement line, order confirmation, transaction reference |
| The listing as it was | What was promised? | Screenshot of the product page with URL and date visible |
| The message thread | What was said, and when did it stop? | Full conversation, uncropped, with timestamps |
Together these answer the three questions a reviewer asks: did the payment happen, was the customer deceived, and did the customer act promptly. Nothing else is required, and adding unrelated material slows the review.
The Domain Record
This is the pillar most victims overlook, and it is often the most persuasive. A legitimate retailer has a domain that has existed for years. A scam shop typically has one registered weeks or months before the campaign, often with privacy protection enabled and hosting on a shared provider.
What to capture:
- The exact domain, including any subdomain, as it appeared in the address bar.
- The registration date, from a public WHOIS lookup, with a screenshot of the result.
- The registrar and hosting provider, which are also the abuse contacts you will report to.
- The date you last saw the site live, and a screenshot of the error page if it has since gone down.
A domain registered three weeks before it took your payment is a fact a reviewer can weigh. It is not proof on its own, but it corroborates everything else in the file.
The Payment Record
Export this as a PDF from your bank or app rather than photographing a screen. It should show the date, the amount, the merchant name exactly as recorded, the reference number and the rail used.
If you paid through a payment app, export the app's own transaction detail as well. The bank statement may show only the app as the counterparty, which is not enough to identify the merchant.
If you paid in cryptocurrency, the transaction hash is the reference number, and the public ledger record is unusually strong evidence that a transfer occurred — though it does not identify the person behind the receiving address. You can read the public side of that record with the free wallet tracer, and the address itself can be included in a police report as set out in taking a wallet address to the police.
The Product Listing as It Was
Scam sites change or delete their pages once they have taken enough payments. The listing as it appeared at the time of purchase is therefore the single most perishable piece of evidence, and the one to capture first.
Capture the whole page, not just the price. The description, the delivery promise, the returns policy and the contact details are all part of what you were told. Include the URL bar and, where the page shows it, the date.
If you have already lost the page, check whether a web archive has a copy, and note the archive URL. An archived snapshot is weaker than your own capture but far better than nothing.
The Chat or Email Thread
Export or screenshot the full conversation, in order, with timestamps. Do not crop to the incriminating line; context is what makes a thread credible.
What matters most is the promise and the silence. The promise is the specific claim that induced the payment — the delivery date, the guarantee, the item described. The silence is the point at which the seller stopped responding, which is often the clearest evidence of intent.
If the conversation happened by phone, write down what was said and when, and label it clearly as your own recollection. Never present a reconstruction as a transcript; a single fabricated detail can discredit an otherwise strong file.
Building the Timeline
One page, one column of dates, plain language. This is the document that frames everything else.
Format:
[DATE] — Found the site via [source]. Listing advertised [item] at [price].
[DATE] — Placed order [NUMBER] and paid [AMOUNT] by [rail].
[DATE] — Expected delivery date passed with nothing received.
[DATE] — Emailed the seller at [address]; no reply.
[DATE] — Captured screenshots of the site and the listing.
[DATE] — Called [issuer/bank], spoke to [agent], case [NUMBER].
[DATE] — Reported the domain to [registrar/host] and filed [agency] report [NUMBER].
Keep it free of adjectives and free of speculation about who the operators are. Facts about your own actions and the site's behaviour are what a reviewer can use.
Packaging for the Card Issuer
The issuer wants the shortest path to a decision. Lead with the timeline, then the payment record, then the listing, then the thread.
- One PDF with a contents page and page numbers.
- State the reason code you are disputing under, and the case number.
- Keep it under about 20 MB so it passes attachment limits.
- Send through the secure channel and keep the submission confirmation.
Match the evidence to the category. A not-as-described claim needs the listing and photographs of what arrived; a services-not-rendered claim needs the payment record and your contact attempt. Sending everything for every category buries the document that decides the case.
Packaging for a Police Report
A police report is a different audience with a different purpose. The officer is recording an allegation, not adjudicating a dispute, so the file should be factual, dated and free of argument.
Bring: the timeline, the payment record, the domain details, the screenshots, and your own identification. State the loss amount plainly and give the domain and any account numbers you have.
Ask for the report number and a copy. That number is what you will quote to your bank, to the FTC and to any regulator, and it changes how a case is treated. For the wider set of reporting routes, see where to report a scam website.
Questions people ask
What evidence do I need to prove a website scam?
Four things: the domain record showing how new the site is, the payment record showing money moved, the listing as it appeared when you bought, and the full message thread. A dated timeline ties them together.
How do I prove a website is a scam?
Check the domain registration date, look for a physical address and a real returns policy, and compare the price against the market. A domain registered weeks ago, with no verifiable business details, is a strong indicator. Capture the evidence before the site disappears.
Are screenshots accepted as evidence of a scam?
Yes, if they show the URL, the date and the full context, and are unedited. Cropped or annotated images are frequently challenged. Save the original files rather than re-sharing them through messaging apps.
How do I package evidence for a card dispute?
One PDF with a contents page: timeline first, then the payment record, the listing screenshot and the message thread. State the reason code and case number, keep it under about 20 MB, and send it through the issuer's secure channel.
Should I include a police report in my evidence pack?
Yes, if you have one. A police reference is not required for most claims, but a case with one is treated differently from a case without, and it supports any later escalation to a regulator.
Check the address before you send anything
A free scan reads public chain data in your browser: balance, activity, counterparties and flags. No wallet connection, no seed phrase, no signup.
Primary sources and further reading
- Consumer Financial Protection Bureau — the US federal complaint route for card and payment disputes
- FBI Internet Crime Complaint Center — federal reporting portal for internet-enabled fraud
- USA.gov consumer complaints — directory of US consumer protection complaint routes
- FTC Consumer Sentinel Network — how consumer fraud reports are collected and shared
Related guides
Information only. We never promise recovery.