Ir para o relatório de segurança
Domain security report
yaccc.top favicon

yaccc.top

Veredicto de ameaça
Assessment sources

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

Disponibilidade Não verificado A acessibilidade atual não foi verificada Observado · HTTP probe
Detecções do VirusTotal: 11/92 Spamhaus DBL: DBL_PHISH Correspondências da lista de bloqueio armazenada: 1 Automated brand label: WhatsApp
OTX: 4 refs 18/10/2026 WhatsApp 1 Report Sent
API
Registrador
Gname
Resolved IP
43.164.2.217
Registered
09/11/2025
3 sources
In this reportGet help
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 11. Listas de bloqueio públicas relatando uma correspondência: 1. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
Resumo do relatório

yaccc.top — Não verificado. Representação da marca: WhatsApp. Resumo das evidências: VirusTotal 11/92 (alphaMountain.ai, CSIS Security Group, ESET, Emsisoft, Fortinet); URLQuery 2 det.; URLScan capture; Spamhaus DBL_PHISH; 1 external blocklist match (OpenPhish); PhishDestroy score 100/100. Registrador: Gname.

The evidence summary below uses retained observations. Each source keeps its own collection date.

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
11 det.
URLQuery
URLQuery
2 det.
OTX references
URLScan
URLScan
Idade
11 mo
PhishDestroy
DestroyList
Listado
Reports Sent
1

Source evidence

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

11 / 92

Denunciar
Interpretation & limits

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

URLQuery

2 det.

Observation time not recorded
Denunciar
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

Public blocklists

1 external matches

Detalhes
Interpretation & limits

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

Spamhaus DBL

DBL_PHISH

Interpretation & limits

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

OTX

4 community references

Denunciar
Interpretation & limits

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

URLScan capture

relatório armazenado

View stored capture ↗
Denunciar
Interpretation & limits

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

CF Radar

Report stored; verdict not recorded

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
11/92
OTX
4 community refs
URLScan
Stored capture

Evidence-based analysis Generated from the observations retained in this report. No stored AI narrative is available for this record. Each source retains its own collection date.

PhishDestroy first observed yaccc.top on Oct 18, 2026. Stored content metadata identifies WhatsApp as the apparent target. Current evidence score: 100/100 (critical).

Positive findings are stored from 4 sources: VirusTotal, OpenPhish, Spamhaus DBL, and URLQuery. VirusTotal recorded 11 detections among 92 engines: alphaMountain.ai, CSIS Security Group, ESET, Emsisoft, Fortinet, G-Data, LevelBlue, Lionic, Netcraft, Sophos, Webroot on Oct 18, 2026 at 02:41 UTC. OpenPhish listed the hostname in the separate external-blocklist snapshot on Oct 18, 2026 at 02:20 UTC. Spamhaus DBL: DBL_PHISH on Oct 18, 2026 at 02:30 UTC. URLQuery recorded 2 detections; no observation timestamp was retained. Additional recorded evidence: AlienVault OTX listed 4 community pulse references (not vendor detections) on Oct 18, 2026 at 02:09 UTC. URLScan captured the page on Oct 18, 2026 at 01:08 UTC.

The collector marked the hostname reachable on Oct 18, 2026 at 01:08 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 17, 2026 at 23:08 UTC. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and Nov 9, 2025 as the creation date. At collection time, the hostname resolved to 43.164.2.217 (AS132203 Tencent Building, Kejizhongyi Avenue). The recorded endpoint location is Bangkok, TH. DOM analysis on Oct 18, 2026 at 02:20 UTC returned 20/100. The evidence archive retains 3 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance.

The content indicators and 4 positive source findings support the current WhatsApp impersonation and phishing classification. The target field identifies WhatsApp.

Data coverage & collection

19 · datasets with records / 12 · 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
11 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
2 · recorded detections / alertsCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
1 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Gname.com Pte. Ltd.Collection time not recorded
Network & DNS
43.164.2.217 · 4 · nameserversCollection time not recorded
Page captures
3 · retained captures
HTML archives
1 · retained responses
Page analysis
1 · automated brand labels
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
90/100 · mobile performance
Response records
1 · outgoing report records
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 12

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

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Certificado TLS
  • Observed indicators
  • Detection & evasion
  • Recorded subdomains
  • Lookalike relationships
  • Denúncias da comunidade
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

1 · external source matches

Status da lista de bloqueios pública

Domain, network & archive

