VirusTotal
2 / 91
“Selfhosted.social”
flare.selfhosted.social — Último ativo conhecido (HTTP 200). Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 2/91 (alphaMountain.ai, Gridinsoft); PhishDestroy score 71/100. Registrador: Cloudflare.
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
Analysis of flare.selfhosted.social indicates a high‑risk generic phishing operation that remains active as of July 12, 2026. The domain was registered on February 21, 2026 through Cloudflare, Inc., and uses the Cloudflare nameservers drew.ns.cloudflare.com and katja.ns.cloudflare.com. DNS resolution points to IP address 172.67.141.27, which is hosted in the United States under ASN 13335 (Cloudflare). The site presents a valid SSL certificate issued by Google Trust Services / WE1 and returns HTTP status 200, employing Cloudflare Browser Insights and HTTP/3. Threat intelligence shows the domain is blocked by PhishDestroy, appears on one public security blocklist, and has a Gridinsoft trust score of 0 out of 100. VirusTotal scans report four of ninety‑three security vendors flagging the domain, reinforcing the phishing classification. The page title "Selfhosted.social" provides no additional context about the targeted brand or content. Given the observed infrastructure, low trust score, and vendor detections, defenders should treat flare.selfhosted.social as malicious, enforce network‑level blocking, add the domain to local blocklists, and monitor for any related activity. Further investigation of the hosted page content is required to determine the specific credential‑capture mechanisms employed.
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.
Nota do digitalizador: alive_content: raw=ok; http=200; via=https_proxy
For the registrable domain selfhosted.social behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
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.
A reputação do Edge-IP não é atribuída a este domínio.
katja.ns.cloudflare.comLocation describes the IP network.
15d0cd721b73f0cdd798d2b5c35646909fbd0e5b7079a8c99416af33872adc1bselfhosted.socialSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of flare.selfhosted.social · checked Jun 27, 2026
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Denunciado por 1 membro da comunidade; visto pela primeira vez em 11/02/2026
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.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
Template-based draft · optional AI wording assistance requires separate consent
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo