Skip to security report
brawl.brwl.fun favicon
Domain security and threat intelligence

brawl.brwl.fun

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded brawl.brwl.fun on 2026-11-20. Stored VirusTotal result: 2/92 engines flagged. Malicious: 1. Suspicious: 1. Analysis time (as stored): 2026-11-20 09:40 UTC. Retrieved (as stored): 2026-11-20 09:59 UTC.

Page title: “Brawl Stars - 1000 гемов”

More about the sources
Recorded security signals

Stored VirusTotal result: 2/92 engines flagged. Malicious: 1. Suspicious: 1. Analysis time (as stored): 2026-11-20 09:40 UTC. Retrieved (as stored): 2026-11-20 09:59 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 2/92 Spamhaus DBL: spam domain
Registrar
GermanyPDR
Resolved IP
Russia81.19.135.219JSC TIMEWEB
Registered
2026-07-03
First seen by PhishDestroy
2026-11-20
Page captures
open gallery
Domain age
registered 2026-07-03 according to WHOIS · source data differ
Reports sent
view timeline
2026-11-20 1 Report Sent

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@publicdomainregistry.com. The latest stored availability evidence still shows the domain reachable; 2 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
2 days
Reports sent
1
Latest case ID
PD-F81FA57DD64ED60E4DA1
Current status
HTTP 301 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded brawl.brwl.fun on 2026-11-20. Stored VirusTotal result: 2/92 engines flagged. Malicious: 1. Suspicious: 1. Analysis time (as stored): 2026-11-20 09:40 UTC. Retrieved (as stored): 2026-11-20 09:59 UTC. Risk: high (evidence score 66/100). Registrar: PDR. Status: Last known active. Hosting: JSC TIMEWEB. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
Status
Last known active
VirusTotal
2 / 92
Hosting
Russia81.19.135.219JSC TIMEWEB
Registrar
GermanyPDR
Registered
2026-07-03
Page captures
4

Recorded source summary

brawl.brwl.fun is a subdomain of brwl.fun. PhishDestroy first observed the hostname on Nov 20, 2026. The captured page title is “Brawl Stars - 1000 гемов”. Current evidence score: 66/100 (high).

Positive findings are stored from 2 sources: VirusTotal and Spamhaus DBL. VirusTotal recorded 2 detections among 92 engines: Fortinet, SOCRadar on Nov 20, 2026 at 09:40 UTC. Spamhaus DBL: DBL_SPAM on Nov 20, 2026 at 11:30 UTC.

HTTP 301 was recorded on Nov 22, 2026 at 11:12 UTC. Latest classified outcome: redirect observed; cause http redirect on Nov 22, 2026 at 10:12 UTC. Registration records for the registrable domain brwl.fun list PDR Ltd. d/b/a PublicDomainRegistry.com as the registrar and Jul 3, 2026 as the creation date. At collection time, the hostname resolved to 81.19.135.219 on AS9123 (JSC TIMEWEB). The recorded endpoint location is Moscow, RU. The stored server header is nginx/1.24.0 (Ubuntu). The evidence archive retains 4 visual captures from PhishDestroy, URLScan, Cloudflare Radar, and URLQuery. TLS metadata lists Let's Encrypt / YE1 as the certificate issuer with validity through Jan 8, 2027.

The content indicators and 2 positive source findings support the current phishing classification.

Source evidenceVirusTotal 2 / 92 4 sources

VirusTotal

2 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
2
Denominator
92
Vendors
Fortinet, SOCRadar
Observed at
2026-11-20 09:40:13
Checked at
2026-11-20 10:59:18
Fetched at
2026-11-20 09:59:18

Spamhaus DBL

spam domain

URLScan

Page capture

SHA-256 27c19a13…a55d431

Open report
URLScanOriginal source recordObserved: 6 fields

Observed: · Retrieved:

Report ID

01a1f845-920f-745d-996b-786849a16856

Final URL

https://brawl.brwl.fun/brawlstars

Domain age, days

125

Registered domain age, days

649

Differs from the registration date in WHOIS (2026-07-03), which gives 139 days on the scan date 2026-11-20. The two sources disagree; both values are kept as recorded.

Page requests

