VirusTotal
4 / 91 engine detections
打开报告“Драгон Мани: играть в онлайн казино | Dragon Money”
赌博诈骗: drgn42.casino — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 4/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy score…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 91 engine detections
打开报告15/100
打开报告4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
drgn42.casino presents itself as Dragon Money (Драгон Мани), a Russian-language online casino, and invites visitors to sign up and play for real money. PhishDestroy classifies it as a fraudulent gambling site. We first detected it on 2026-08-21, one day after the domain was registered. On 2026-10-19 the site was still online and serving its casino content.
The page title, "Драгон Мани: играть в онлайн казино | Dragon Money", is aimed at players searching for the Dragon Money brand in Russian. Fraudulent casinos like this one usually let players deposit easily and may show early wins to build trust. When a player tries to withdraw, the payout gets stuck behind extra verification, sudden wagering requirements or fees. Victims can lose their deposits and any balance shown on screen. They also hand over identity documents and card details that can be misused later. The numbered name "drgn42" follows a pattern common in gambling schemes that keep switching domains to stay reachable after blocks.
VirusTotal shows 4 of 91 engines flagging the domain as of 2026-10-06: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That number is low, but four unrelated vendors reached the same verdict on their own. The domain also appears in 4 AlienVault OTX threat pulses, which means other researchers are tracking it too. Among the blocklists we checked, only PhishDestroy lists it, so many browsers and filters may still load it without warning.
The domain was registered on 2026-08-20 through Fewmoretaps OU (Trustname.com), and we picked it up the next day. A brand-new domain that goes live right away fits an operation built for quick replacement rather than a long-running business. The site is hosted on ALEXHOST SRL infrastructure in Moldova at 85.121.149.84. Its certificate comes from Let's Encrypt, so the padlock in the browser says nothing about whether the casino is legitimate.
Do not deposit on drgn42.casino, and do not pay any "withdrawal", "tax" or "verification" fee to unlock winnings, because these fees only add to the loss. If you paid by card, contact your bank about a chargeback and block the card. Change any password you reused on the site. If you uploaded passport or ID scans, treat them as exposed. Security teams should block the domain and the hosting IP, and watch for similar numbered Dragon Money domains appearing nearby.
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.
eugene.ns.cloudflare.comfaye.ns.cloudflare.comLocation describes the IP network.
38b466d4913cfed4dbe84223335a5a4f2647fd48e52a1723bcd0d950ccce1d38www.drgn42.casinoSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.drgn42.casinoDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of drgn42.casino · checked Aug 21, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
drgn42.casino
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
3→4
2→3
可访问
4/91 engine detections
View source4 community references
View sourceNo threat flag
View sourcedrgn42.casino
View sourcePage captured
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
Choose 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 ↗
drgn42.casino)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.