Vai al rapporto di sicurezza
Pannello di controllo analitico
Domain security report
formlyx.jp favicon

formlyx.jp

“リンク計測・配信停止の受付ドメイン / Link tracking and unsubscribe domain”

Verdetto di minaccia
CriticoRicorso in materia di domini
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilità Ultimo attivo conosciuto Ultima osservazione di raggiungibilità memorizzata Osservato · HTTP probe
Segnali di rischio
Rilevamenti VirusTotal: 6/92 Spamhaus DBL: DBL_SPAM Corrispondenze della blocklist memorizzate: 2 Automated brand label: MetaMask Dominio giovane: 3 giorni
OTX: 4 refs 17/10/2026 MetaMask
API
Resolved IP
54.92.60.118
Registered
14/10/2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Fonte
Primary capture
Collected · UTC
Open capture
In this reportGet help
Questo dominio è stato segnalato come dannoso
Motori di sicurezza che segnalano un rilevamento: 6. Blocklist pubbliche che segnalano una corrispondenza: 2. Prestare estrema cautela: non inserire credenziali o informazioni personali.
Riepilogo del rapporto

formlyx.jp — Ultimo attivo conosciuto (HTTP 200). Simulazione del marchio: MetaMask; Tipo di truffa: Impersonation. Riepilogo delle prove: VirusTotal 6/92 (BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft); URLScan capture; Spamhaus DBL_SPAM; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100.

L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
VirusTotal
VirusTotal
6 det.
OTX references
4 community refs
URLScan
URLScan
Segnala ↗
Certificato TLS
Within stored validity dates
Let's Encrypt / YE1 · Hostname coverage not recorded
Età
3d Brand New!
Stato osservato
Ultimo attivo conosciuto 200
PhishDestroy
Elenco da eliminare
Presente

Source evidence

7 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

6 / 92

Segnala
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Dettagli
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_SPAM

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

Segnala
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Segnala
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

rapporto memorizzato

View stored capture ↗
Segnala
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Segnala
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Riepilogo delle prove

Critico
VirusTotal
6/92
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

The domain formlyx.jp was first observed on 2026-10-17, with a recorded entry from the MetaMask blocklist on that date. This observation provides a reference point for its presence in external security listings and supports further technical comparison.

Recorded Evidence

VirusTotal checked formlyx.jp on 2026-10-17, documenting 6 detections out of 92 scanners. The domain was listed on both MetaMask and SEAL external blocklists as of 2026-10-17. OTX referenced four pulses for the domain on 2026-10-17, and PhishDestroy internally listed it. The registration date is recorded as 2026-10-14, and the SSL certificate was issued by Let's Encrypt / YE1, scanned on 2026-10-17. The PageSpeed performance score was measured at 100 on 2026-10-17.

Interpretation

VirusTotal provides a quantitative measurement of detections across multiple scanners, documenting the technical review of formlyx.jp. PhishDestroy contains an internal listing, which records domains for monitoring within its system. The evidence from OTX, MetaMask, and SEAL blocklists adds context about external intelligence entries, while the registration and SSL scan dates offer infrastructure timeline references.

Recommended Actions

For formlyx.jp, preserve the VirusTotal record and its detection count for ongoing comparison. Retain the OTX pulse references and PhishDestroy internal listing as part of the domain’s evidence profile. Keep the MetaMask and SEAL blocklist entries for historical and security review.

Data coverage & collection

21 · datasets with records / 10 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
6 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
pulitoCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
Registration dates retainedCollection time not recorded
Network & DNS
54.92.60.118 · 4 · nameserversCollection time not recorded
Certificato TLS
Let's Encrypt / YE1
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
100/100 · mobile performance
Availability history
2 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Response records
  • Recorded subdomains
  • Segnalazioni della comunità
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Stato della lista di blocco pubblica

Domain, network & archive

54.92.60.118 · DNS, TLS and retained responses

Domain details

Dominio
Reputazione IP abuse score 0/100 0 reports checked 17/10/2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodominidrainerfraudlivemonthlyphishdestroyphishingscam
RegistrazioneCreato 14/10/2026 (3d · Brand New!) — Expires 31/10/2027
Stato HTTP200
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta17/10/2026
DOM Analysisanalyzed 17/10/2026score 100/100
Submitted URLhttp://formlyx.jp/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
54.92.60.118
Network ASN
AS16509
Organization
AWS EC2 (ap-northeast-1)
Observed location
Tokyo, JP
Server header
nginx/1.24.0 (Ubuntu)
Nameserver 4
  • 01.dnsv.jp
  • 02.dnsv.jp
  • 03.dnsv.jp
  • 04.dnsv.jp

Location describes the IP network.

Certificato TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-10-14 02:49:24
Valid until
2027-01-12 02:49:23
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-17 04:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintff094ee57f5ae4cde3f945df021aeb61bae5c8080e81958514429a2f14afacbb

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 54.92.60.118rapiddns.io

Latest Classified Outcome 2026-10-17 11:01:00 UTC

