This domain, arecs.online, is flagged as a phishing site impersonating the Arecs Research Institute, a fabricated entity likely designed to lend credibility to fraudulent activities. Analysis indicates the threat type is brand impersonation, targeting victims through a deceptive institutional facade rather than direct credential harvesting or cryptocurrency drainer tactics. The site employed a WordPress-based infrastructure, leveraging technologies such as MySQL, PHP, LiteSpeed, and jQuery to mimic legitimate research portals, though no specific phishing kit or payload was identified in initial scans.
Technical indicators confirm elevated risk levels: the domain resolves to IP address 82.29.189.219 and was registered on June 16, 2025, through HOSTINGER operations, UAB. VirusTotal detects the domain as malicious by 4 out of 95 security vendors, while Gridinsoft assigns a trust score of 0/100. Scamadviser rates it at 49/100, and the domain appears on one security blocklist. The SSL certificate is issued by Let’s Encrypt, a common choice for both legitimate and malicious sites due to its accessibility. Google Safe Browsing (GSB) status is not explicitly listed, but the domain’s inclusion in PhishDestroy’s blocklist further corroborates its fraudulent nature.
As of the latest assessment, arecs.online has been taken offline, likely in response to detection by security vendors and blocklist providers. However, residual risk persists due to the domain’s recent registration and the potential for infrastructure reuse. Organizations and individuals are advised to monitor for re-emergence under similar naming conventions or shared hosting infrastructure. Network defenders should update blocklists to include the domain and its associated IP, while users should verify the legitimacy of any unsolicited communications referencing research institutes or academic entities. No direct financial or credential theft was confirmed, but the impersonation tactic suggests potential for follow-on social engineering attacks.
O que contabilizamos
Tempo decorrido desde a primeira denúncia de abuso armazenada até a primeira observação de que o conteúdo estava indisponível. Isto não estabelece a causa.
O que cada relatório contém
Os registros de relatórios de saída armazenados podem fazer referência a evidências disponíveis no momento, como veredictos de fornecedores, dados de registro, detalhes de hospedagem, classificações ou capturas de tela. Esta página não infere a carga exata entregue, recebimento, confirmação ou ação de um destinatário.
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez17/09/2025
DOM Analysisanalyzed 11/03/2026score 56/100
Submitted URLhttp://arecs.online/
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
82.29.189.219
Network ASN
AS47583
Organization
Hostinger International Limited
Observed location
Manchester, GB
Servidores de nomes 2
ns1.dns-parking.com
ns2.dns-parking.com
Location describes the IP network.
Certificado TLS
Issuer
Let's Encrypt
Valid from
2026-02-27 09:07:16
Valid until
2026-05-28 09:07:15
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-15 05:42:36 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta0a787a008945b4dd3065dc51f4905422a92d57794000e4d02d2b5dd167ef61bCertificate names · 1 SANs
www.arecs.online
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-19 01:10:53 UTC
RDAP registrationDesconhecido
Observed timelinelast reachable: 2026-07-30 22:19:52 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-30 22:19:52 UTC → 2026-09-30 16:14:55 UTC · 1,481.92hmidpoint estimate ≈ 2026-08-30 19:17:23 UTC · precision very 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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.arecs.onlineDomain record
The original observation time is not recorded for these hostnames.
Tecnologias · 12 identified
W
WordPress
CMS
Open-source CMS powering over 40% of websites worldwide.
Google PageSpeed Insights — mobile performance audit of arecs.online· checked Jun 27, 2026
70
Needs Work
Performance
FCP
2.72s
First Contentful Paint
LCP
24.62s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
98ms
Total Blocking Time
SI
2.72s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
1481.92
Estimate basis
Bounded by observations
Estimate precision
very_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='arecs.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
arecs.online
Resultado salvo
Inacessível
Stored observation history12
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 · arecs.online
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.
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 recordsConteúdo indisponível
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 arecs.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
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.
(LT)
