VirusTotal
11 / 92 engine detections
レポートを開く“Xpay”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 10 days 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.
フィッシング: xpay-app.cc — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 11/92 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 92 engine detections
レポートを開くSuspicious
レポートを開くScan report
レポートを開く2 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
xpay-app.cc is on the PhishDestroy blocklist. It presents itself simply as "Xpay", a payment-style name that gives visitors no clear company or product behind it. PhishDestroy first saw the domain on 2026-10-09. As of 2026-10-19 the site was still online and serving content.
PhishDestroy has not yet assigned this domain a specific scheme. What it has instead is a listing on MetaMask's and SEAL's crypto-focused blocklists, which points to risk for people who connect a wallet or move funds through the site. Sites with a generic payment brand and this kind of listing typically ask visitors to link a wallet, sign a request, or deposit crypto into an "app" balance. Any signature, approval or transfer made on such a page can be irreversible.
VirusTotal showed 11 of 92 engines flagging the domain on 2026-10-13. The vendors that flagged it include alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky and LevelBlue, a spread of independent vendors rather than a single outlier. Beyond PhishDestroy, MetaMask and the SEAL security alliance both list the domain, and it appears in 2 AlienVault OTX threat pulses.
The domain was registered through Dynadot Inc on 2026-09-15, just 24 days before PhishDestroy picked it up, which fits the short lifecycle of throwaway crypto domains. It sits behind Cloudflare, Inc., which hides the real origin server, and the network is geolocated to Canada. The Google Trust Services certificate only means the connection is encrypted; the padlock says nothing about whether the site is legitimate.
Do not connect a wallet, sign messages or send funds to xpay-app.cc. If you already connected a wallet, review its token approvals with a revocation tool, cancel any you don't recognize, and move remaining assets to a fresh wallet if you signed anything you didn't fully understand. If you entered a seed phrase, treat that wallet as compromised and empty it immediately. If you deposited funds, do not pay any extra "fee" to unlock a withdrawal. Defenders should block the domain at DNS and proxy level and watch for lookalike "xpay" registrations.
Last checked
Edge-IP の評判はこのドメインに起因しません。
amy.ns.cloudflare.comcleo.ns.cloudflare.comLocation describes the IP network.
2bf06bd3cd184e1a0f0861cb355fb38bd90874757c56e7d1ab90403faeb1a889Saved 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 xpay-app.cc · checked Oct 9, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
No threat flag
View source11/92 engine detections
View sourcePD-20261009-BB0EEE
Page captured
View source2 community references
View sourcexpay-app.cc
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
xpay-app.cc
PD-20261009-BB0EEE Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
xpay-app.cc)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.