VirusTotal
15 / 91 engine detections
レポートを開く“Velmora: Most Popular Online Crypto Casino Based on Blockchain”
暗号資産カジノ詐欺: velmora.casino — コンテンツが利用できません. 証拠の概要: VirusTotal 15/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, ESET); URLQuery 2 alerts…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 91 engine detections
レポートを開く2 threat-system alerts
レポートを開く1/12
1/100
1/100
レポートを開くDBL_PHISH
悪意あり
レポートを開くchecked — no match recorded
no community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of the domain velmora.casino indicates an active high-risk phishing campaign targeting users through a fraudulent online crypto casino platform. The domain was registered on April 13, 2026, via Global Domain Group LLC and currently resolves to the IP address 172.67.218.152, hosted behind Cloudflare infrastructure in Canada. The site presents itself as a blockchain-based crypto casino, as evidenced by its page title, 'Velmora: Most Popular Online Crypto Casino Based on Blockchain,' though the legitimacy of this claim remains unverified due to the absence of confirmed brand affiliation or licensing details. Infrastructure review reveals the use of Cloudflare nameservers (steven.ns.cloudflare.com and shubhi.ns.cloudflare.com) and a Let's Encrypt SSL certificate (serial E7), which are common among both legitimate and malicious sites. The domain is flagged by 17 of 94 security vendors on VirusTotal, and it appears on at least one security blocklist, with additional low trust scores (1/100) from Scamadviser and Gridinsoft. The scam type is classified as brand impersonation, though the specific brand being mimicked is not explicitly identified in available data. The Gambler Scam phishing kit is reportedly in use, suggesting a focus on financial fraud through deceptive gambling offers. Defenders should treat this domain as malicious based on its detection history, low trust scores, and active status. The use of Cloudflare does not inherently indicate legitimacy, as threat actors frequently leverage its services to obscure hosting details and evade takedowns. No legitimate business indicators, such as verifiable licensing or contact information, are present in the available intelligence. Network-level blocking of the IP 172.67.218.152 and domain-level filtering are recommended for organizations seeking to mitigate exposure to this campaign.
Last checked
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 の評判はこのドメインに起因しません。
shubhi.ns.cloudflare.comLocation describes the IP network.
26ecbc9a4243da9457b63844e9b738234f520bba47e1b47bb412d358259c13beSaved 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 velmora.casino · checked Jun 26, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='velmora.casino', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
velmora.casino
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
11→17
15/91 engine detections
View sourceNo threat flag
View source⚠️ ESCALATION #4 (515h active): Phishing - velmora[.]casino
⚠️ ESCALATION #3 (366h active): Phishing - velmora[.]casino
⚠️ ESCALATION #2 (164h active): Phishing - velmora[.]casino
velmora.casino
View sourceコミュニティの 1 人が報告・初回確認 2026年4月13日
PD-20260413-8C9B21 Recipient: abuse@identitydigital.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
velmora.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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.