VirusTotal
13 / 92 engine detections
レポートを開く“Fxfunds”
The sent-report ledger records the first outgoing report at .
The recorded recipient is legal@gname.com.
The latest stored availability evidence still shows the domain reachable; 5 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.
フィッシング: web30.new — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 13/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 92 engine detections
レポートを開くScan report
レポートを開く3 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
web30.new is a domain on the PhishDestroy blocklist that presents itself under the name "Fxfunds". It has not been tied to a specific scheme yet. Its listing by MetaMask and SEAL, both focused on crypto threats, points to risk for wallet holders and anyone who handles digital assets. PhishDestroy first saw it on 2026-10-14, and the site was still online and serving content on 2026-10-19.
The name "Fxfunds" reads like a forex or fund-management brand. That kind of branding is commonly used to attract deposits with promises of trading returns. Nothing confirms that this site runs a fake trading platform or a wallet drainer. The main risks are sending funds to an operator you cannot verify and handing over personal or wallet access details to a site that crypto-security lists have already blocked.
On 2026-10-18, 13 of 92 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. Most engines stay silent on young sites, so a minority result like this still counts. Several unrelated vendors reached the same negative verdict on their own. MetaMask and SEAL list it alongside PhishDestroy, and three AlienVault OTX threat pulses reference it.
The domain was registered on 2026-07-31 through GNAME.COM PTE. LTD., about 75 days before PhishDestroy flagged it. That gap is long enough for an operator to build a site and start drawing in visitors before blocklists catch up. Traffic passes through Cloudflare's network, with the visible address in Canada. The Cloudflare proxy hides the server that actually hosts the content.
Do not deposit money or sign up with Fxfunds. If you already sent funds, keep your transaction records and do not pay any extra "fee" or "tax" to release a balance. If you connected a wallet, review and revoke its token approvals, and move assets to a fresh wallet if you shared a seed phrase. Change any password you reused on the site and turn on two-factor authentication. Defenders should block web30.new at DNS and proxy level and check logs for earlier visits.
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 の評判はこのドメインに起因しません。
igor.ns.cloudflare.commelissa.ns.cloudflare.comLocation describes the IP network.
749141628394c72b91f2de0e38ec002c2f2e4b4c25660363546a67170b3ed8dbSaved 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.web30.newDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of web30.new · checked Oct 14, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://web30.new/https://web30.new/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4a91a1a9b2ab2eb-YYZkeep-alivegziptext/htmlWed, 14 Oct 2026 19:48:30 GMTTue, 13 Oct 2026 17:44:06 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=dbfngT19hfk7p%2F9AQlRVZM1yDeE9kP%2BppViB%2FLkFu0MN7sZKfrhIAa0v%2F014mKpaqmBx9qCf5l%2B03Kvrb%2BQynLhiDBHVEg54eY9GVDkNlu4NPP7fpgCV0%2FL9uU8%3D"}]cloudflarecfCacheStatus;desc="DYNAMIC"max-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
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
No threat flag
View source13/92 engine detections
View source3 community references
View sourcePD-20261014-0239C1
Page captured
View sourceweb30.new
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
web30.new
PD-20261014-0239C1 Recipient: legal@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
web30.new)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.