VirusTotal
0 / 92 engine detections
Ouvrir le rapportUsurpation de Monad: monlock.xyz — Non vérifié. Résumé des preuves: VirusTotal 0/92; URLScan capture; 2 external blocklist matches (MetaMask, SEAL)…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
0 / 92 engine detections
Ouvrir le rapportScan report
Ouvrir le rapportno community references
Ouvrir le rapportScan report
Ouvrir le rapportNo threat flag
Ouvrir le rapportPage capture
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has listed monlock.xyz on its blocklist as a suspicious domain. The domain was first seen by PhishDestroy on 2026-10-20.
Because no specific scheme was identified, the listing does not confirm any particular malicious behavior. The domain could be used for typical phishing, fraud or malware distribution, but no concrete activity was observed.
VirusTotal scanned the site on 2026-10-13 with 92 engines and reported 0 detections. Google Safe Browsing checked the URL on 2026-10-20 and did not flag it. External blocklists showed 0 matches on 2026-10-20, while PhishDestroy’s internal list marked the domain as suspicious on the same day. OTX recorded 0 pulses for the domain as of 2026-10-20.
The domain was registered on 2026-09-30 through NameCheap, Inc. The recorded IP address for the site is 146.103.57.55, and the domain was observed 20 days after registration.
Do not enter credentials, personal data, or cryptocurrency information on the site; if you have already done so, change any associated passwords immediately. Monitor accounts for unexpected activity and consider reporting the domain to your security team. Defenders should add a rule to block traffic to monlock.xyz and review logs for any connections to the recorded IP.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
apollo.ns.cloudflare.comjamie.ns.cloudflare.comLocation describes the IP network.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.monlock.xyzDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of monlock.xyz · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://monlock.xyz/https://monlock.xyz/Cache-Control: no-cacheContent-Encoding: gzipContent-Type: text/html; charset=utf-8Server: Caddysummaryh3=":443"; ma=2592000no-cachegzip1267text/html; charset=utf-8Tue, 20 Oct 2026 13:18:38 GMT"dlyyxmr3tfcw-2eo-gzip"Wed, 07 Oct 2026 22:44:29 GMTCaddyAccept-EncodingValues retained by the collector; long values may be shortened during collection.
Page captured
View sourceNo threat flag
View source0/92 engine detections
View sourcemonlock.xyz
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
monlock.xyz
Listed domains receive at least one abuse report; this entry has no retained notification history.
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
monlock.xyz)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.