VirusTotal
6 / 89 engine detections
打开报告
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@trustname.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
钓鱼: luckmega.com — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus DBL_SPAM…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 89 engine detections
打开报告DBL_SPAM
3 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
luckmega.com is an impersonation phishing site that passes itself off as a legitimate brand to win visitors' trust. Its targets are users who expect to log in, claim something or move money. PhishDestroy first flagged the domain on 2026-09-09. As of 2026-10-19 it was still online and redirecting visitors to another destination, so the lure is still active.
Impersonation pages copy the look, wording and flow of a service the victim already uses. Their aim is to make the victim enter credentials, personal details or payment information, or approve a transaction. The site does not need to steal anything technically. The victim hands it over, believing they are dealing with the real brand. Because luckmega.com now forwards traffic through a redirect, the page a visitor finally lands on can change without the domain itself changing.
Six of 89 engines on VirusTotal flagged the domain as of 2026-09-18: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That count is modest, so many security tools will still let the site load without a warning. Spamhaus separately lists the domain on its DBL as a spam domain, which shows it is also tied to unsolicited messaging, a common way phishing links are delivered. Three AlienVault OTX threat pulses reference it, and it appears on the PhishDestroy blocklist.
The domain was registered on 2026-07-13 through Fewmoretaps OU, trading as Trustname.com. It sat for about two months before PhishDestroy detected it, a gap often used to set up and warm a domain before it is pushed to victims. It resolves to an address on SKN-NETWORK-1, operated by SKN Subnet & Telecom Ltd, a network registered in Saint Kitts and Nevis and geolocated to the United States. The free automated certificate means the padlock icon proves nothing about who runs the site.
If you typed a password on luckmega.com, change it immediately on the real service and anywhere you reuse it, then turn on app-based two-factor authentication. If you entered card or bank details, contact your bank to block the card and dispute any charges. If you connected a crypto wallet or signed anything, revoke token approvals with a trusted approval checker, and move remaining funds to a fresh wallet if you shared a seed phrase. Defenders should block the domain and its redirect at DNS and proxy level, and search mail logs for messages containing it.
ns4.nameserverhub.comLocation describes the IP network.
25cfce7935a19c7147b8adf7b41b5b7b831295c7210918b14618333980d1a33aSaved 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.
luckmega.com
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
5→6
3→5
1→3
3 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePage captured
View source⚠️ ESCALATION #1 (0h active): Phishing - luckmega[.]com
luckmega.com
View sourcePD-1788907819-luckmega.com Recipient: abuse@trustname.com 如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
luckmega.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.