Ir para o relatório de segurança
Domain security report
cloudenginelab.web.app favicon

cloudenginelab.web.app

“Site Not Found”

Veredicto de ameaça
Assessment sources

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

Disponibilidade Último ativo conhecido Última observação de acessibilidade armazenada Observado · HTTP probe
Detecções do VirusTotal: 2/91 Correspondências da lista de bloqueio armazenada: 2 Automated brand label: MetaMask
31/07/2026 MetaMask CDN
API
Registrador
Google Firebase
Resolved IP
199.36.158.100
0 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 2. Listas de bloqueio públicas relatando uma correspondência: 2. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
Resumo do relatório

cloudenginelab.web.app — Último ativo conhecido (HTTP 301). Representação da marca: MetaMask; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 2/91 (alphaMountain.ai, Forcepoint ThreatSeeker); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 83/100. Registrador: Google Firebase.

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

Additional indicators at a glance

VirusTotal
VirusTotal
2 det.
Certificado TLS
Hostname mismatch
Google Trust Services · Certificate hostname mismatch
Status observado
Último ativo conhecido 301
PhishDestroy
DestroyList
Listado

Source evidence

5 · 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

2 / 91

Denunciar
Interpretation & limits

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

Public blocklists

2 external matches

Detalhes
Interpretation & limits

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

OTX

no community references

Denunciar
Interpretation & limits

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

CF Radar

provider verdict: clean

Observation time not recorded
Denunciar
Interpretation & limits

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

Google Safe Browsing

Checked; no threat flag recorded

Denunciar
Interpretation & limits

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

Resumo das evidências

Crítico
VirusTotal
2/91

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

cloudenginelab.web.app returned an HTTP 404 status in a check recorded on 2026-10-01, according to the HTTP response observation. The domain was first observed on 2026-07-31, and a PageSpeed check on 2026-08-10 recorded a performance score of 93.

Recorded Evidence

An HTTP check recorded on 2026-10-01 returned status 404 for cloudenginelab.web.app. The first observation of the domain is dated 2026-07-31. A PageSpeed assessment dated 2026-08-10 recorded a performance score of 93. VirusTotal, checked on 2026-08-12, reported 2 detections across 91 scanners. The external blocklist review on 2026-10-02 listed 2 external blocklists: MetaMask and SEAL. An SSL scan on 2026-08-21 identified the issuer as Google Trust Services / WR4.

Interpretation

The recorded HTTP 404 describes only the response captured on that date, not the domain's broader content. The PageSpeed score reflects a single dated measurement rather than a persistent performance level. The VirusTotal detections and external blocklist listings are separate source observations that should not be combined into a single verdict. The chronology from first observation to the later checks shows the domain was recorded across multiple dates, but the dates alone do not establish a trend.

Recommended Actions

For cloudenginelab.web.app, preserve the HTTP response record, the PageSpeed result, and the VirusTotal report as separate source documents. Compare the external blocklist listings against the VirusTotal detections in a later review, keeping each source's own record distinct. Recheck the domain's HTTP response and PageSpeed score to see whether the recorded values persist. Retain the SSL scan record alongside the other observations for future comparison.

Data coverage & collection

15 · datasets with records / 16 · 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
2 / 91 · engine detections
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
limpoCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Google FirebaseCollection time not recorded
Network & DNS
199.36.158.100 · 0 · nameserversCollection time not recorded
Certificado TLS
Google Trust Services
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
93/100 · mobile performance
Availability history
7 · stored state changes
Source observation history
4 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 16

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

  • URLScan analysis
  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Page captures
  • HTML archives
  • Page analysis
  • Observed indicators
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Denúncias da comunidade
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Status da lista de bloqueios pública

Domain, network & archive

Google Firebase · 199.36.158.100 · DNS, TLS and retained responses

Domain details

Domínio
IP Context Fastly shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
Provedor de plataforma Google Firebase US(US)
Status HTTP301 Moved Permanently
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez31/07/2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
199.36.158.100
Network ASN
AS54113
Organization
Google LLC
Observed location
Mountain View, US

A reputação do Edge-IP não é atribuída a este domínio.

Location describes the IP network.

Certificado TLS

Issuer
Google Trust Services
Valid from
2026-07-20 14:59:55
Valid until
2026-10-18 14:59:54
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-08-21 07:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd69d48c3edf1af146f82e0e40950ba1d2c2a6ac9875657536c51cd7e9b82591b
Certificate names · 1 SANs
  • web.app

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

Latest Classified Outcome 2026-10-16 10:05:29 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-16 10:05:29 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-16 10:05:29 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.
Tecnologias · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

