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

quicknode.fhlac.com

“Home”

レジストラ
Gname
Resolved IP
95.40.116.4
Registered
2015年1月11日
PhishDestroy assessment クリティカル
First observed Oct 16, 2026 14:39 UTC · PhishDestroy
VirusTotal 検出数: 17/92 保存されたブロックリストの一致: 2 自動ブランドラベル:Google Google Safe Browsing: threat flag recorded
2026年10月16日 1 Report Sent
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 17。 一致を報告する公開ブロックリスト: 2。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is complaint@gname.com. The latest stored availability evidence still shows the domain reachable; 4 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.

Elapsed since first report
4 days
Reports sent
1
Latest case ID
PD-20261016-EFC34E
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Reports sent
view timeline
レポート概要

Googleなりすまし: quicknode.fhlac.com — 未検証. 証拠の概要: VirusTotal 17/92 (ChainPatrol, BitDefender, CRDF, CyRadar, Ermes); URLScan malicious verdict; Google Safe…

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

Source evidenceVirusTotal 17 / 92 · Google Safe Browsing: flagged 6 sources

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

Analysis

クリティカル
VirusTotal
17 / 92
Page captures
2

PhishDestroy threat report

Overview

quicknode.fhlac.com is an impersonation phishing page that borrows the name of QuickNode, a blockchain RPC and node infrastructure provider. Its audience is developers and crypto users who would trust a QuickNode-branded address. PhishDestroy first flagged it on 2026-10-16. As of 2026-10-19 the site was still online and serving its phishing content.

How the scam works

Impersonation pages like this rely on a familiar brand in the hostname. The QuickNode label sits on an unrelated parent domain, so the address looks legitimate at a glance. The page carries only the bland title "Home", which gives nothing away in a browser tab or search result. Schemes that copy crypto infrastructure brands usually push visitors to sign in, which hands over account credentials and API keys. Others ask visitors to connect a wallet and approve a transaction or signature that gives the attacker control over tokens.

Evidence

VirusTotal shows 0 detections out of 92 engines as of 2026-10-16, so a clean result there means nothing for this site. Other sources disagree with that result. Google Safe Browsing flags the site for social engineering, and urlscan.io rates it malicious. MetaMask and SEAL list it alongside PhishDestroy. Because MetaMask's blocklist is among them, wallet users of that extension should see a warning before the page loads.

Infrastructure

The parent domain fhlac.com was registered on 2015-01-11 through Gname.com Pte. Ltd. That makes the domain over a decade old, so domain age offers no warning, and the QuickNode subdomain is what carries the deception. The site runs on Amazon's AMAZON-02 cloud network, with the address geolocated to Hong Kong. It uses a free Let's Encrypt certificate, so the padlock only means the connection is encrypted. It says nothing about who runs the site.

What to do

If you entered QuickNode or other login details here, change the password, enable two-factor authentication and review recent account activity. If you entered API keys or endpoint tokens, rotate them immediately. If you connected a wallet or signed anything, revoke token approvals with a reputable approval checker and move remaining funds to a fresh wallet if you signed an unknown message. Only reach QuickNode by typing its official address yourself. Defenders should block the full hostname and the fhlac.com parent domain, and should not treat the zero VirusTotal score as clearance. Abuse reports to the hosting provider and registrar can help take it down.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 掲載あり View source
PhishDestroy PhishDestroy list View source
SEAL 掲載あり View source

Last checked

保存済みキャプチャ · 2 captures

Domain details

ドメイン
URLScan verdict 悪意あり score 100 Phishing report ↗
Google Safe Browsing フラグ付き Social engineering checked 2026年10月20日
IPレピュテーション abuse score 2/100 2 reports PhishingBad Web Bot checked 2026年10月16日
Registrar (base domain) Gname CN(CN)
不正利用連絡先complaint@gname.com
ICANNレジストリICANN Lookup (RDAP) →
Registration (base domain)fhlac.com · 作成日 2015年1月11日 — Expires 2027年1月11日
技術詳細Provenance & timestamps
初確認2026年10月16日
DOM Analysisanalyzed 2026年10月16日score 80/100
Submitted URLhttp://quicknode.fhlac.com/
Favicon Hash
ケース ID
Observed page title
ホーム
TLS証明書
発行者 Let's Encrypt / YR2 · stored validity ends in 74 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
95.40.116.4
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Hong Kong, HK
Server header
nginx

ネームサーバー 2

  • a10.share-dns.com
  • b10.share-dns.net

Location describes the IP network.

TLS証明書

Issuer
Let's Encrypt / YR2
Valid from
2026-10-05 10:43:34
Valid until
2027-01-03 10:43:33
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf7b640e137a81204c2a47f4165b06dfe29661838d049d9cfbae731523dcd9ec9
Certificate names · 4 SANs
  • quicknode.miutone.com
  • quicknode.vhuatu.com
  • quicknode.yiguk.com
  • quicknode.zikaoe.com

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-19 22:31:50 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-19 01:54:24 UTC last content: 2026-10-19 01:54:24 UTC current episode first observed: 2026-10-19 08:21:20 UTC observed RIP window: 2026-10-19 01:54:24 UTC → 2026-10-19 08:21:20 UTC · 6.45h midpoint estimate ≈ 2026-10-19 05:07:52 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.
脅威情報の照合 · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
使用技術 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

17 / 92 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
ChainPatrol
BitDefender
CRDF
CyRadar
Ermes
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
カスペルスキー
LevelBlue
Lionic
SOCRadar
ソフォス
URLQuery
VIPRE

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of quicknode.fhlac.com · checked Oct 16, 2026

43
Poor
Performance
FCP
5.61s
First Contentful Paint
LCP
8.95s
Largest Contentful Paint
CLS
0.245
Cumulative Layout Shift
TBT
70ms
Total Blocking Time
SI
21.31s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://quicknode.fhlac.com/
QuickNode
対応
HTTP 200
HTML body
1.8 KB
Compressed
903 B
Links
0 internal · 2 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: b4ba1c96f64b44c6f9438051d441f3fa3b19ffc742f4e90b465c66324c6b7ae2
Saved response-header values · 10
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Fri, 16 Oct 2026 14:39:24 GMT
Etag
W/"6a9c54fa-726"
Last-Modified
Sat, 05 Sep 2026 17:44:26 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

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
6.45
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 history6

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

    live_content→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→live_content

    content_served

  4. Availability monitor · Recorded state

    不明→live_content

    content_served

  5. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

Earlier observations 1
  1. Availability monitor · First collection record

    到達可能

Recorded activity

5 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    17/92 engine detections

    View source
  3. Abuse report sent

    PD-20261016-EFC34E

    complaint@gname.com
  4. Added to PhishDestroy

    quicknode.fhlac.com

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

quicknode.fhlac.com

証拠および外部報告書

送信済み証拠のスナップショット
Sent: Ledger records: 1 Case ID: PD-20261016-EFC34E Recipient: complaint@gname.com
PDF notice generated Notice text archived (317 chars)
Abuse notice text as sent to the provider
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)
詳細な分析
Help & reporting

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

5 evidence signal groups linked 1 stored notification records 未検証
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およびドメイン 詐欺師が使用した(以下を含む) quicknode.fhlac.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/quicknode.fhlac.com"
  title="PhishDestroy threat report for quicknode.fhlac.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>