VirusTotal
6 / 92 engine detections
Відкрити звітфішинг: magonex.com — Останній відомий активний (HTTP 301). Зведення доказів: VirusTotal 6/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
6 / 92 engine detections
Відкрити звіт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
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.
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.
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.
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.
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.
Репутація Edge-IP не пов’язана з цим доменом.
mallory.ns.cloudflare.comLocation describes the IP network.
87e247789f048ad9ddb80365445e15acab9bc73d1e5b926b5399a67e79a03047Saved 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.
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
No threat flag
View source6/92 engine detections
View source4 community references
View sourcemagonex.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
magonex.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
magonex.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
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.