VirusTotal
6 / 92 engine detections
Buka laporan“リンク計測・配信停止の受付ドメイン / Link tracking and unsubscribe domain”
Peniruan MetaMask: formlyx.jp — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 6/92 (BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
6 / 92 engine detections
Buka laporanDBL_SPAM
4 community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
formlyx.jp is an impersonation phishing page. It presents itself as a Japanese link tracking and unsubscribe domain, and it is listed on the MetaMask and SEAL blocklists, which focus on crypto users. PhishDestroy first detected it on 2026-10-17, three days after the domain was registered. As of 2026-10-19 the site was still online and serving content.
The page title reads "リンク計測・配信停止の受付ドメイン / Link tracking and unsubscribe domain," which frames the site as harmless mailing infrastructure. We classify it as impersonation phishing, so the title and the classification point in different directions. Impersonation pages of this kind borrow a trusted identity to get visitors to act. They typically ask for login credentials, personal details, or wallet recovery phrases, or they push visitors to approve actions they would refuse on an unfamiliar site. Anything entered on such a page goes straight to the operators.
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 count, though typical for a domain only days old. Spamhaus lists it in its Domain Blocklist as spam (DBL_SPAM). Four AlienVault OTX pulses reference it. Besides PhishDestroy, it is blocked by MetaMask and SEAL.
The domain was registered on 2026-10-14. It resolves to 54.92.60.118 on Amazon.com, Inc. infrastructure located in Japan. Its TLS certificate comes from Let's Encrypt (YE1), so the padlock in the browser says nothing about whether the site is legitimate.
If you opened formlyx.jp from an email or message, close it and do not click any unsubscribe or tracking links in that message. If you entered a password, change it right away on the real service and on any other account that uses the same password, then turn on two-factor authentication. If you typed a wallet recovery phrase, treat that wallet as compromised and move your funds to a newly created wallet. Defenders should block the domain and its IP at mail and web gateways, and search mail logs for messages that link to it.
Last checked
01.dnsv.jp02.dnsv.jp03.dnsv.jp04.dnsv.jpLocation describes the IP network.
ff094ee57f5ae4cde3f945df021aeb61bae5c8080e81958514429a2f14afacbbSaved 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.jp · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://formlyx.jp/https://formlyx.jp/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:55:33 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.
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Dapat dijangkau
No threat flag
View source4 community references
View source6/92 engine detections
View sourceformlyx.jp
View sourcePage captured
View source79 domain serupa tersimpan
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
formlyx.jp
Listed domains receive at least one abuse report; this entry has no retained notification history.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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.jp)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.