VirusTotal
17 / 91 engine detections
レポートを開く“xulvertik.digital”
フィッシング: xulvertik.digital — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 17/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); CF Radar…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 91 engine detections
レポートを開く悪意あり
レポートを開く3 community references
レポートを開く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
xulvertik.digital is an impersonation phishing page that copies a legitimate service to win visitors' trust and harvest their access. PhishDestroy first flagged it on 2026-09-20. As of 2026-10-19 the site was still online and serving its phishing content, so anyone sent there today can still be caught.
The browser tab shows only the bare domain, xulvertik.digital, with no brand name. Impersonation pages like this copy the look and wording of a service the victim already uses, then ask the victim to sign in, verify an account or connect a wallet. Whatever is typed in goes straight to the operators. That can include passwords, one-time codes or a recovery phrase, and with them the operators can take over accounts or empty funds.
On 2026-10-01, 17 of 91 VirusTotal engines rated the domain malicious. That is a clear signal from a wide mix of vendors, including alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker and Fortinet. The domain also appears in three AlienVault OTX threat pulses, so other researchers have tracked it independently. It sits on the PhishDestroy blocklist.
The domain was registered through Spaceship, Inc. on 2026-05-31, about 112 days before PhishDestroy detected it. That gap suggests it was set up ahead of time and kept in reserve rather than used right away. It is hosted at 185.62.57.28 on the Snel.com B.V. network in the Netherlands. Its free ZeroSSL certificate gives the padlock icon, which only means the connection is encrypted and says nothing about whether the site can be trusted.
If you entered a password on this site, change it now on the real service and on any other account that shares it, then turn on app-based two-factor authentication. Sign out of all active sessions and check for unfamiliar logins, changed recovery emails or new forwarding rules. If you typed in a wallet recovery phrase, treat that wallet as compromised and move any remaining funds to a newly created wallet immediately. Security teams should block the domain and its IP at the DNS and proxy level and search logs for past visits.
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 の評判はこのドメインに起因しません。
elisabeth.ns.cloudflare.comLocation describes the IP network.
2dd5cb3c9e33514d92499632aa5bf4fb3fb2571d44b2ec325bac36ed5f8fc9bfSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
alive_content: raw=ok; http=200; via=https_proxy
xulvertik.digital
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
17→Observation retained
No threat flag
View source17/91 engine detections
View source3 community references
View sourcexulvertik.digital
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 ↗
xulvertik.digital)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.