VirusTotal
15 / 92 engine detections
打开报告“Google”
冒充 Google: luxelayer.shop — 未验证 (HTTP 409). 证据摘要: VirusTotal 15/92 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker); Spamhaus…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
15 / 92 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
luxelayer.shop is a phishing site that presents itself as Google, right down to a browser tab titled simply "Google". Its targets are people with Google accounts, who are led to believe they are on a genuine Google page. PhishDestroy first flagged the domain on 2026-10-08, and it was still online when last checked on 2026-10-19.
Impersonation pages like this copy the look of a familiar Google screen, usually a sign-in or verification prompt, so the visitor types in their email address and password without a second thought. Anything entered goes to the operators, not to Google. A captured Google login can open Gmail, Drive, saved passwords and every service that uses "Sign in with Google". For crypto users that can include exchange accounts and the email inbox used for withdrawal confirmations and password resets. The domain name itself has nothing to do with Google, which is the clearest sign that the page is not what its title claims.
Fifteen of 92 VirusTotal engines flagged the domain as of 2026-10-08. They include established vendors such as BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CyRadar and Gridinsoft. Spamhaus lists it in its Domain Block List under the phishing category (DBL_PHISH), which means mail and DNS filters that use that feed will block it. The domain also appears in four AlienVault OTX threat pulses, so other researchers have tracked it independently of PhishDestroy.
The domain was registered on 2026-03-10 through West263 International Limited, about seven months before PhishDestroy caught it. That long gap suggests the domain was registered well in advance or used quietly before it drew attention. The site sits behind Cloudflare's network, with the visible address geolocated to Canada, so the actual origin server is hidden. Its TLS certificate comes from Google Trust Services. That makes the padlock and certificate details look reassuring, but it only confirms an encrypted connection. It does not mean Google runs the site.
If you entered a Google password here, change it immediately from a device you trust. Then sign out all other sessions in your Google account's security settings. Turn on two-step verification, ideally with a passkey or security key, and check your recovery email, recovery phone, Gmail forwarding rules and connected third-party apps for anything you did not add. Change passwords on any exchange or other service that shared the same password or relies on that inbox. Defenders should block the domain at DNS and mail gateways and search proxy logs for earlier visits.
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 声誉不属于此域。
ns1.dnsip.comns2.dnsip.comLocation describes the IP network.
5538bad3c59a888efc7a9d4a7d141be4b8d9e5cabb0d543867d6279bee758d97Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.luxelayer.shopDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of luxelayer.shop · checked Oct 8, 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.
http_other: raw=http_409; http=409; via=http_proxy; server=cloudflare
luxelayer.shop
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
未知→redirected
http_redirect
未知→redirected
http_redirect
可访问
No threat flag
View source4 community references
View source15/92 engine detections
View sourceluxelayer.shop
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 ↗
luxelayer.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
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.