VirusTotal
6 / 91 engine detections
打开报告“301 Moved Permanently”
冒充 Google: pehowin.com — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 91 engine detections
打开报告Suspicious
打开报告3 community references
打开报告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
pehowin.com is an impersonation phishing domain. It is designed to pose as a legitimate service so visitors trust it with logins, personal details or funds. PhishDestroy first flagged it on 2026-09-28. As of 2026-10-19 the domain is still online and answers with a redirect rather than serving a page of its own.
Impersonation sites copy the name, look and wording of a service people already trust, then wait for victims who arrive through ads, messages or mistyped addresses. Once a victim believes they are on the real site, they are asked to sign in, verify an account or move money. Anything entered there goes to the operators: credentials, recovery details or payments. Here the page title reads "301 Moved Permanently", so the domain acts as a forwarding hop rather than displaying content directly, while our classification is impersonation phishing.
Six of 91 VirusTotal engines flagged the domain when it was checked on 2026-10-01: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That count is modest, but it comes from six unrelated vendors with separate detection pipelines, so it is not one tool's opinion. The domain also appears in three AlienVault OTX threat pulses, which means other researchers have tracked it as well. Among blocklists, PhishDestroy currently lists it.
The domain was registered on 2026-09-04 through Fewmoretaps OU d/b/a Trustname.com and was caught 24 days later. That short gap is typical of throwaway domains that are put to use soon after purchase. Traffic passes through Cloudflare, Inc. at an address geolocated to Canada, so the real origin server is not exposed. The certificate comes from Google Trust Services (WE1), a routine issuer that does not show who runs the site.
If you followed pehowin.com and typed a password anywhere along the way, change it on the genuine service right away. Turn on two-factor authentication and sign out any sessions you do not recognise. If you entered card or bank details or sent a payment, contact your bank or payment provider to dispute it and block further charges. Be on guard for follow-up messages that offer "help" in getting your money back. Defenders should block the domain and whatever it redirects to at the DNS and proxy level. They should also search logs for earlier visits and report the redirect chain to Cloudflare so the forwarding can be cut.
Edge-IP 声誉不属于此域。
zoe.ns.cloudflare.comLocation describes the IP network.
a6a044f4a9778b28a3acb456005b30b5bfefc4f665f13413187db95bb81809f8Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
5→6
4→5
3→4
2→3
0→2
No threat flag
View source3 community references
View source6/91 engine detections
View sourcepehowin.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
pehowin.com
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 ↗
pehowin.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
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.