# Fake event website report and follow-up log

Event: __________  Case owner: __________  Opened (date/time and timezone): __________
Official event URL: __________  Official ticket seller/URL: __________

## Verify and preserve
Suspected full URL (including path): __________
How it was discovered (message, ad, search, attendee report): __________
Observed claim, copied identity or checkout behavior: __________
Safe reviewer and review method: __________
Evidence folder (restricted): __________
- [ ] Dated screenshot with full URL and relevant content
- [ ] Original message/ad and redirect path if available
- [ ] Comparison with verified event and ticket URLs
- [ ] Personal information minimized before external reporting

## Protect attendees
Public notice owner and approved channel: __________
Official URL/support route stated: __________
Affected attendee support owner: __________
Payment or account exposure escalated to relevant provider/incident team: __________

## Provider reports
| Recipient and what it controls | Official abuse/report channel | Evidence sent | Case ID and time | Requested action | Response | Next follow-up owner/date |
|---|---|---|---|---|---|---|
| Hosting provider/platform | | | | | | |
| Domain registrar | | | | | | |
| Browser safety service | | | | | | |
| Ad/social/ticket platform | | | | | | |

## Outcome
Exact URL and redirects checked at: __________
State for each path (reported / warning / page removed / domain suspended): __________
Replacement domains or listings found: __________
Attendee notice updated at: __________
Closure decision and evidence: __________

A report is not a takedown guarantee. Do not enter credentials or payment details on the suspected site. Route legal claims and financial incidents to qualified local teams.