Analysis of the domain blasar.casino, observed on July 24, 2026, indicates that it is being used for a crypto‑focused phishing campaign. The site resolves to the Cloudflare edge address 188.114.96.3, which is advertised as belonging to AS13335 Cloudflare, Inc. in the United States. No TLS certificate is presented, meaning the service is reachable only over plain HTTP. The page title returned from the host, "Blasar: Most Popular Online Crypto Casino Based on Blockchain," aligns with the documented scam type of a Crypto Scam and the identified phishing kit labeled as Gambler Scam. Infrastructure evidence shows the domain is registered through Cloudflare, Inc., and the authoritative nameservers are katelyn.ns.cloudflare.com and kayden.ns.cloudflare.com.
Reputation scoring is extremely low, with Gridinsoft assigning a trust score of 0 out of 100. VirusTotal analysis flags the domain on 15 of 95 scanning engines, reinforcing the malicious classification. The domain has been added to at least one public security blocklist and is actively blocked by the PhishDestroy feed, confirming that defensive communities have recognised it as hostile. Current operational status is offline, suggesting the operators have taken the site down, either voluntarily or due to takedown actions.
While the exact content of the site at the time of takedown is not available, the combination of the page title, scam type, and phishing kit strongly implies that the site was intended to lure cryptocurrency enthusiasts into submitting credentials or wallet information. Uncertainty remains around whether any victim data was exfiltrated before the takedown, as no forensic dump of the site’s pages has been published. Defenders should continue to block blasar.casino at network perimeters, add the domain to URL filtering and DNS sink‑hole lists, and monitor for any re‑registration attempts or similar domains using the same nameserver pattern.
DOM Analysisanalyzed 2026年4月23日score 78/1001 brand signal
Submitted URLhttps://blasar.casino/
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:12:25 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-15 22:40:49 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-15 22:40:49 UTC → 2026-09-30 16:14:55 UTC · 2,561.57hmidpoint estimate ≈ 2026-08-08 07:27:52 UTC · precision very low · basis bounded
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.
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='blasar.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
blasar.casino
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
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.
(US)
