VirusTotal
6 / 89 engine detections
PhishDestroy first recorded cs2.market on 2026-03-12. Stored VirusTotal result: 6/89 engines flagged.
Page title: “Buy and Sell Counter-Strike 2 (CS2) Skins - CS GO Market”
Stored VirusTotal result: 6/89 engines flagged. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
PhishDestroy analysis, earlier unreviewed version
This domain, cs2.market, is currently flagged as a high-risk generic phishing site. Created on March 12, 2026, the domain has been identified in various threat intelligence reports and is listed on at least one security blocklist. The page title 'Buy and Sell Counter-Strike 2 (CS2) Skins - CS GO Market' suggests that the site is attempting to impersonate a legitimate market for Counter-Strike 2 skins, a popular feature in the gaming community. Analysis indicates that the domain is still active and has been flagged by 10 out of 95 security vendors on VirusTotal, further corroborating its malicious nature. The domain is registered through GoDaddy.com, LLC and resolves to the IP address 195.85.59.45. Notably, the site employs several advanced technologies, including HSTS, Cloudflare Browser Insights, and HTTP/3, which may be used to enhance the credibility of the phishing site and evade detection. Additionally, the domain is blocked by PhishDestroy and has been mentioned in 23 threat intelligence pulses on AlienVault OTX, highlighting its significance in ongoing phishing campaigns. Defenders should immediately block access to this domain and monitor network traffic for any signs of users attempting to access it. Given the domain's high risk level and the specific targeting of gamers interested in CS2 skins, organizations should also educate their users about the dangers of phishing sites, especially those that mimic legitimate gaming platforms. Infrastructure analysis reveals the use of a Google Trust Services SSL certificate, which, while legitimate, does not guarantee the safety of the site and should not be used as a sole indicator of trustworthiness. Overall, the combination of the domain's creation date, security vendor flags, and technological features strongly suggests that cs2.market is a sophisticated phishing operation targeting gamers, and proactive measures are essential to mitigate potential risks.
6 / 89 engine detections
23 community references
Open reportScan report
Open report96/100
Trust score, lower = worse
Open reportPage capture
Open reportSeparate stored monitor snapshot; does not replace the primary report record or establish current availability.
100 / 100 · heuristic score · 0 brand references · 1 classification
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
PhishDestroy rates cs2.market as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-03-12. Stored VirusTotal result: 6/89 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on cs2.market. A confirmed blockchain transaction cannot be reversed.
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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/marketcsgoskinsStored page referenceIoC extraction recorded 2026-07-29 02:26 UTC
1522d89254f3df7179cdfd2fbe6ba049dc8054c8abab5bbcf57158772d482d9e · 370874 bytes 5bcd36348d982b20402360b9d94bfdb0267259a9913f46a0c3019b4280abd967 · 245579 bytes a4cb5fa96bc59efa56495d7ef4102eaabe3e53199ca2e79dcb24f0a1770180be · 15678 bytes 
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.
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.
Edge-IP reputation is not attributed to this domain.
coby.ns.cloudflare.comLocation describes the IP network.
99fb789afd77046a4f71fb01037ad96489b9e7431b4d89813bc36e2c6a13f7e4cs2.market*.cs2.marketSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was redirecting visitors elsewhere at the latest check.
Google PageSpeed Insights — mobile performance audit of cs2.market ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://cs2.market/https://cs2.market/en/Content-Type: text/htmlCache-Control: max-age=14400CF-Cache-Status: DYNAMICContent-Encoding: gzipServer: cloudflareh3=":443"; ma=86400max-age=14400DYNAMICa50e4013cca5ae87-GRUkeep-alivegzipscript-src 'self' 'wasm-unsafe-eval' 'strict-dynamic' 'nonce-43f24ea02bad505495afa786b8123376' *.yandex.ru *.facebook.net *.google-analytics.com *.google.com *.gstatic.com *.googletagmanager.com *.mail.ru dota2.net *.trustpilot.com; frame-ancestors 'self'; report-to csp-endpointdefault-src 'self'; script-src 'self' 'wasm-unsafe-eval' 'strict-dynamic' 'nonce-43f24ea02bad505495afa786b8123376' *.yandex.ru *.facebook.net *.google-analytics.com *.google.com *.gstatic.com *.googletagmanager.com *.mail.ru dota2.net *.trutext/htmlTue, 27 Oct 2026 02:25:28 GMTTue, 27 Oct 2026 06:25:28 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=abkmzh2hWBEBlDDB2enrCzuTAIRx2JdV%2FeUWopCN1aiEHSj07hbv4Ns72MT1IshCsT4jj9sK71WP4m4v5gD6GG4b77a81jePZWkdtrV7LnoIgZLQ%2FLJ5VehAwwQK"}]}csp-endpoint="https://mysentry.io/api/148/security/?sentry_key=a616d2c34afed96d13185a20f54a6732"cloudflarecfCacheStatus;desc="DYNAMIC"chunkedAccept-EncodingSAMEORIGINValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 266 SHA-256 hashes: 264 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-10-29 05:24 UTC.
Open this scan on URLScan 019ce288-a37e-739f-92ac-9f91c10f6dcf ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
content_divergence
cs2.market Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 1090 d 4 h after registration
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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| ID | Stored data |
|---|
Reported by 1 community member, first seen 2026-03-12
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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
cs2.market)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
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.