VirusTotal
6 / 91 engine detections
打开报告“Secure Payment”
冒充 ["cash app"]: meappay.cash — 内容不可用. 证据摘要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, SOCRadar); Spamhaus DBL_SPAM…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 91 engine detections
打开报告DBL_SPAM
Scan report
打开报告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
meappay.cash is an impersonation phishing page that presented itself under the title "Secure Payment", posing as a legitimate checkout or payment service. Its targets are people who believe they are completing a payment or verifying an account. PhishDestroy first flagged the domain on 2026-09-27. The site has been offline since 2026-10-14 and was still unreachable when last checked on 2026-10-19.
Pages like this copy the look of a trusted payment flow, and the generic "Secure Payment" label is meant to reassure visitors that they are on a safe checkout screen. Victims typically arrive through a link in a message, ad or fake invoice, then are asked to enter card numbers, banking logins, account passwords or one-time codes to "confirm" a transaction. Anything typed into the form goes straight to the operators, who can use it to make purchases, take over accounts or resell the data. The ".cash" ending and payment-style name are part of the pitch, making the address look like it belongs to a money service.
Six of 91 VirusTotal engines flagged the domain as of 2026-10-01: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, SOCRadar and Webroot. That is a modest count, but it comes from vendors that independently reached the same verdict. Spamhaus lists the domain on its DBL as a spam domain, which suggests it was promoted through unsolicited messages. It also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered through NameCheap, Inc. on 2026-05-18, about four months before PhishDestroy detected it. That gap suggests the domain was registered well in advance and held before it was put to use. It was hosted in Singapore on the Webhosting Holdings LLC network at 160.30.208.11, behind a free Let's Encrypt certificate. The padlock only means the connection was encrypted. It does not mean the site was legitimate.
If you entered card details on this page, contact your bank or card issuer right away to block the card and dispute any charges you don't recognize. If you typed a password, change it everywhere you reused it and turn on two-factor authentication. Treat any codes you entered as compromised and watch for follow-up calls or texts posing as fraud teams. Defenders should block the domain and its IP at mail and web gateways and search 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.
ns1.hostnost.commx2.mxfilter.netpriority 10mx1.mxfilter.netpriority 10mx3.mxfilter.netpriority 20Location describes the IP network.
986ebd1de271afdc54a72fc3bddf58b84cff689fd1465085e98df0a7ec34f9b0ftp.meappay.cashmail.meappay.cashpop.meappay.cashsmtp.meappay.cashwebmail.meappay.cashwww.meappay.cashSaved 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.
ftp.meappay.cashDomain recordmail.meappay.cashDomain recordpop.meappay.cashDomain recordsmtp.meappay.cashDomain recordwebmail.meappay.cashDomain recordwww.meappay.cashDomain recordThe original observation time is not recorded for these hostnames.
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.
可访问→不可用
5→6
1→5
0→1
5→Observation retained
2→5
1→2
0→1
可访问
No threat flag
View source4 community references
View source6/91 engine detections
View sourcePD-20260927-EA1327
meappay.cash
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
meappay.cash
PD-20260927-EA1327 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 ↗
meappay.cash)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.