Primary outcome Contenuto attivo reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenuto attivo Ordinary HTTP content served 90% 2026-10-17 11:01:00 UTC
RDAP registration Sconosciuto
Observed timeline last reachable: 2026-10-17 11:01:00 UTC last content: 2026-10-17 11:01:00 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.
Tecnologie · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Segnala questo dominio Invia le prove e contribuisci a proteggere gli altri

Analisi di VirusTotal

6 / I fornitori di sicurezza 92 hanno contrassegnato questo dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
BitDefender
CRDF
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Kaspersky
Analisi delle prestazioni del sito

Google PageSpeed Insights — mobile performance audit of formlyx.jp · checked Oct 17, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.32s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://formlyx.jp/
Final URL: https://formlyx.jp/
リンク計測・配信停止の受付ドメイン / Link tracking and unsubscribe domain
Risposta
HTTP 200
HTML body
2.1 KB
Compressed
1.2 KB
Links
0 internal · 2 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.24.0 (Ubuntu)
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 22
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
default-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 's
Content-Type
text/html; charset=utf-8
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Sat, 17 Oct 2026 03:55:33 GMT
Etag
W/"863-a00EZKPk7k5KJql7ES0JeTxxUb8"
Origin-Agent-Cluster
?1
Permissions-Policy
camera=(), microphone=(), geolocation=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=(), payment=(self "https://js.stripe.com"), interest-cohort=()
Referrer-Policy
strict-origin-when-cross-origin
Server
nginx/1.24.0 (Ubuntu)
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Content-Type-Options
nosniff
X-DNS-Prefetch-Control
off
X-Download-Options
noopen
X-Frame-Options
DENY
X-Permitted-Cross-Domain-Policies
none
X-Robots-Tag
noindex, nofollow
X-XSS-Protection
0

Values retained by the collector; long values may be shortened during collection.

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-17 03:55:33 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-17 03:55:33 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-17 03:55:33 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Analisi di rilevamento ed evasione

Verifica del cloaking e della distribuzione del traffico

Non ancora scansionato Non è stata ancora rilevata alcuna differenza tra crawler e browser

Osservazioni archiviate relative al confronto tra crawler e browser per questo host, oltre a una verifica in tempo reale delle impronte digitali per i sistemi di distribuzione del traffico in stile Keitaro.

Flag di occultamento memorizzato
Non ancora scansionato
Ultima scansione di occultamento
Intestazione del server rilevata dallo scanner
nginx/1.24.0 (Ubuntu)
Indirizzamento delle acquisizioni
Local archiviato l'2026-10-17 03:55:33, UTC

Nota dello scanner: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.24.0 (Ubuntu)

Verifica delle impronte digitali in tempo reale TDS
Sette indicatori Keitaro e un confronto tra browser e crawler. Una nuova scansione parte solo premendo il pulsante.
Su richiesta

Nessun risultato di verifica live salvato.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-10-17 03:54:29 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 54.92.60.118.
Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Sconosciuto→live_content

    content_served

  2. Availability monitor · First collection record

    Raggiungibile

  3. Availability monitor · Recorded state

    Sconosciuto

    probe_inconclusive

Pipeline di risposta alle minacce

Scoperta
Analysis
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Minaccia rilevata
formlyx.jp rilevati e inseriti in coda per un’analisi completa
17/10/2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
17/10/2026
URLScan.io Capture
Memorizzato URLScan report with capture artifacts
17/10/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
6/92 recorded on VirusTotal
17/10/2026
Rilevamento delle liste di blocco
Si trova in 2 blocklists: MetaMask, SEAL
17/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
17/10/2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
17/10/2026
Technical Analysis Recorded
Il report contiene tecnologia archiviata o risultati di analisi forensi.
17/10/2026
DestroyList pubblicato
Listed in the public PhishDestroy/DestroyList repository
17/10/2026
Monitoring Continues
Il dominio rimane raggiungibile o ad accesso limitato; controlli futuri potrebbero aggiornare questa osservazione.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecRecensione del sito AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Domini simili

79 domini simili memorizzati

etamask.io omission Report interno meetamask.io repetition Report interno megamask.io replacement Report interno metam.ask.io subdomain Report interno metamaak.io replacement Report interno metamadk.io replacement Report interno metamaks.io transposition Report interno metamassk.io insertion Report interno metamsask.io insertion Report interno metamssk.io replacement Report interno metanask.io homoglyph Report interno metanmask.io homoglyph Report interno
Mostra tutto (67)
metasmask.io insertion Report interno metramask.io insertion Report interno mewtamask.io insertion Report interno mmetamask.io homoglyph Report interno mtamask.io omission Report interno mwetamask.io insertion Report interno nmetamask.io homoglyph Report interno metamark.io bitsquatting Report interno metamaskj.io addition Report interno metammask.io homoglyph Report interno metamnask.io homoglyph Report interno emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Dati e relazioni esterne