2 / Os fornecedores de segurança 91 sinalizaram este domínio
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of cloudenginelab.web.app · checked Aug 10, 2026

93
Good
Performance
FCP
2.56s
First Contentful Paint
LCP
2.56s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.56s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable 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

Análise de detecção e evasão

Verificação de cloaking e distribuição de tráfego

Ainda não foi digitalizado Ainda não foi registrada nenhuma diferença entre o rastreador e o navegador

Observações armazenadas comparando o rastreador com o navegador para este host, além de uma verificação em tempo real da assinatura digital para sistemas de distribuição de tráfego do tipo Keitaro.

Sinalizador de camuflagem armazenado
Ainda não foi digitalizado
Última varredura de camuflagem
Cabeçalho do servidor detectado pelo scanner
Varnish

Nota do digitalizador: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://cloudenginelab.web.app/; server=Varnish

Verificação de impressão digital “TDS” em tempo real
Sete indicadores do Keitaro e uma comparação entre navegador e rastreador. Uma nova análise começa somente ao pressionar o botão.
Resultado salvo
Cloaked / Filtered

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. Domain Status Transition 2026-10-09 01:23:56 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-09-11 01:15:37 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. Domain Status Transition 2026-08-10 10:00:21 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  4. Threat First Observed 2026-08-10 06:13:11 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive.
Stored observation history11

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

    inactive→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Indisponível→Acessível

  3. Availability monitor · Recorded state

    inactive→Desconhecido

    stale_current_evidence

  4. Availability monitor · Recorded state

    Desconhecido→inactive

    hosting_placeholder · placeholder_page

  5. Availability monitor · Recorded state

    inactive→Desconhecido

    stale_current_evidence

Earlier observations 6
  1. Availability monitor · Recorded state

    Desconhecido→inactive

    hosting_placeholder · placeholder_page

  2. Availability monitor · Recorded state

    Desconhecido

    stale_current_evidence

  3. Availability monitor · Recorded state

    Desconhecido→inactive

    hosting_placeholder · placeholder_page

  4. Availability monitor · Recorded state

    Acessível→Indisponível

  5. Availability monitor · Recorded state

    Acessível→Indisponível

  6. Availability monitor · First collection record

    Acessível

Pipeline de resposta a ameaças

Descoberta
Analysis
Monitoring

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

Ameaça detectada
cloudenginelab.web.app detectados e colocados na fila para análise completa
31/07/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
2/91 recorded on VirusTotal
12/08/2026
Detecção de lista de bloqueio
Encontrado em 2 blocklists: MetaMask, SEAL
16/10/2026
Brand Impersonation
Impersonation of MetaMask
Technical Analysis Recorded
O relatório contém tecnologia armazenada ou resultados de análises forenses.
16/10/2026
Site Came Back Online
Domain is responding again — monitoring resumed
09/10/2026
Content Observed Unavailable
O monitoramento registrou uma resposta indisponível (HTTP 404); a causa não foi estabelecida de forma independente.
11/09/2026
Content Observed Unavailable
O monitoramento registrou uma resposta indisponível (HTTP 404); a causa não foi estabelecida de forma independente.
10/08/2026
Lista de Destruição Publicada
31/07/2026
Monitoring Continues
O domínio permanece acessível ou com acesso restrito; verificações futuras poderão atualizar esta observação.
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.

Related infrastructure

Shared hosting, registrar records and related domains

Domínios semelhantes

79 domínios semelhantes armazenados

Mostrar tudo (67)
metasmask.io insertion Relatório interno metramask.io insertion Relatório interno mewtamask.io insertion Relatório interno mmetamask.io homoglyph Relatório interno mtamask.io omission Relatório interno mwetamask.io insertion Relatório interno nmetamask.io homoglyph Relatório interno metamark.io bitsquatting Relatório interno metamaskj.io addition Relatório interno metammask.io homoglyph Relatório interno metamnask.io homoglyph Relatório 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

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Você foi afetado por este site?

1 evidence signal groups linked 0 stored notification records Último ativo conhecido

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 cloudenginelab.web.app)
  • 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
Read the evidence in context

Sobre este relatório: cloudenginelab.web.app

Este relatório apresenta as últimas evidências armazenadas disponíveis para PhishDestroy. Os carimbos de data/hora de origem são mostrados quando disponíveis; a disponibilidade e os veredictos do fornecedor podem mudar após a coleta.

O site capturado exibia o título da página “Site Not Found” e pode estar se passando por MetaMask.

A partir de 2026-08-12 04:30:07 UTC, cloudenginelab.web.app tinha detecções de mecanismos de segurança 2.

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.

Embed this report

A 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/cloudenginelab.web.app"
  title="PhishDestroy threat report for cloudenginelab.web.app"
  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>