Ir para o relatório de segurança
Domain security report
zap-tech.online favicon

zap-tech.online

“بەخێربێیت بۆ زاپ تێک”

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/92 Automated brand label: Adobe
OTX: 4 refs 16/10/2026 Adobe CDN
API
Registrador
GoDaddy
Resolved IP
172.67.141.34
Registered
11/06/2025
1 sources
In this reportGet help
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 2. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
Resumo do relatório

zap-tech.online — Último ativo conhecido (HTTP 200). Representação da marca: Adobe; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 2/92 (alphaMountain.ai, Webroot); PhishDestroy score 81/100. Registrador: GoDaddy.

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.
OTX references
URLScan
URLScan
Certificado TLS
Within stored validity dates
Let's Encrypt / YE1 · Hostname coverage not recorded
Idade
1.3 yr
Status observado
Último ativo conhecido 200
PhishDestroy
DestroyList
Listado

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

2 / 92

Denunciar
Interpretation & limits

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

OTX

4 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.

URLScan capture

relatório armazenado

Denunciar
Interpretation & limits

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

URLScan verdict

Análise concluída

Denunciar
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

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.

Public blocklists

0 external matches

Detalhes
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/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

zap-tech.online was first observed on 2026-10-16, with a record from OTX documenting 4 pulses on that date. The domain also appears in the PhishDestroy internal listing, providing a catalogue entry relevant to security review.

Recorded Evidence

VirusTotal checked zap-tech.online on 2026-10-16, recording 2 detections out of 92 scanners. The domain was registered with GoDaddy.com, LLC on 2025-06-11. OTX observed zap-tech.online with 4 pulses on 2026-10-16. The PhishDestroy internal listing includes zap-tech.online as of 2026-10-16.

Interpretation

PhishDestroy contains a catalogue entry for zap-tech.online, documenting its inclusion in a publisher-managed listing. VirusTotal records a quantitative assessment of detections from multiple scanners, offering a technical perspective on the domain's profile. OTX provides community-driven intelligence, with its pulse count representing external observations. Together, these sources capture a snapshot of the domain's recorded security context.

Recommended Actions

For zap-tech.online, preserve the VirusTotal, OTX, and PhishDestroy records for ongoing reference. Compare each source's entries and detection counts to monitor future changes or additional findings.

Data coverage & collection

22 · datasets with records / 9 · 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 / 92 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
0 · external matches
Cloudflare Radar
limpoCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
GoDaddy.com, LLCCollection time not recorded
Network & DNS
172.67.141.34 · 2 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt / YE1
Page captures
1 · retained captures
HTML archives
1 · retained responses
Page analysis
2 · 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
79/100 · mobile performance
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
4 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 9

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
  • Lookalike relationships
  • Denúncias da comunidade
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Status da lista de bloqueios pública

Domain, network & archive

GoDaddy.com, LLC · 172.67.141.34 · DNS, TLS and retained responses

Domain details

Domínio
URLScan verdict Análise concluída score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador GoDaddy US(US)
RegistroCriado 11/06/2025 — Expires 11/06/2027
Status HTTP200
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez16/10/2026
DOM Analysisanalyzed 16/10/2026score 81/1002 brand signals
Submitted URLhttp://zap-tech.online/
Favicon Hash
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

Shared CDN edge
Resolved IP
172.67.141.34
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

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

Servidores de nomes 2
  • bingo.ns.cloudflare.com
  • dexter.ns.cloudflare.com
Mail routing 2 MX records
  • mx1.hostinger.compriority 5
  • mx2.hostinger.compriority 10

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-09-15 23:21:39
Valid until
2026-12-14 23:21:38
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 04:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint257eb7b36576164887c099c3999c767605522dfa3658beb4729bad0bdb5a22ea

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-17 10:46:12 UTC

Primary outcome Conteúdo ativo 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 Conteúdo ativo Ordinary HTTP content served 90% 2026-10-17 10:46:12 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-17 10:46:12 UTC last content: 2026-10-17 10:46:12 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.
Recorded subdomains1

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

  • www.zap-tech.onlineDomain record

The original observation time is not recorded for these hostnames.

Tecnologias · 4 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 92 sinalizaram este domínio
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
Webroot

Evidências arquivadas

Wayback Machine Snapshot
Um instantâneo histórico está disponível para revisão de evidências
View Archive
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of zap-tech.online · checked Oct 16, 2026

79
Needs Work
Performance
FCP
2.4s
First Contentful Paint
LCP
4.81s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
38ms
Total Blocking Time
SI
2.83s
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://zap-tech.online/
Final URL: https://zap-tech.online/
بەخێربێیت بۆ زاپ تێک
Resposta
HTTP 200
HTML body
41.7 KB
Compressed
6.6 KB
Links
19 internal · 25 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/8.3.35
Cache-Control: no-store, no-cache, must-revalidate
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Content-Security-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 20
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a4b363e94d26d3a9-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
upgrade-insecure-requests
Content-Type
text/html; charset=UTF-8
Date
Fri, 16 Oct 2026 01:46:31 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
panel
hpanel
platform
hostinger
Pragma
no-cache
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=0ST2cAnibvJjcGKMk1uKFIobmgGq09pm58QqamyjfVok87OuooebZqfCn7AyX5DUFKq5%2FeLDJhEhazTE%2BkHO4OLg3t7osoGihhIq65UGaeHyZXfHt7kIqtKB8fnoHfnU6Aw%3D"}]}
Server
cloudflare
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-powered-by
PHP/8.3.35
x-turbo-charged-by
LiteSpeed

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

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-16 01:46:31 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-16 01:46:31 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-16 01:46:31 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

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
cloudflare
Roteamento de captura
Local arquivado em 2026-10-16 01:46:31 UTC

Nota do digitalizador: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

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.
Sob demanda

Nenhum resultado desta verificação foi salvo.

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-16 01:45:27 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.141.34.
Stored observation history5

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

    Desconhecido→live_content

    content_served

  2. Availability monitor · Recorded state

    live_content→Desconhecido

    probe_inconclusive

  3. Availability monitor · Recorded state

    Desconhecido→live_content

    content_served

  4. Availability monitor · Recorded state

    Desconhecido

    probe_inconclusive

  5. 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
zap-tech.online detectados e colocados na fila para análise completa
16/10/2026
URLScan.io Capture
Armazenado URLScan report with capture artifacts
16/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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
16/10/2026
VirusTotal
2/92 recorded on VirusTotal
16/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
16/10/2026
Brand Impersonation
Impersonation of Adobe
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
16/10/2026
Technical Analysis Recorded
O relatório contém tecnologia armazenada ou resultados de análises forenses.
17/10/2026
Lista de Destruição Publicada
16/10/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

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?

4 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 zap-tech.online)
  • 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: zap-tech.online

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 “بەخێربێیت بۆ زاپ تێک” e pode estar se passando por Adobe.

A partir de 2026-10-16 02:58:17 UTC, zap-tech.online 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/zap-tech.online"
  title="PhishDestroy threat report for zap-tech.online"
  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>