Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
网络安全情报 Registrar context
Registrar contextTrustname
Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
magonex.com is on the PhishDestroy blocklist as a suspicious domain. It does not openly imitate a known brand, and we have not yet assigned it a specific scam type. PhishDestroy first flagged it on 2026-10-06. On 2026-10-19 it was still online, and instead of serving its own page it redirected visitors to another destination.
How the scam works
The domain works as a redirect, so the page a visitor ends up on is not hosted at magonex.com itself. Redirecting domains like this are commonly used to send traffic onward to a landing page that can be swapped out at any time. That page might ask for login details, a wallet connection or a payment. Because the final destination can change without the domain changing, a link that looks harmless today may lead somewhere harmful tomorrow. Until it is classified more precisely, treat anything reached through magonex.com as untrusted, and do not enter credentials, seed phrases or funds there.
Evidence
On 2026-10-10, six of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a minority of engines. Still, six vendors with different detection methods reaching the same verdict on their own is a meaningful signal. The domain also appears in four AlienVault OTX threat pulses, which means other researchers have tied it to tracked malicious activity. Among the blocklists we checked, only PhishDestroy currently lists it.
Infrastructure
The domain was registered on 2026-07-30 through Fewmoretaps OU, which trades as Trustname.com. It was flagged 68 days later. That gap fits a domain that was registered, left idle, and then put into use. The site sits behind Cloudflare, with the address located in Canada. Because Cloudflare acts as a front, the server that actually hosts the content stays hidden. The Google Trust Services certificate is the standard one Cloudflare issues automatically, so the padlock says nothing about whether the site is legitimate.
What to do
If you followed a link through magonex.com, do not act on anything the destination page asked of you. If you typed a password there, change it on the real service and turn on two-factor authentication. Never send funds or share recovery phrases with a site you reached this way. If you paid for something, contact your payment provider. Security teams should block magonex.com at DNS and proxy level and check logs for past visits. They should also watch for any domains it redirects to, since the final landing page may change.
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-20 10:06:53 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-20 10:06:53 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.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(BY)
PhishDestroy Investigation
