VirusTotal
6 / 89 engine detections
Abrir relatório
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Phishing: fortguard.cc — Não verificado. Resumo das evidências: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, LevelBlue)…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
6 / 89 engine detections
Abrir relatórioDBL_SPAM
checked — no detections recorded
Abrir relatório4 community references
Abrir relatórioprovider verdict: clean
Abrir relatórioNo threat flag
Abrir relatórioNo malicious flag
Abrir relatórioResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
fortguard.cc is a phishing site that impersonates a legitimate service to win visitors' trust and harvest what they type into it. Its likely targets are crypto users who reach it through links in messages, ads or social posts. PhishDestroy first flagged it on 2026-09-16. On 2026-10-19 the domain still responded, but its DNS no longer pointed to live phishing content. A domain in this state can be reactivated at any time.
Impersonation pages copy the look and wording of a service the victim already uses. They then ask for a login, a one-time code or a wallet recovery phrase. Anything entered goes straight to the operators, who can take over the account or empty the wallet within minutes. The page shows only the generic title "Loading", which does not name the brand being copied. We classified the site by its behaviour as an impersonation phishing page.
On 2026-09-24, VirusTotal showed 6 of 89 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, LevelBlue and SOCRadar. That is a modest count, so many browsers and filters may not warn visitors. Spamhaus lists the domain in its DBL as a spam source, which points to distribution through unsolicited messages. It also appears in 4 AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-08-05 through HOSTINGER operations, UAB, about six weeks before we detected it. That gap fits a domain set up in advance and then put into use for a campaign. It is hosted at 46.29.26.38 on the M/S ROBI TRADERS network in Turkey. The free Let's Encrypt certificate gives the site a browser padlock, which proves nothing about who runs it.
If you entered a password or one-time code on this site, change that password right away, along with any account that reuses it. Then reset two-factor authentication and sign out all active sessions. If you typed a seed phrase or private key, treat that wallet as compromised and move your funds to a newly created wallet. Defenders should block the domain and its IP, and search mail and proxy logs for messages or visits linked to it. Its Spamhaus listing suggests it arrived by spam.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
46a76e824bb2d83509f056d4b47f87705c96921da78d9ab0818b9ef7f5454d03Saved 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 fortguard.cc · checked Sep 16, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
fortguard.cc
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
4→5
3→4
2→3
0→2
Acessível
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePD-20260916-6CD304
fortguard.cc
View sourcePage captured
View sourcePD-20260916-6CD304 Recipient: abuse@forticore.digital 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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
fortguard.cc)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 report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
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.