The domain axondao.network is associated with generic phishing activities designed to steal credentials. It does not impersonate any specific brand and does not appear to use a known drainer kit. The site is currently taken offline, indicating it is no longer active or accessible. Users searching whether axondao.network is safe or a scam should consider it unsafe due to its phishing nature and elevated risk level.
Technical analysis shows that axondao.network is flagged by 1 of 95 VirusTotal security vendors, including Gridinsoft, which assigns it a trust score of 0 out of 100. The domain is registered through OwnRegistrar, Inc., though the creation date is not available. It resolves to IP address 104.21.0.152 located in the United States under AS13335 Cloudflare, Inc. The domain appears on one security blocklist, PhishDestroy, and uses an SSL certificate issued by Google Trust Services / WE1. The site employed Cloudflare and HTTP/3 technologies and had page content titled 'Just a moment...'. Nameservers include amber.ns.cloudflare.com and peter.ns.cloudflare.com.
To mitigate potential harm from axondao.network phishing attempts, users who may have entered credentials should immediately change their passwords on affected accounts and enable two-factor authentication where possible. Vigilance for fraudulent activity is recommended. Users can report phishing scams like axondao.network to security blocklists such as PhishDestroy and to relevant authorities to help prevent further victimization.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inativoreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationDesconhecidoProbe Inconclusive20%2026-10-20 10:14:02 UTC
RDAP registrationDesconhecido
Observed timelinelast reachable: 2026-10-03 10:35:47 UTClast content: 2026-10-03 10:35:47 UTCcurrent episode first observed: 2026-10-05 22:13:39 UTCobserved RIP window: 2026-10-03 10:35:47 UTC → 2026-10-05 22:13:39 UTC · 59.63hmidpoint estimate ≈ 2026-10-04 16:24:43 UTC · precision low · basis bounded
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 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
Google PageSpeed Insights — mobile performance audit of axondao.network· checked Apr 16, 2026
78
Needs Work
Performance
FCP
0.77s
First Contentful Paint
LCP
2.3s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
891ms
Total Blocking Time
SI
1.4s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details9
Availability observations
Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
59.63
Estimate basis
Bounded by observations
Estimate precision
Low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='axondao.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
axondao.network
Resultado salvo
Inacessível
Stored observation history22
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Os relacionamentos armazenados são agrupados pelo atributo de correspondência exata. Um provedor ou registrador compartilhado por si só não prova propriedade comum.
Mapa da infraestrutura · axondao.network
Cada faixa representa um motivo pelo qual um domínio está vinculado a este host. O tamanho dos nós indica as detecções do VirusTotal, e os nós tracejados já estão offline. As listas completas seguem abaixo.
O conteúdo corresponde4
O mesmo hash do favicon ou o mesmo título da página que este host.
Registrados pelo mesmo registrador. Um registrador atende a milhões de clientes sem qualquer relação entre si; portanto, isso apenas agrupa os registros, em vez de comprovar uma ligação.
5 evidence signal groups linked0 stored notification recordsNã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.
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 →
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 axondao.network)
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
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