Analisi della sicurezza
URLScan Stored capture VirusTotal 6 det. ChainPatrol URLQuery SSL Laboratori Hostname coverage not recorded CF Radar Apri il rapporto OTX 4 refs WOT ScamAdviser Verifica lista nera URLVoid Sucuri SiteCheck Osservatorio MDN
OSINT e intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificati WHOIS Wayback
DNS e rete
nslookup.io DNS bgp.tools ASN /Percorso
SEO e dominio
SpyFu Moz DA/PA Ahrefs Backlink
Analisi approfondita
Analisi approfondita

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Questo sito ti ha influenzato in qualche modo?

4 evidence signal groups linked 0 stored notification records Ultimo attivo conosciuto

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.

Immediate steps Find reporting contacts
Official reporting routes
Europol
Trova il canale di segnalazione ufficiale per il tuo paese dell'UE
National police directory
Find your country
PhishDestroy listing review Non un rapporto delle forze dell'ordine
Ricorso in materia di domini
Richiedi una revisione se possiedi questo dominio e ritieni che l'elenco non sia corretto
Attenzione ai truffatori che promettono il recupero dei fondi! I criminali possono contattare nuovamente le vittime fingendo di essere investigatori, avvocati o agenti di recupero. Non pagare commissioni anticipate né condividere credenziali. Scopri di più sulle frodi relative ai sussidi di recupero →
Segnalalo alle autorità locali

Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.

Elenco di 97 paesi

Template-based draft · optional AI wording assistance requires separate consent

Bozza assistita dall'intelligenza artificiale: i dettagli dell'incidente vengono elaborati dal fornitore di intelligenza artificiale · Controllalo e invialo tu stesso
After a phishing incident

Raccomandazioni e consigli per le vittime

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Cosa devo fare subito?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifica tutte le password — e-mail, account Exchange, qualsiasi servizio che utilizzi la stessa password
  • Abilita l'autenticazione a due fattori (2FA) utilizzando un'app di autenticazione (non via SMS). Disattiva il recupero tramite SMS
  • Carte congelate se hai inserito i tuoi dati bancari sul sito di phishing

Quali informazioni devo raccogliere per la mia relazione?

Linee guida dell'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.
  • Date e orari esatti — di ogni transazione e del primo contatto con il truffatore
  • Schermate — siti web truffaldini, messaggi in chat, e-mail, transazioni tramite portafoglio digitale, social media
  • Tutti gli URL e i domini utilizzato dal truffatore (tra cui formlyx.jp)
  • Comunicazioni — e-mail, SMS, numeri di telefono, nomi utente utilizzati dal truffatore

Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.

A chi devo segnalare la truffa?

  • FBI IC3 — Internet Crime Complaint Center (sistema di segnalazione federale degli Stati Uniti)
  • Europol — Segnalazioni relative alla criminalità informatica in Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polizia locale — crea un documento ufficiale, anche se non è in grado di agire immediatamente

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?

  • Siti web fasulli — cloni perfetti, al pixel, di siti legittimi con domini leggermente modificati
  • Macellazione dei suini — fiducia conquistata nel corso di settimane tramite Telegram/WhatsApp/app di incontri, per poi rubare i soldi
  • Truffe legate al recupero dei fondi — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Truffe basate sull'intelligenza artificiale — i deepfake, il phishing automatizzato e i siti generati dall’intelligenza artificiale rendono più difficile individuare le frodi

Come posso proteggermi in futuro?

  • Aggiungi i siti ufficiali ai preferiti — Non cliccare mai sui link contenuti nelle e-mail, nei messaggi diretti o negli annunci pubblicitari
  • Verifica i domini — controllare PhishDestroy prima di interagire. Verifica l'HTTPS, l'ortografia e l'età del dominio
  • "Troppo bello per essere vero" = truffa — rendimenti garantiti, testimonial di personaggi famosi, scadenze urgenti

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Verifica qualsiasi dominio

Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica

Scansiona ora

Segnala un tentativo di phishing

Segnala i domini sospetti al nostro database delle minacce — proteggi la comunità

Segnala

Feed in tempo reale sulle minacce

Segnalazioni recenti di phishing e modifiche osservate della disponibilità

Monitora

Rimani informato, rimani al sicuro

Controlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo

Feed in tempo reale sulle minacce Contesta questo annuncio
Read the evidence in context

Informazioni su questo rapporto: formlyx.jp

Questo rapporto presenta le ultime prove archiviate disponibili per PhishDestroy. I timestamp della sorgente vengono mostrati ove disponibili; la disponibilità e i verdetti del fornitore possono cambiare dopo il ritiro.

Il sito catturato mostrava il titolo della pagina “リンク計測・配信停止の受付ドメイン / Link tracking and unsubscribe domain” e potrebbe spacciarsi per MetaMask.

Al momento di 2026-10-17 04:57:47 UTC, formlyx.jp ha ricevuto rilevamenti dai motori di sicurezza 6.

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Se ritieni che questo elenco sia impreciso, presentare ricorso. Per conoscere la nostra metodologia, visita Pagina delle domande frequenti.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Incorpora questo rapporto

Condividi queste informazioni sulle minacce sul tuo sito web o sul tuo blog

embed.html 
<iframe
  src="https://phishdestroy.io/it/embed/domain/formlyx.jp"
  title="PhishDestroy threat report for formlyx.jp"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>