VirusTotal
6 / 89 engine detections
レポートを開く“404 Not Found”
Googleなりすまし: havaianasne.shop — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Netcraft)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 89 engine detections
レポートを開く4 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
havaianasne.shop is an impersonation phishing site built around the Havaianas footwear brand. Its name tacks a couple of extra letters onto the brand and uses a cheap .shop extension, a pattern aimed at bargain-hunting shoppers who arrive from ads or social media links. PhishDestroy first flagged it on 2026-09-04. As of 2026-10-19 the domain was still online and serving content.
Brand-impersonation shops like this mimic a familiar retailer, advertise steep discounts, and push visitors through a checkout that harvests names, addresses, phone numbers and payment card details. Victims typically receive nothing, or a cheap counterfeit, while their card data is reused or sold. When we checked, the page title read "404 Not Found", which differs from the impersonation classification we assigned.
On 2026-09-18, six of 89 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Netcraft and SOCRadar. That is a modest count. Many browsers and filters will still load the site without warning, so the absence of a red screen should not reassure anyone. The domain also appears in four AlienVault OTX threat pulses, which means other researchers have tracked it independently. Among blocklists, it is listed by PhishDestroy.
The domain was registered through Spaceship, Inc. on 2026-08-29, and we caught it just six days later. That short gap fits a disposable storefront spun up for a quick campaign. Traffic passes through Cloudflare, Inc. on an address geolocated to Canada, which hides the real origin server. The site holds a Google Trust Services (WE1) certificate, so it shows a padlock like any legitimate store, and that padlock says nothing about who runs it.
If you entered card details on havaianasne.shop, call your bank now to block the card and dispute the charges. Then watch your statements for small test transactions. If you created an account with a password you use elsewhere, change it on those other services and turn on two-factor authentication. Expect follow-up phishing by email or SMS that refers to your "order", and buy Havaianas products only through the brand's official channels or known retailers. Defenders should block the domain at DNS and proxy level, flag lookalike Havaianas .shop domains in mail and ad filtering, and report the site to the brand's protection team.
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 の評判はこのドメインに起因しません。
rick.ns.cloudflare.comLocation describes the IP network.
1c36197f07b0c81719d276522f8b5e6e2bdff52a85c679718593fb31e3e47936Saved 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 havaianasne.shop · checked Sep 4, 2026
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
不明→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
不明→live_content
content_served
利用不可→到達可能
到達可能→利用不可
2→3
到達可能
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePage captured
View sourcehavaianasne.shop
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
havaianasne.shop
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
havaianasne.shop)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.