VirusTotal
13 / 91
DenunciarInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Главная - М&Ю Жалюзи Тольятти”
Assessment based on the stored source evidence below. Review sources →
zalyzi63.ru — Último ativo conhecido (HTTP 200). Representação da marca: Google; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 13/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker); PhishDestroy score 99/100. Registrador: AXELNAME-RU.
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
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.
13 / 91
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 community references
DenunciarCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
relatório armazenado
View stored capture ↗ DenunciarA preserved page image documents what the collector received; a capture is not a safety verdict.
Análise concluída
DenunciarThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
DenunciarA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetalhesA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, zalyzi63.ru returned an HTTP 200 status, a recorded response on that date. The domain was first observed on 2026-09-20, and its registration date is recorded as 2026-07-31.
VirusTotal checked zalyzi63.ru on 2026-09-30 and recorded 13 detections across 91 scanners. OTX recorded four pulses for the domain on 2026-09-22. The PhishDestroy internal catalogue listed the domain, and a PageSpeed check on 2026-09-20 returned a performance score of 88. The SSL certificate, issued by Google Trust Services / WE1, was scanned on 2026-09-20.
The named sources observe zalyzi63.ru on different dates, so their records describe separate moments rather than one continuous picture. VirusTotal, OTX, and the PhishDestroy catalogue each contribute a distinct dated observation, while the HTTP and PageSpeed checks fall on other days. Because the checks are not synchronized, a reader can compare what each source recorded without treating any single record as current.
Retain the dated records for zalyzi63.ru so later checks can be compared against the same source values. When new observations arrive, compare them with the earlier VirusTotal, OTX, and PhishDestroy entries rather than relying on one snapshot. During review, avoid submitting sensitive information to zalyzi63.ru until the evidence has been assessed.
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.
These checks have no retained result. This does not mean they passed or that a scan is running.
A reputação do Edge-IP não é atribuída a este domínio.
celeste.ns.cloudflare.comfelipe.ns.cloudflare.comLocation describes the IP network.
dc717a5bb5511c161d890253e7aa087ac512532080bcdc1c1e79001f86661b79Saved 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 zalyzi63.ru · checked Sep 20, 2026
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.
cloudflareNota do digitalizador: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
172.67.171.63.10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
Template-based draft · optional AI wording assistance requires separate consent
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo