Security engines reporting a detection: 9. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
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.
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.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
RegistrationCreated Apr 14, 2026 (182d)—Expires Jun 28, 2026
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedApr 14, 2026
DOM Analysisanalyzed Oct 9, 2026score 95/10013 brand signals
IoC Extractionscanned Aug 1, 20261 wallet · 0 Telegram IoC
Submitted URLhttp://mayan.exchange/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:10:04 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 10:10:04 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
Google PageSpeed Insights — mobile performance audit of mayan.exchange· checked Apr 15, 2026
56
Needs Work
Performance
FCP
2.59s
First Contentful Paint
LCP
7.45s
Largest Contentful Paint
CLS
0.026
Cumulative Layout Shift
TBT
542ms
Total Blocking Time
SI
3.65s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-08-09 22:13:52 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-08-09 10:17:05 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
mayan.exchange detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · mayan.exchange
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches5
Same favicon hash or the same page title as this host.
Report 
