VirusTotal
6 / 89
“CSFAIL — Top CS2 site for high-risk games and big wins”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 2 months 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.
On 2026-10-01, an HTTP request to 2cs.fail returned status 301, a redirect response recorded in the HTTP check. The domain 2cs.fail also appears in the PhishDestroy internal listing, and its registration date is recorded as 2023-07-04.
The HTTP check on 2026-10-01 recorded status 301 for 2cs.fail. VirusTotal, checked on 2026-09-21, reported 6 detections across 89 scanners. OTX, checked on 2026-08-21, recorded 4 pulses. The domain was first observed on 2026-08-10, the same date as the PageSpeed check, which returned a performance score of 52. The SSL scan on 2026-08-10 identified Google Trust Services / WE1 as the issuer, and the registrar is NameCheap, Inc. The IP address 45.199.188.12 is recorded in TW with organization Cloud Innovation Ltd.
The named source observations describe separate measurements taken on different dates, so they should be compared as distinct records rather than combined into a single verdict. The HTTP status, VirusTotal detections, OTX pulses, and PageSpeed score each reflect only what their respective checks recorded at the time. The chronology shows the first observation and SSL scan on 2026-08-10, followed by OTX on 2026-08-21, VirusTotal on 2026-09-21, and the HTTP check on 2026-10-01.
Preserve the PhishDestroy internal listing record for 2cs.fail alongside the HTTP check that recorded status 301. Compare the VirusTotal and OTX records for 2cs.fail in separate reviews, since each source reports its own metric. Retain the PageSpeed and SSL scan records for 2cs.fail to document what those checks observed. Use the recorded HTTP response as a dated observation rather than a statement about current availability.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://12cs.fail/; server=cloudflare
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.
bayan.ns.cloudflare.comnia.ns.cloudflare.comLocation describes the IP network.
6c5a87166924340200299f94339092dd122dd8529885106bf2aec9820cbc36cdSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of 2cs.fail · checked Aug 10, 2026
45.199.188.12. 14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
PD-20260810-45CEBC Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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