1

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
28
Malicious
Yes
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
UUID
01a1f845-920f-745d-996b-786849a16856
Final URL
https://brawl.brwl.fun/brawlstars
Domain age days
125
Apex age days
649

Differs from the registration date in WHOIS (2026-07-03), which gives 139 days on the scan date 2026-11-20. The two sources disagree; both values are kept as recorded.

Requests
1
Provider verdicts
Engines: Tags: urlscan-ml, urlscan-ml-2aab354; Score: 28; Malicious: ✓; Overall: Score: 0; Malicious: ✗
Separate monitor record · 2026-11-21 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1f845-920f-745d-996b-786849a16856
Score
0
Malicious
✗
Result at
2026-11-21T04:30:19Z
Enriched at
2026-11-21T09:12:15Z
Source timestamps
Urlscan result at: 2026-11-21 05:30:19; Urlscan enriched at: 2026-11-21 10:12:15

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 15 fields

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443
  • 8888

DNS servers

Nameservers
  • IP address
    162.251.82.124
    Host
    fdomain.mars.orderbox-dns.com
  • IP address
    162.251.82.249
    Host
    fdomain.venus.orderbox-dns.com
  • IP address
    162.251.82.123
    Host
    fdomain.mercury.orderbox-dns.com
  • IP address
    162.251.82.118
    Host
    fdomain.earth.orderbox-dns.com
DNS zone
brwl.fun

Location

IP address
81.19.135.219
ASN
9123
Organization
JSC TIMEWEB
City
Moscow
Country
RU

TLS certificate

Subject alternative names
  • brawl.brwl.fun
  • roblox.brwl.fun
  • stats.brwl.fun
Key size, bits
256
Certificate chain
  • stats.brwl.fun
  • YE1
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE1
Serial
06AE035FFA00825A819396282EE22275F1F0
SHA-256
4c069bee08f24bfdd23b1da51f69510f38da49fba547e0f737a8e17a6aca856e
Subject
stats.brwl.fun
Valid until
Valid from

DNS records

A
  • 81.19.135.219

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
81.19.135.219
IP version
4

Subdomains

Count
4
Subdomains
  • brawl.brwl.fun
  • roblox.brwl.fun
  • standoff.brwl.fun
  • stats.brwl.fun

Technology stack

Technologies
  • Ubuntu
  • Nginx 1.24.0

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID
303
Registrar URL
https://publicdomainregistry.com/
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • fdomain.earth.orderbox-dns.com
  • fdomain.mars.orderbox-dns.com
  • fdomain.mercury.orderbox-dns.com
  • fdomain.venus.orderbox-dns.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
nginx/1.24.0 (Ubuntu)
Content-Type
application/json
Original source fields · JSON
Protective DNS results
Resolvers: 12; Blocked count: 0
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 22, 80, 443, 8888
DNS server
NS: (IP: 162.251.82.124; Host: fdomain.mars.orderbox-dns.com), (IP: 162.251.82.249; Host: fdomain.venus.orderbox-dns.com), (IP: 162.251.82.123; Host: fdomain.mercury.orderbox-dns.com), (IP: 162.251.82.118; Host: fdomain.earth.orderbox-dns.com); Zone: brwl.fun
Location
IP: 81.19.135.219; ASN: 9123; Org: JSC TIMEWEB; City: Moscow; Country: RU
SSL
San: brawl.brwl.fun, roblox.brwl.fun, stats.brwl.fun; Bits: 256; Chain: stats.brwl.fun, YE1, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE1; Serial: 06AE035FFA00825A819396282EE22275F1F0; SHA256: 4c069bee08f24bfdd23b1da51f69510f38da49fba547e0f737a8e17a6aca856e; Subject: stats.brwl.fun; Valid to: 2027-01-08T12:31:17Z; Valid from: 2026-10-10T12:31:18Z
DNS records
A: 81.19.135.219
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 81.19.135.219; Family: 4
Subdomains
Count: 4; Subdomains: brawl.brwl.fun, roblox.brwl.fun, standoff.brwl.fun, stats.brwl.fun
Tech stack
Technologies: Ubuntu, Nginx 1.24.0
Registration record
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com; Registrar iana ID: 303; Registrar URL: https://publicdomainregistry.com/; Created: 2026-07-03T14:38:53Z; Updated: 2026-07-08T14:39:28Z; Expires: 2027-07-03T14:38:53Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: fdomain.earth.orderbox-dns.com, fdomain.mars.orderbox-dns.com, fdomain.mercury.orderbox-dns.com, fdomain.venus.orderbox-dns.com; Dnssec: unsigned
HTTP headers
Headers: Server: nginx/1.24.0 (Ubuntu); Content type: application/json

