セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
resourcefixweb.com favicon

resourcefixweb.com

“Resource Dex”

レジストラ
NameCheap
Resolved IP
216.24.57.1
Registered
2026年8月26日
PhishDestroy assessment クリティカル
First observed Sep 16, 2026 04:40 UTC · PhishDestroy
VirusTotal 検出数: 4/91 自動ブランドラベル:Google
OTX: 3 refs 2026年9月16日 CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 4。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Domain age
レポート概要

Googleなりすまし: resourcefixweb.com — 未検証. 証拠の概要: VirusTotal 4/91 (CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy score 81/100. レジストラ…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 4 / 91 · OTX 3 references 4 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

クリティカル
VirusTotal
4 / 91
OTX
3 community refs

PhishDestroy threat report

Overview

resourcefixweb.com is an impersonation phishing page that presents itself as "Resource Dex," a decentralized exchange front end. It targets crypto users looking to trade or swap tokens who may reach it through ads, social media posts or direct messages. PhishDestroy first flagged it on 2026-09-16. On 2026-10-19 the hosting endpoint still responded, but the domain's DNS was inactive and no phishing content was being served.

How the scam works

Fake DEX pages copy the look of a real trading interface and ask the visitor to connect a wallet before swapping. The trap is in what follows. The site requests a token approval, a permit signature or a transaction that hands spending rights to an address the operators control, and they can then move the victim's tokens out. Some variants also ask for a seed phrase under the pretext of "syncing" or "fixing" a wallet, which gives up the entire wallet. The "fix" wording in the domain name fits that second pattern.

Evidence

On 2026-09-29, 4 of 91 VirusTotal engines flagged the domain: CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a low count, so most security tools would have let a visitor through. The domain also appears in 3 AlienVault OTX threat pulses, which means other researchers have tied it to malicious activity. Among blocklists, PhishDestroy currently lists it.

Infrastructure

The domain was registered through NameCheap, Inc. on 2026-08-26, three weeks before PhishDestroy detected it. That short gap between registration and use is typical of throwaway phishing domains. The site was hosted on Render, a US cloud application platform, at 216.24.57.1. Platforms like this let operators deploy a cloned front end in minutes and replace it just as quickly.

What to do

If you connected a wallet to this site, check its token approvals with a reputable approval checker and revoke any you do not recognize. Move remaining assets to a fresh wallet if you signed anything you did not understand. If you typed in a seed phrase, treat that wallet as compromised and transfer funds to a new wallet with a new phrase right away. Security teams should block the domain at DNS and proxy level and watch for lookalike "Resource Dex" domains on the same hosting pattern.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

ドメイン
IP Context Cloudflare shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
OTX tags 2026-09activeall-domainsblocklistcontentcryptoドメインdrainerfraudmonthlyphishdestroyphishingscam
レジストラ NameCheap US(US)
不正利用連絡先["abuse@namecheap.com"]
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年8月26日 (54d · New) — Expires 2027年8月26日
技術詳細Provenance & timestamps
初確認2026年9月16日
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.24.57.1
Network ASN
AS397273
Organization
Render
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP の評判はこのドメインに起因しません。

ネームサーバー 1

  • dns2.registrar-servers.com

Mail routing 5 MX records

  • eforward2.registrar-servers.compriority 10
  • eforward1.registrar-servers.compriority 10
  • eforward3.registrar-servers.compriority 10
  • eforward4.registrar-servers.compriority 15
  • eforward5.registrar-servers.compriority 20

Location describes the IP network.

TLS証明書

Issuer
Google Trust Services / WE1
Valid from
2026-08-26 21:08:00
Valid until
2026-11-24 22:07:55
Validity
Within stored validity dates
Collection time
2026-10-11 04:02:56 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2773f0658fdb516e6631c82c7888dcd8d6fd71e353bfbc67e0fde405a722e968

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS 非アクティブ reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 不明 Probe Inconclusive 20% 2026-10-20 10:07:19 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-13 01:46:23 UTC last content: 2026-10-13 01:46:23 UTC current episode first observed: 2026-10-13 20:21:07 UTC observed RIP window: 2026-10-13 01:46:23 UTC → 2026-10-13 20:21:07 UTC · 18.58h midpoint estimate ≈ 2026-10-13 11:03:45 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.resourcefixweb.comDomain record

The original observation time is not recorded for these hostnames.

使用技術 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

4 / 91 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of resourcefixweb.com · checked Sep 23, 2026

82
Needs Work
Performance
FCP
0.93s
First Contentful Paint
LCP
2.48s
Largest Contentful Paint
CLS
0.31
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.01s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
18.58
Estimate basis
Bounded by observations
Estimate precision
中

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history20

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

Earlier observations 15
  1. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→live_content

    content_served

  4. Availability monitor · Recorded state

    不明→live_content

    content_served

  5. Availability monitor · Recorded state

    不明→live_content

    content_served

  6. Availability monitor · Recorded state

    不明→live_content

    content_served

  7. Availability monitor · Recorded state

    不明→live_content

    content_served

  8. Availability monitor · Recorded state

    不明→live_content

    content_served

  9. Availability monitor · Recorded state

    不明→live_content

    content_served

  10. Availability monitor · Recorded state

    不明→live_content

    content_served

  11. Availability monitor · Recorded state

    不明→live_content

    content_served

  12. Availability monitor · Recorded state

    不明→live_content

    content_served

  13. Availability monitor · Recorded state

    不明→live_content

    content_served

  14. VirusTotal · Detection count

    2→3

  15. Availability monitor · First collection record

    到達可能

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    4/91 engine detections

    View source
  3. AlienVault OTX

    3 community references

    View source
  4. Added to PhishDestroy

    resourcefixweb.com

    View source

コミュニティ情報

コミュニティ報告:1 件

カテゴリPHISHING

I opened a support ticket on a Discord server for an AI API platform (AceDataCloud) about a failed crypto payment. An account posing as support ("Ticket Tool | Adm") asked for my wallet address, then sent a link to an external site (resourcefixweb.com) asking me to "validate my w

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

resourcefixweb.com

証拠および外部報告書

Community Scam Report — ChainAbuse
1 report filed for resourcefixweb.com (1 written by a person) · category: Phishing · source checked
“I opened a support ticket on a Discord server for an AI API platform (AceDataCloud) about a failed crypto payment. An account posing as support ("Ticket Tool | Adm") asked for my wallet address, then sent a link to an external site (resourcefixweb.com) asking me to "validate my wallet" by connecting MetaMask to it. This matches the pattern of a wallet drainer scam, where connecting and signing on such sites grants attackers unlimited approval to drain wallet funds. I did not click the link or co”
— reported by Anonymous on Sep 15, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

2 evidence signal groups linked 0 stored notification records 未検証

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

Template-based draft · optional AI wording assistance requires separate consent

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

FBIのガイドライン

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) resourcefixweb.com)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/embed/domain/resourcefixweb.com"
  title="PhishDestroy threat report for resourcefixweb.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>