VirusTotal
17 / 91 engine detections
レポートを開く“Amazon Refund Check”
The sent-report ledger records the first outgoing report at .
The recorded recipient is domainabuse@tucows.com.
The latest stored availability evidence still shows the domain reachable; 25 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.
Amazonなりすまし: rhliey.com — 未検証. 証拠の概要: VirusTotal 17/91 (alphaMountain.ai, CRDF, ESET, Emsisoft, Forcepoint ThreatSeeker); URLQuery 2 det.; URLScan malicious…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 91 engine detections
レポートを開く2 det.
レポートを開く悪意あり
レポートを開くDBL_SPAM
悪意あり
レポートを開く5 community references
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
rhliey.com is a phishing page that impersonates Amazon under the title 'Amazon Refund Check', aimed at Amazon shoppers who are told they have money waiting. PhishDestroy first flagged it on 2026-09-25. As of 2026-10-19 the site was still online and serving its phishing content, so anyone receiving a link to it right now is at risk.
Refund lures play on a simple hook: a message claims an Amazon refund is pending and points to a 'check' page where the victim must confirm who they are to receive it. Pages like this typically ask for the Amazon login first, then card details, billing information or one-time codes under the pretext of sending the refund back to the right account. What the victim actually loses is control of their Amazon account and any payment card they type in, which can be used for fraudulent purchases or resold.
Seventeen of 91 VirusTotal engines classified the domain as malicious on 2026-10-03, including ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, Gridinsoft, CRDF and alphaMountain.ai. urlscan.io returned a malicious verdict and independently recognized Amazon branding on the page. Spamhaus lists the domain in its DBL as a spam domain, which fits links being pushed through bulk messages, and it appears in five AlienVault OTX threat pulses. Beyond the PhishDestroy blocklist, it is not yet on other major blocklists.
The domain was registered through Tucows on 2026-09-21, just four days before PhishDestroy caught it, a short turnaround typical of throwaway phishing domains. It is hosted on the AVA HOST SRL network in Moldova. The site uses a TrustAsia LiteSSL certificate, so the padlock in the browser only means the connection is encrypted, not that the page belongs to Amazon.
If you entered your Amazon credentials on this site, change your Amazon password immediately, sign out of all devices, and enable two-step verification; change the same password anywhere else you reused it. If you entered card details, call your bank to block the card and dispute any charges you do not recognize, and review your Amazon order history and saved addresses for changes. Real Amazon refunds are issued automatically to the original payment method and never require you to re-enter card data on an outside page. Defenders should block rhliey.com at DNS and email gateways, and hunt mail logs for messages linking to it to identify targeted users.
addyson.ns.cloudflare.combrad.ns.cloudflare.comLocation describes the IP network.
5596d1ee4f0e0dfd41cb47de804afa6461ba7c0ac04e10ff9abcf2bd34ce7680Saved 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 rhliey.com · checked Sep 25, 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.
rhliey.com
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
不明→live_content
content_served
protected→live_content
content_served
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
18→17
不明→live_content
content_served
No threat flag
View source5 community references
View source17/91 engine detections
View sourcePD-20260925-2289FF
Page captured
View sourcerhliey.com
View sourcePD-20260925-2289FF Recipient: domainabuse@tucows.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 ↗
rhliey.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.