VirusTotal
6 / 89 engine detections
打开报告“www.adobe.com”
冒充 Adobe: search-adobe.us — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 89 engine detections
打开报告DBL_PHISH
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
search-adobe.us is an impersonation phishing site that poses as Adobe, aimed at people who use Adobe accounts for Creative Cloud, Acrobat and document sharing. PhishDestroy first flagged it on 2026-08-31. As of 2026-10-19 the domain was still alive and serving a redirect, so it remains a live risk to anyone who lands on it.
The page sets its browser title to Adobe's own official web address, so a victim glancing at the tab sees what looks like the real site. The domain name adds to the illusion by combining 'search' with the brand, the kind of name that slips past someone clicking a search result, a shared-document notice or an email link. Impersonation pages like this usually present a familiar Adobe sign-in or 'view document' prompt and capture whatever is typed. Victims can lose their Adobe account, the files stored in it, and any other service where the same password is reused.
On 2026-09-14, 6 of 89 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a modest count, so many security tools will still let the page load without a warning. Other sources are firmer. Spamhaus lists the domain in its DBL under the phishing category, MetaMask and SEAL block it alongside PhishDestroy, and it appears in 4 AlienVault OTX threat pulses.
The domain was registered through Dynadot Inc on 2026-07-21, 41 days before PhishDestroy detected it. That gap suggests it was set up in advance rather than used the moment it was bought. Traffic runs through Cloudflare, with the address geolocated to Canada, which hides the actual origin server. The certificate comes from Google Trust Services, so the browser padlock appears as normal and says nothing about whether the site is genuine.
If you entered an Adobe email and password on this site, change your Adobe password right away from Adobe's official app or a bookmarked address. Then turn on two-step verification and sign out all active sessions. Change the password anywhere you reused it, and check your Adobe account for unfamiliar devices, shared files or billing changes. Treat any follow-up email about 'document access' or 'account verification' as suspect. Defenders should block search-adobe.us at DNS and the web proxy, and search mail and proxy logs for users who reached it so their credentials can be reset.
Last checked
Edge-IP 声誉不属于此域。
amanda.ns.cloudflare.comrandy.ns.cloudflare.comemx.mail.rupriority 10Location describes the IP network.
14e45ec7d13435f3e5a20e53b6b7dd401327c504146616abf0ce07f52c9d6335Saved 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://adobe.com/; server=cloudflare
search-adobe.us
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
3→4
可访问
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcesearch-adobe.us
View sourcePage captured
View sourceListed 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 ↗
search-adobe.us)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.