Skip to security report
Recorded security signals
Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-16 07:48 UTC. Retrieved (as stored): 2026-11-16 20:26 UTC. Use caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
case-battlee.com favicon

case-battlee.com

In short

PhishDestroy first recorded case-battlee.com on 2026-11-16. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-16 07:48 UTC. Retrieved (as stored): 2026-11-16 20:26 UTC.

Registrar
RussiaNiceNIC
Resolved IP
172.67.191.131
Registered
Nov 11, 2026
First observed
Nov 16, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 12/92 Young domain: 5 days old
VirusTotal
engine detections ·
URLQuery
detections
URLScan
engine verdict · score 96
Page captures
open gallery
Domain age
registered 2026-11-11 according to WHOIS
Reports sent
view timeline
Nov 16, 2026 1 Report Sent CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded case-battlee.com on 2026-11-16. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-16 07:48 UTC. Retrieved (as stored): 2026-11-16 20:26 UTC. Risk: critical (100/100). Registrar: NiceNIC. Status: Last known active. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
12 / 92
Hosting
172.67.191.131
Registrar
RussiaNiceNIC
Registered
Nov 11, 2026
Page captures
3

Recorded source summary

PhishDestroy first observed case-battlee.com on Nov 16, 2026. Current evidence score: 100/100 (critical).

Positive findings are stored from 2 sources: VirusTotal and URLQuery. VirusTotal recorded 12 detections among 92 engines: CRDF, ESET, G-Data, Lionic, Webroot, Emsisoft, Fortinet, Netcraft, Kaspersky, Seclookup, BitDefender, alphaMountain.ai on Nov 16, 2026 at 07:48 UTC. URLQuery recorded 4 detections; no observation timestamp was retained.

HTTP 200 was recorded on Nov 16, 2026 at 19:52 UTC. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Nov 11, 2026 as the creation date. Registration preceded first observation by 5 days. At collection time, the hostname resolved to 172.67.191.131. The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and URLQuery; the captures preserve the landing-page appearance. TLS metadata lists YE2 as the certificate issuer with validity through Feb 9, 2027.

The record contains 2 positive source findings supporting the current phishing classification.

Source evidenceVirusTotal 12 / 92 4 sources

VirusTotal

12 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 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
Numerator
11
Vendors
alphaMountain.ai, BitDefender, CRDF, Emsisoft, Fortinet, G-Data, Kaspersky, Lionic, Netcraft, Seclookup, Webroot

URLScan

Malicious · engine verdict · score 96

SHA-256 454d425f73d5c5e219cf630fd0e698bfd6ef3074acc48081c41fa3e32b442891

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record

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

UUID
01a1e5ea-4fd2-755a-b69d-44e87b5a287f

Google Safe Browsing

No threat flag

Open report

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: 22 fields

Mail configuration

Spf lookups: 0

Protective DNS results

Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1

Trackers

Requests: 74

Forms and mixed content

Third party scripts: 0

HTTP response

Up: ✓; Code: 200; Timings: DNS: 0; Wait: 266; Download: 54; Response ms: 377

TLS connection

Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓

Ports

Open: 80, 443, 8080

Carbon estimate

Bytes: 373911; Co2 grams: 0.0137; Cleaner than: 1

DNS server

NS: (IP: 162.159.44.78; Host: rodrigo.ns.cloudflare.com), (IP: 108.162.194.163; Host: indie.ns.cloudflare.com); Zone: case-battlee.com

Location

IP: 2606:4700:3033::6815:33e9; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US

SSL

Issuer: Let's Encrypt / YE2; Subject: case-battlee.com

DNS records

A: 172.67.191.131, 104.21.51.233; NS: indie.ns.cloudflare.com, rodrigo.ns.cloudflare.com; Soa: Nsname: indie.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419978599; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Txt: google-site-verification=M7-vHcvfQAdsFmz9ngey3dhDycAiA9WGOJPIJn5CWxk; Aaaa: 2606:4700:3033::6815:33e9, 2606:4700:3035::ac43:bf83

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: ✗

Web application firewall

Waf: Cloudflare; Has waf: ✓

Get IP

IP: 2606:4700:3033::6815:33e9; Family: 6

Redirects

Chain: https://case-battlee.com

