VirusTotal
6 / 92 engine detections
Відкрити звіт“リンク計測・配信停止の受付ドメイン / Link tracking and unsubscribe domain”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@internet.gmo.
The latest stored availability evidence still shows the domain reachable; 3 days 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.
фішинг: formlyx.net — Останній відомий активний (HTTP 200). Зведення доказів: VirusTotal 6/92 (BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
6 / 92 engine detections
Відкрити звіт2 det.
Відкрити звітSuspicious
Відкрити звіт4 community references
Відкрити звіт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
formlyx.net is an impersonation phishing page that presents itself as a bilingual Japanese and English link-tracking and unsubscribe domain. It appears built to reach people who click links in marketing-style emails, and its listing by wallet-focused blocklists places crypto users squarely in its audience. PhishDestroy first saw it on 2026-10-17, three days after registration. As of 2026-10-19 the site was alive and its content was live.
The page title reads "リンク計測・配信停止の受付ドメイン / Link tracking and unsubscribe domain", which describes a routine email service rather than a fraudulent one, while PhishDestroy classifies the site as impersonation phishing. Schemes like this borrow the look of trusted infrastructure, such as tracking redirects or unsubscribe forms, so a victim lowers their guard and follows the page's prompts. From there the visitor is typically pushed to enter an email address, account login or other personal details, or is passed on to a lookalike page that asks for wallet access or a recovery phrase. Whatever is typed in goes straight to the operators, who can use it to take over accounts or empty funds.
On 2026-10-17, VirusTotal showed 6 of 92 engines flagging the domain: BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft and Kaspersky. That is a modest detection rate, but it comes from several independent vendors and is typical of a newly launched phishing domain. MetaMask and SEAL list the domain alongside PhishDestroy, and it is referenced in 4 AlienVault OTX pulses.
The domain was registered on 2026-10-14 through GMO Internet Group, Inc. d/b/a Onamae.com. It resolves to 54.92.60.118 on Amazon.com, Inc. infrastructure located in Japan. Its TLS certificate was issued by Let's Encrypt (YE1), so the padlock in the browser says nothing about whether the site is legitimate.
If you opened formlyx.net, close it and do not return through any link that pointed you there. If you entered a password or email on the page, change that password at once, change it anywhere else you reused it, and turn on two-factor authentication. If you typed a wallet recovery phrase, treat that wallet as compromised and move your assets to a new wallet created on a trusted device. Defenders should block the domain and 54.92.60.118 at mail and web gateways and search inbound email for links to it. Report any related messages to your provider.
Last checked
01.dnsv.jp02.dnsv.jp03.dnsv.jp04.dnsv.jpLocation describes the IP network.
4de4c38a1f9fa4865eb24e4ff358979f9e0a9e06b6e86175efbd1d390a06efe3Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of formlyx.net · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://formlyx.net/https://formlyx.net/Server: nginx/1.24.0 (Ubuntu)Content-Type: text/html; charset=utf-8Content-Encoding: gzipkeep-alivegzipdefault-src 'self';script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://cdn.jsdelivr.net https://www.googletagmanager.com https://www.clarity.ms https://*.clarity.ms https://line-hunter.com;script-src-attr 'unsafe-inline';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;font-src 'stext/html; charset=utf-8same-originsame-originSat, 17 Oct 2026 03:48:23 GMTW/"863-a00EZKPk7k5KJql7ES0JeTxxUb8"?1camera=(), microphone=(), geolocation=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=(), payment=(self "https://js.stripe.com"), interest-cohort=()strict-origin-when-cross-originnginx/1.24.0 (Ubuntu)max-age=31536000; includeSubDomains; preloadchunkedAccept-EncodingnosniffoffnoopenDENYnonenoindex, nofollow0Values retained by the collector; long values may be shortened during collection.
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.
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
3→6
Доступний
No threat flag
View source4 community references
View source6/92 engine detections
View sourcePD-20261017-679D12
formlyx.net
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
formlyx.net
PD-20261017-679D12 Recipient: abuse@internet.gmo Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
formlyx.net)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.