Ir para o relatório de segurança
Domain security report
terbangwdlink.org favicon

terbangwdlink.org

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
Listagem de ameaças PhishDestroy armazenadas Automated brand label: Ankr Domínio jovem: 1 dias atrás
OTX: 4 refs 17/10/2026 Ankr
API
Registrador
Spaceship
Resolved IP
66.29.148.126
Registered
16/10/2026
2 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
⚠️
Suspicious Domain — Listed on PhishDestroy
Listagem de ameaças PhishDestroy armazenadas. VirusTotal analysis stored; no vendor detections were recorded at check time. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
Resumo do relatório

terbangwdlink.org — Não verificado. Representação da marca: Ankr. Resumo das evidências: VirusTotal 0/92; URLScan capture; PhishDestroy score 45/100. Registrador: Spaceship.

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

Additional indicators at a glance

OTX references
URLScan
URLScan
Certificado TLS
Hostname mismatch
Let's Encrypt / YR1 · Certificate hostname mismatch
Idade
1d Brand New!
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

checked — no detections recorded

Denunciar
Interpretation & limits

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

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Denunciar
Interpretation & limits

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

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.

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

Alto
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 terbangwdlink.org on Oct 17, 2026. Stored content metadata identifies Ankr as the apparent target. Current evidence score: 45/100 (high).

On Oct 17, 2026 at 19:49 UTC, VirusTotal recorded 0 detections among 92 engines; AlienVault OTX listed 4 community pulse references (not vendor detections). URLScan captured the page on Oct 17, 2026 at 17:16 UTC.

The collector marked the hostname reachable on Oct 17, 2026 at 17:16 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 17, 2026 at 15:16 UTC. Registration records for the domain list Spaceship, Inc. as the registrar and Oct 16, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 66.29.148.126 (AS22612 Namecheap, Inc.). The recorded endpoint location is Phoenix, US. DOM analysis on Oct 17, 2026 at 18:20 UTC returned 10/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt / YR1 as the certificate issuer with validity through Jan 14, 2027; checked Oct 17, 2026 at 19:02 UTC.

The classification is based on stored page-analysis fields. The target field identifies Ankr.

Data coverage & collection

20 · datasets with records / 11 · 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
0 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
0 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Spaceship, Inc.Collection time not recorded
Network & DNS
66.29.148.126 · 2 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt / YR1
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
1 · automated brand labels
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
46/100 · mobile performance
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 11

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

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

Blocklist records

0 · external source matches

Status da lista de bloqueios pública

Domain, network & archive

Spaceship, Inc. · 66.29.148.126 · DNS, TLS and retained responses

Domain details

Domínio
Reputação do IP abuse score 0/100 0 reports checked 17/10/2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Spaceship US(US)
Contato para abusosabuse@spaceship.com
Registro da ICANNICANN Lookup (RDAP) →
RegistroCriado 16/10/2026 (1d · Brand New!) — Expires 16/10/2027
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez17/10/2026
DOM Analysisanalyzed 17/10/2026score 10/1001 brand signal
Submitted URLhttps://terbangwdlink.org/
Favicon Hash
ID do caso

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
66.29.148.126
Network ASN
AS22612
Organization
Namecheap, Inc.
Observed location
Phoenix, US
Servidores de nomes 2
  • launch1.spaceship.net
  • launch2.spaceship.net

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-10-16 12:47:30
Valid until
2027-01-14 12:47:29
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-17 19:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf49ef3e5079ec7c3949051db9949ea1bf9c1a857c1fc43f0240ffb23b54996cc
Certificate names · 1 SANs
  • www.terbangwdlink.org

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 17:16:02 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-17 17:16:02 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-17 17:16:02 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.terbangwdlink.orgDomain 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 terbangwdlink.org · checked Oct 17, 2026

46
Poor
Performance
FCP
5.19s
First Contentful Paint
LCP
17.55s
Largest Contentful Paint
CLS
0.277
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
6.2s
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://terbangwdlink.org/
TERBANGWD Link Slot Gacor yang Ramai Dibicarakan
TERBANGWD menjadi topik ulasan tentang tren percakapan slot digital, identitas link, pengalaman Android, teknologi HTML5, dan keamanan akses website.
Resposta
HTTP 200
HTML body
146.1 KB
Compressed
21.9 KB
Links
251 internal · 1 external
Detected technologies
wordpress
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: public, max-age=0
Content-Encoding: gzip
Server: LiteSpeed
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 6d2b6d4fd4b4094e63b61bbe30c1cba1041d51409d13646c2b4be7671d7e003f
Open Graph title: TERBANGWD Link Slot Gacor yang Ramai Dibicarakan
Open Graph description: TERBANGWD menjadi topik ulasan tentang tren percakapan slot digital, identitas link, pengalaman Android, teknologi HTML5, dan keamanan akses website.
Twitter card: summary_large_image
Saved response-header values · 10
Cache-Control
public, max-age=0
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sat, 17 Oct 2026 17:16:28 GMT
Expires
Sat, 17 Oct 2026 17:16:28 GMT
Keep-Alive
timeout=5, max=100
Server
LiteSpeed
Transfer-Encoding
chunked
Vary
Accept-Encoding
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

Reachable (legacy)
/robots.txt
HTTP response
200
Observed at
2026-10-17 17:16:30 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-17 17:16:30 UTC
Fonte
legacy scan archive

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

security.txt

Não encontrado
/.well-known/security.txt
HTTP response
404
Observed at
2026-10-17 17:16:30 UTC
Fonte
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

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-17 17:16:30 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

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-17 17:16:02 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 66.29.148.126.
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
Monitoring

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

Ameaça detectada
terbangwdlink.org detectados e colocados na fila para análise completa
17/10/2026
URLScan.io Capture
Armazenado URLScan report with capture artifacts
17/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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
17/10/2026
Brand Impersonation
Impersonation of Ankr
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
17/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
17/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

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 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 terbangwdlink.org)
  • 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: terbangwdlink.org

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.

PhishDestroy lista terbangwdlink.org como suspeito. Foi verificado pelos mecanismos de segurança 92; veredictos automatizados podem mudar. O monitoramento continua. Observado: 2026-10-17 19:49:16 UTC

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