Technology stack

Technologies: Svelte, Cloudflare, HTTP/3

Page links

External: https://case-battle.life/upgrade, https://case-battle.life/, https://case-battle.life/contract, https://case-battle.life/case/malgosha, https://case-battle.life/case/monsterhunterwilds, https://case-battle.life/, https://case-battle.life/giveaway, https://case-battle.life/tournament/131, https://m.sitehelp.me/telegram, https://www.youtube.com/c/CaseBattle, https://m.sitehelp.me/vkGroup, https://www.twitch.tv/casebattle_official, https://case-battle.life/case/ruby, https://case-battle.life/support, https://steamcommunity.com/openid/login, https://case-battle.life/auth, https://case-battle.life/users/76561199855131589, https://case-battle.life/users/76561198373965465, https://case-battle.life/users/76561199808130907, https://case-battle.life/users/76561199756382941, https://case-battle.life/users/76561198216692651, https://case-battle.life/users/76561197992578884, https://case-battle.life/users/76561198242978448, https://case-battle.life/users/76561199249743713, https://case-battle.life/users/76561198312982125; External count: 113; Internal count: 3

Registration record

Registrar: NICENIC INTERNATIONAL GROUP CO., LIMITED; Created: 2026-11-11T18:23:13Z; Updated: 2026-11-11T18:23:13Z; Expires: 2027-11-11T18:23:13Z; Status: clientDeleteProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp; Nameservers: indie.ns.cloudflare.com, rodrigo.ns.cloudflare.com

HTTP headers

Headers: Server: cloudflare; Content type: text/html
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Trackers
Requests: 74
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 266; Download: 54; Response ms: 377
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 373911; Co2 grams: 0.0137; Cleaner than: 1
DNS server
NS: (IP: 162.159.44.78; Host: rodrigo.ns.cloudflare.com), (IP: 108.162.194.163; Host: indie.ns.cloudflare.com); Zone: case-battlee.com
Location
IP: 2606:4700:3033::6815:33e9; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US
SSL
Issuer: Let's Encrypt / YE2; Subject: case-battlee.com
DNS records
A: 172.67.191.131, 104.21.51.233; NS: indie.ns.cloudflare.com, rodrigo.ns.cloudflare.com; Soa: Nsname: indie.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419978599; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Txt: google-site-verification=M7-vHcvfQAdsFmz9ngey3dhDycAiA9WGOJPIJn5CWxk; Aaaa: 2606:4700:3033::6815:33e9, 2606:4700:3035::ac43:bf83
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: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3033::6815:33e9; Family: 6
Redirects
Chain: https://case-battlee.com
Tech stack
Technologies: Svelte, Cloudflare, HTTP/3
Page links
External: https://case-battle.life/upgrade, https://case-battle.life/, https://case-battle.life/contract, https://case-battle.life/case/malgosha, https://case-battle.life/case/monsterhunterwilds, https://case-battle.life/, https://case-battle.life/giveaway, https://case-battle.life/tournament/131, https://m.sitehelp.me/telegram, https://www.youtube.com/c/CaseBattle, https://m.sitehelp.me/vkGroup, https://www.twitch.tv/casebattle_official, https://case-battle.life/case/ruby, https://case-battle.life/support, https://steamcommunity.com/openid/login, https://case-battle.life/auth, https://case-battle.life/users/76561199855131589, https://case-battle.life/users/76561198373965465, https://case-battle.life/users/76561199808130907, https://case-battle.life/users/76561199756382941, https://case-battle.life/users/76561198216692651, https://case-battle.life/users/76561197992578884, https://case-battle.life/users/76561198242978448, https://case-battle.life/users/76561199249743713, https://case-battle.life/users/76561198312982125; External count: 113; Internal count: 3
Registration record
Registrar: NICENIC INTERNATIONAL GROUP CO., LIMITED; Created: 2026-11-11T18:23:13Z; Updated: 2026-11-11T18:23:13Z; Expires: 2027-11-11T18:23:13Z; Status: clientDeleteProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp; Nameservers: indie.ns.cloudflare.com, rodrigo.ns.cloudflare.com
HTTP headers
Headers: Server: cloudflare; Content type: text/html
Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Questions about case-battlee.com

Is case-battlee.com legit?