Gname.com Pte. Ltd. · 43.164.2.217 · DNS, TLS and retained responses

Domain details

Domínio
Reputação do IP abuse score 0/100 0 reports checked 18/10/2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Gname VN(VN)
RegistroCriado 09/11/2025 (342d) — Expires 09/11/2026
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez18/10/2026
DOM Analysisanalyzed 18/10/2026score 20/1001 brand signal
Submitted URLhttps://yaccc.top/
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
43.164.2.217
Network ASN
AS132203
Organization
Tencent Building, Kejizhongyi Avenue
Observed location
Bangkok, TH
Servidores de nomes 4
  • a.share-dns.com
  • a5.share-dns.com
  • b.share-dns.net
  • b5.share-dns.net

Location describes the IP network.

Latest Classified Outcome 2026-10-18 01:08:06 UTC

Primary outcome Desconhecido reason: Probe Inconclusive 20% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Desconhecido Probe Inconclusive 20% 2026-10-18 01:08:06 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-18 01:08:06 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.
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

11 / Os fornecedores de segurança 92 sinalizaram este domínio
View on VT
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
CSIS Security Group
ESET
Emsisoft
Fortinet
G-Data
LevelBlue
Lionic
Netcraft
Sophos
Webroot
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of yaccc.top · checked Oct 18, 2026

90
Good
Performance
FCP
2.4s
First Contentful Paint
LCP
2.48s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.27s
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: https://yaccc.top/
WhatsApp
WhatsApp device linking
Resposta
HTTP 200
HTML body
521 B
Compressed
329 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.24.0 (Ubuntu)
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 328b129896d6aac1c3e59c232254d357e6cf1616e0af116e3346bf6f2249da4a
Saved response-header values · 8
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 18 Oct 2026 01:07:37 GMT
Etag
W/"6accc86c-209"
Last-Modified
Mon, 12 Oct 2026 11:45:48 GMT
Server
nginx/1.24.0 (Ubuntu)
Transfer-Encoding
chunked

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

Reachable (legacy)
/robots.txt
HTTP response
200
Observed at
2026-10-18 01:07:38 UTC
Fonte
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

Sitemap

Reachable (legacy)
/sitemap.xml
HTTP response
200
Observed at
2026-10-18 01:07:38 UTC
Fonte
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

security.txt

Reachable (legacy)
/.well-known/security.txt
HTTP response
200
Observed at
2026-10-18 01:07:38 UTC
Fonte
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

Registration & observation details1

Availability observations

Last reachable observation

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
Roteamento de captura
Local arquivado em 2026-10-18 01:07:38 UTC
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

1 · outbound report records

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-18 01:08:06 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 43.164.2.217.
Stored observation history2

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

    probe_inconclusive

  2. Availability monitor · First collection record

    Acessível

Pipeline de resposta a ameaças

Descoberta
Analysis
Notifications
Monitoring

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

Ameaça detectada
yaccc.top detectados e colocados na fila para análise completa
18/10/2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
18/10/2026
URLScan.io Capture
Armazenado URLScan report with capture artifacts
18/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.
VirusTotal
11/92 recorded on VirusTotal
18/10/2026
Detecção de lista de bloqueio
Encontrado em 1 blocklist: OpenPhish
18/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
18/10/2026
Brand Impersonation
Impersonation of WhatsApp
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
18/10/2026
Technical Analysis Recorded
O relatório contém tecnologia armazenada ou resultados de análises forenses.
18/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar Gname.com Pte. Ltd., 2 abuse contacts
abuse@tencent.comcomplaint@gname.com
18/10/2026
Lista de Destruição Publicada
18/10/2026
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

Evidências e relatórios externos

Instantâneo das evidências enviadas
Sent: Ledger records: 1 Case ID: PD-20261018-D8709E Recipient: abuse@tencent.com
Page title stored with report: WhatsApp
PDF notice generated Notice text archived (317 chars)
Abuse notice text as sent to the provider
Registrar: Gname.com Pte. Ltd. (Singapore)
Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain
Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
Análise aprofundada

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Você foi afetado por este site?

6 evidence signal groups linked 1 stored notification records Não verificado
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 yaccc.top)
  • 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: yaccc.top

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.

A partir de 2026-10-18 02:41:59 UTC, yaccc.top tinha detecções de mecanismos de segurança 11.

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/yaccc.top"
  title="PhishDestroy threat report for yaccc.top"
  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>