Ir para o relatório de segurança
Segurança de domínio e inteligência contra ameaças
monlock.xyz favicon

monlock.xyz

Registrador
NameCheap
Resolved IP
146.103.57.55
Registered
30/09/2026
PhishDestroy assessment Alto
First observed Oct 20, 2026 13:16 UTC · PhishDestroy
Correspondências da lista de bloqueio armazenada: 2 Rótulo automático de marca: Monad Domínio jovem: 19 dias atrás
20/10/2026
API
Este domínio foi sinalizado como malicioso
Listas de bloqueio públicas relatando uma correspondência: 2. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Resumo do relatório

Imitação de Monad: monlock.xyz — Não verificado. Resumo das evidências: VirusTotal 0/92; URLScan capture; 2 external blocklist matches (MetaMask, SEAL)…

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Source evidenceVirusTotal 0 / 92 6 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Alto
VirusTotal
0 / 92
Page captures
3

PhishDestroy threat report

Overview

PhishDestroy has listed monlock.xyz on its blocklist as a suspicious domain. The domain was first seen by PhishDestroy on 2026-10-20.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listado View source
PhishDestroy PhishDestroy list View source
SEAL Listado View source

Last checked

Captura armazenada · 3 captures

Automated brand references
Curve Monad Uniswap

Domain details

Domínio
Reputação do IP abuse score 0/100 0 reports checked 20/10/2026
Registrador NameCheap US(US)
RegistroCriado 30/09/2026 (19d · Very New!) — Expires 30/09/2027
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez20/10/2026
DOM Analysisanalyzed 20/10/2026score 15/1003 brand signals
Submitted URLhttp://monlock.xyz/
Favicon Hash
ID do caso
ICANN OVERSIGHT

Credenciamento e contexto RAA

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Nada é enviado automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
146.103.57.55
Network ASN
AS47447
Organization
23M GmbH
Observed location
Frankfurt am Main, DE

Servidores de nomes 2

  • apollo.ns.cloudflare.com
  • jamie.ns.cloudflare.com

Location describes the IP network.

Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.monlock.xyzDomain record

The original observation time is not recorded for these hostnames.

Denunciar este domínio Envie evidências e ajude a proteger outras pessoas
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of monlock.xyz · checked Oct 20, 2026

50
Needs Work
Performance
FCP
7.82s
First Contentful Paint
LCP
8.79s
Largest Contentful Paint
CLS
0.06
Cumulative Layout Shift
TBT
303ms
Total Blocking Time
SI
8.47s
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://monlock.xyz/
Final URL: https://monlock.xyz/
MonLock · Monad token launchpad
Launch a token on Monad with a fair bonding curve. When it sells out, its liquidity moves to Uniswap v4 and locks forever.
Resposta
HTTP 200
HTML body
3.0 KB
Compressed
1.2 KB
Links
0 internal · 0 external
Selected response headers
Cache-Control: no-cache
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Caddy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: MonLock · Monad token launchpad
Open Graph description: Fair launches on a bonding curve, anti-snipe built in, liquidity locked forever in Uniswap v4.
Twitter card: summary
Saved response-header values · 10
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
no-cache
Content-Encoding
gzip
Content-Length
1267
Content-Type
text/html; charset=utf-8
Date
Tue, 20 Oct 2026 13:18:38 GMT
Etag
"dlyyxmr3tfcw-2eo-gzip"
Last-Modified
Wed, 07 Oct 2026 22:44:29 GMT
Server
Caddy
Vary
Accept-Encoding

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

Recorded activity

4 entries
  1. URLScan

    Page captured

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    0/92 engine detections

    View source
  4. Added to PhishDestroy

    monlock.xyz

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

monlock.xyz

Evidências e relatórios externos

Análise aprofundada
Help & reporting

Você foi afetado por este site?

3 evidence signal groups linked 0 stored notification records Não verificado

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 você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes

Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →

Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

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

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

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

O que devo fazer agora mesmo?

Urgente

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

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do 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.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo monlock.xyz)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

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?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

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

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

embed.html
<iframe
  src="https://phishdestroy.io/pt-br/embed/domain/monlock.xyz"
  title="PhishDestroy threat report for monlock.xyz"
  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>