PhishDestroy rates case-battlee.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-16. Stored VirusTotal result: 12/92 engines flagged. malicious: 11. suspicious: 1. Analysis time (as stored): 2026-11-16 07:48 UTC. Retrieved (as stored): 2026-11-16 20:26 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is case-battlee.com safe to connect a wallet?

This report does not record which wallet requests case-battlee.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used case-battlee.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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 · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 3 captures

All capture links and hashes (3)

Domain details

Domain
IP Context 172.67.191.131 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NiceNIC RU(RU) PhishDestroy Investigation
RegistrationCreated Nov 11, 2026 (5d · Brand New!) — Expires Nov 11, 2027
Registrant countrySerbia VirusTotal WHOIS
Registrant6eb609d996e182a6s@ VirusTotal WHOIS
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 16, 2026
Submitted URLhttps://case-battlee.com/
Case ID
TLS Certificate
Issued by YE2 · stored validity ends in 84 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.191.131
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • indie.ns.cloudflare.com
  • rodrigo.ns.cloudflare.com

SOA

  • nsname: indie.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2419978599
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

TLS certificate

Issuer
YE2
Valid from
2026-11-11 17:28:46
Valid until
2027-02-09 17:28:45
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint69406ecd338d3abc8485e6116d98c411816e9a2977c95adc1af844b454b92cbe
Certificate names · 2 SANs
  • *.case-battlee.com
  • case-battlee.com

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed
CRDF
ESET
G-Data
Lionic
Webroot
Emsisoft
Fortinet
Netcraft
Kaspersky
Seclookup
BitDefender
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://case-battlee.com/
CASE-BATTLE :: Официальный Сайт — CS2 Кейсы и Лучший Дроп из Них!
Response
HTTP 200
HTML body
365.5 KB
Compressed
49.3 KB
Links
3 internal · 147 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
Alt-Svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a5b90a9a9de13cb7-CDG
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Mon, 16 Nov 2026 19:53:22 GMT
Last-Modified
Wed, 11 Nov 2026 18:22:45 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=bG27iTHOQRapPbpIiGnIvyNQRPL0hbXsevgCoq0tnRlsTDDZW17CI3cP%2BzwhexinHzLty1weKld7f8zjbr3OV4ecgbxV3J0sAOHjGIc7aHomDBKBAMmr5i647G%2Bup8aklfBq"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Registration & observation details1

Availability observations

Last reachable observation

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

All stored data75
Open complete records

Captured network requests

Network requests: 224 SHA-256 hashes: 218 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-16 19:53 UTC.

Open this scan on URLScan 01a1e5ea-4fd2-755a-b69d-44e87b5a287f ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. Current state backfill
    Observation source
    Current state backfill
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    stale
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-16 20:52:57.000000
    Evidence SHA-256
    7a16011d11a78ea7836716cb791f561f9c988319174d558d558124b9e1c04c2d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-16 20:52:57
  2. Http observation
    Observation source
    Http observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-16 20:52:57.000000
    Evidence SHA-256
    7a16011d11a78ea7836716cb791f561f9c988319174d558d558124b9e1c04c2d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-16 20:52:57

Threat Response Pipeline

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

Recorded events: 9. 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: 1 of 1
  • Threat Ingested
    case-battlee.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Registrar Context: NiceNIC · Forensic Evidence Collected Recorded: 6 of 6
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: NICENIC INTERNATIONAL GROUP CO., LIMITED. Abuse contacts: 1.
    • abuse@nicenic.net
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Wayback Machine

    Page archived

    View source
  2. Abuse report sent

    PD-1DBFF316A8E506A6FA69 · Receipt 85090

    abuse@nicenic.net
  3. Added to PhishDestroy

    case-battlee.com

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    12/92 engine detections

    View source
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

Check for cloaking

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

case-battlee.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1DBFF316A8E506A6FA69 Recipient: abuse@nicenic.net
Page title stored with report: CASE-BATTLE :: Официальный Сайт — CS2 Кейсы и Лучший Дроп из Них!
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Official reporting routes

More official reporting routes
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.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
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

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 case-battlee.com)
  • 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/case-battlee.com"
  title="PhishDestroy threat report for case-battlee.com"
  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>