VirusTotal
11 / 89 engine detections
レポートを開く“SAXO”
フィッシング: saxo-jp.top — コンテンツが利用できません. 証拠の概要: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); URLQuery 2 alerts…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 89 engine detections
レポートを開く2 threat-system alerts
レポートを開くDBL_PHISH
6 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
saxo-jp.top was a phishing page built to pass as Saxo, the online investment and trading brand. Its page title read simply "SAXO", and the "-jp" in the domain points at a Japanese audience. PhishDestroy first flagged it on 2026-09-15. The site has been offline since 2026-09-17, and its DNS was still inactive at the last check on 2026-10-19.
Brokerage impersonation pages copy the look of a real trading platform so visitors believe they are logging into their own account. Victims typically hand over login credentials, one-time codes or identity details. In investment-themed variants, they are pushed to deposit funds into a fake account that shows invented profits, then asked for "fees" or "taxes" before any withdrawal. Either way, the loss is real: account access, personal data, or money sent to the operators that cannot be recovered through the fake platform.
Eleven of 89 VirusTotal engines flagged the domain by 2026-09-17, including Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a meaningful spread of independent vendors for a site that was live for only a few days. Spamhaus lists it in its DBL as a phishing domain. Beyond PhishDestroy, it appears on the MetaMask and SEAL blocklists, and six AlienVault OTX threat pulses reference it.
The domain was registered on 2026-09-04 through GLOBAL ASSET DOMAINS INC., just eleven days before PhishDestroy caught it. It went dark two days after that. This short lifespan is typical of throwaway phishing domains. The site sat behind Cloudflare, Inc. on an address geolocated to Canada, which masks the real origin server.
If you entered a Saxo username or password on this page, change it immediately through the official Saxo app or site. Reset or re-enroll two-factor authentication and check your account for unfamiliar logins or transfers. Contact Saxo support through channels you find yourself, never through links in messages. If you sent money or were asked to pay a fee to unlock a withdrawal, stop all payments, report the case to your bank and local police, and be wary of "recovery" services that approach you afterwards. Defenders should block saxo-jp.top and watch for look-alike Saxo domains on cheap TLDs such as .top.
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 の評判はこのドメインに起因しません。
amy.ns.cloudflare.comcleo.ns.cloudflare.comLocation describes the IP network.
24b9be9de60cf87be74f3787be3c2d3b04ab12f20ec7c47a6752730129694f0fSaved 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 saxo-jp.top · checked Sep 15, 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.
saxo-jp.top
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/89 engine detections
View sourceNo threat flag
View source6 community references
View sourcePD-20260915-07044A
Page captured
View sourcesaxo-jp.top
View sourcePD-20260915-07044A Recipient: complaint@gadomains.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 ↗
saxo-jp.top)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.