VirusTotal
9 / 91 engine detections
打开报告“Mayan Bridge”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 6 months 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.
冒充 Google: mayan.exchange — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 9/91 (ChainPatrol, alphaMountain.ai, BitDefender, CRDF, CyRadar); PhishDestroy score…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
9 / 91 engine detections
打开报告checked — no detections recorded
打开报告checked — no match recorded
23 community references
打开报告provider verdict: clean
打开报告12 已检查 — 未发现拦截
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
Mayan.exchange, a fake exchange site impersonating Google, is flagged by 3 out of 95 VirusTotal vendors and listed on 3 public blocklists, including MetaMask and SEAL. Despite its offline status, the domain's previous activity poses a significant threat, having been detected by PhishDestroy in April 2026.
The site, hosted by Cloudflare in Canada, used an SSL certificate issued by Google Trust Services, adding a deceptive layer of legitimacy. Its registration through NameCheap, Inc. and a moderate platform risk score of 63/100 highlight the need for vigilance against such sophisticated scams. The domain was active for nearly a year before being taken down, exploiting the trust users place in Google's brand.
Phishing domains like mayan.exchange capitalize on the gap between domain registration and antivirus database updates, often going undetected for crucial early periods. PhishDestroy's proactive detection pipeline identifies these threats during this vulnerable window, underscoring the importance of early threat intelligence. The site's takedown mitigates immediate risks, but the incident underscores the persistent threat of brand impersonation scams.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x413AFd270B7b5E5FBF6e07B841c9fC1c33c1330bFormat validated · Domain analysisIoC extraction recorded 2026-08-01 04:16:22 UTC
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 声誉不属于此域。
sergi.ns.cloudflare.comLocation describes the IP network.
08784cc88005cf32e402113809a7e371bb3277974280c46e4fca9f6ca75fb237Saved 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 mayan.exchange · checked Apr 15, 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.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://expireddomains.com/domain/mayan.exchange?utm_source=redi; server=openresty
mayan.exchange
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
不可用→可访问
可访问→不可用
No threat flag
View source23 community references
View source9/91 engine detections
View sourcemayan.exchange
View sourcePD-20260414-855374
由 1 名社区成员报告;首次发现于 2026年4月14日
PD-20260414-855374 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
mayan.exchange)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.