Questions about brawl.brwl.fun

Is brawl.brwl.fun legit?

PhishDestroy rates brawl.brwl.fun as high risk (evidence score 66/100) from the recorded evidence; it was first recorded on 2026-11-20. Stored VirusTotal result: 2/92 engines flagged. Malicious: 1. Suspicious: 1. Analysis time (as stored): 2026-11-20 09:40 UTC. Retrieved (as stored): 2026-11-20 09:59 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is brawl.brwl.fun safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on brawl.brwl.fun. A confirmed blockchain transaction cannot be reversed.

What should I do if I used brawl.brwl.fun?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (4)

All capture links and hashes (4)
Observed page title
Brawl Stars - 1000 гемов
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 47 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 28 report ↗
IP Reputation Russia81.19.135.219 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 0 reports checked 2026-11-20 last reported · outside the counted period
Registrar (base domain) PDR DE(DE)
Hosting abuse contact abuse@timeweb.ru JSC TIMEWEB · AS9123
Registration (base domain)brwl.fun · Created 2026-07-03 (141d) — Expires 2027-07-03
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First Detected2026-11-20
Submitted URLhttps://brawl.brwl.fun/brawlstars
Case ID
ICANN OVERSIGHT Registration: brwl.fun

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

Registrable domain behind this subdomain: brwl.fun. For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Russia81.19.135.219
Network ASN
AS9123
Organization
JSC TIMEWEB
Observed location
RussiaMoscow, RU
Server header
nginx/1.24.0 (Ubuntu)

Nameservers 4

  • fdomain.earth.orderbox-dns.com
  • fdomain.mars.orderbox-dns.com
  • fdomain.mercury.orderbox-dns.com
  • fdomain.venus.orderbox-dns.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-10 12:31:18
Valid until
2027-01-08 12:31:17
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint4c069bee08f24bfdd23b1da51f69510f38da49fba547e0f737a8e17a6aca856e
Certificate names · 3 SANs
  • brawl.brwl.fun
  • roblox.brwl.fun
  • stats.brwl.fun

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-22 11:12 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-21 11:13 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:12 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
Open complete records

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
Fortinet
SOCRadar
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data102
Open complete records

Captured network requests

Network requests: 1 SHA-256 hashes: 0 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-20 09:29 UTC.

Open this scan on URLScan 01a1f845-920f-745d-996b-786849a16856 ↗

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

Our scanner could not complete this check.

Browser
Brawl Stars - 1000 гемов
Crawler
301 Moved Permanently
brawl.brwl.fun
Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Domain monitor · First collection record

    Reachable

All retained availability observations7
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    brawl.brwl.fun detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: PDR Ltd. d/b/a PublicDomainRegistry.com. Abuse contacts: 1.
    • abuse@publicdomainregistry.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+139 d 18 h
  3. First abuse report sent+1 min
  4. VirusTotal analysis with detections+13 min

Reported 139 d 18 h after registration

  1. VirusTotal

    2/92 engine detections

    +13 min
  2. Abuse report sent

    PD-F81FA57DD64ED60E4DA1 · Receipt 85408

    abuse@publicdomainregistry.com
    +1 min
  3. Added to PhishDestroy

    brawl.brwl.fun

    same minute
  4. URLScan

    Page captured

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-F81FA57DD64ED60E4DA1 Recipient: abuse@publicdomainregistry.com
Page title stored with report: Brawl Stars - 1000 гемов
PDF notice generated Notice text archived (395 characters)
Abuse notice text as sent to the provider
Registrar policy. Per PDR Ltd. d/b/a PublicDomainRegistry.com's published terms: “Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice”
Applicable law. Domestic legal framework (India): IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud).
Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including brawl.brwl.fun)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/brawl.brwl.fun"
  title="PhishDestroy threat report for brawl.brwl.fun"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>