Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
fortwexa.com favicon

fortwexa.com

Registrador
Global Domain Group
Resolved IP
46.29.26.38
Registered
03/09/2026
PhishDestroy assessment Crítico
First observed Oct 5, 2026 01:02 UTC · PhishDestroy
VirusTotal detecciones: 6/92
OTX: 4 refs 05/10/2026 1 Report Sent
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 6. Tenga extrema precaución: no ingrese credenciales o información personal.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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; 15 days 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.

Elapsed since first report
15 days
Reports sent
1
Latest case ID
PD-20261005-8B515E
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Resumen del informe

Phishing: fortwexa.com — No verificado. Resumen de las pruebas: VirusTotal 6/92 (Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue)…

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Source evidenceVirusTotal 6 / 92 · OTX 4 references 6 sources

VirusTotal

6 / 92 engine detections

Abrir informe

Google Safe Browsing

No threat flag

Abrir informe

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Crítico
VirusTotal
6 / 92
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

fortwexa.com is a suspicious domain on the PhishDestroy blocklist. It presents nothing but a page titled "Loading", with no visible brand. PhishDestroy first saw it on 2026-10-05, about a month after registration. As of 2026-10-19 the server still responded, but the site's content was no longer resolving through DNS.

How the scam works

A page that shows only a "Loading" title reveals nothing about itself to a casual visitor or an automated scanner. Pages like this often act as a placeholder or redirect step, and the real content is served later or only to certain visitors. Several security vendors independently treat this domain as malicious, which points to a risk of phishing or fraud. The safest assumption is that any login, payment details or wallet connection requested here could be captured by whoever runs it.

Evidence

On 2026-10-07, 6 of 92 VirusTotal engines flagged the domain: Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue and SOCRadar. That is a modest count. It is meaningful because the flags come from unrelated vendors, including Bfore.Ai PreCrime, which specialises in spotting malicious domains early. The domain also appears in 4 AlienVault OTX threat pulses, so other researchers have tied it to tracked activity. Of the blocklists checked, only PhishDestroy lists it.

Infrastructure

The domain was registered on 2026-09-03 through Global Domain Group LLC and was on our radar by 2026-10-05. That timeline fits a short-lived site set up shortly before use. It is hosted in Turkey on the M/S ROBI TRADERS network. Its certificate from Let's Encrypt is free and automated, so the padlock in the browser says nothing about whether the site is trustworthy.

What to do

If you typed a password on fortwexa.com, change it everywhere you reused it and turn on two-factor authentication. If you entered card or bank details, contact your bank and watch for unfamiliar charges. If you connected a crypto wallet or typed a recovery phrase, move your funds to a new wallet whose phrase has never been exposed. Defenders should block the domain and its hosting address at DNS and proxy level. They should also search logs for visits since 2026-09-03 and report the domain to the registrar and the hosting provider.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 3 captures

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
Reputación de IP abuse score 9/100 2 reports PhishingOpen ProxyPort Scan checked 05/10/2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodominiosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Global Domain Group (Unknown)
RegistroCreado 03/09/2026 (47d · New) — Expires 03/09/2027
Detalles técnicosProvenance & timestamps
Primera detección05/10/2026
DOM Analysisanalyzed 09/10/2026score 88/100
Submitted URLhttps://fortwexa.com/
Favicon Hash
ID del caso
Certificado TLS
Emitido por Let's Encrypt / YR2 · stored validity ends in 42 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
46.29.26.38
Network ASN
AS132359
Organization
FortiCore Digital
Observed location
Istanbul, TR

Servidores de nombres 3

  • a.dnspod.com
  • b.dnspod.com
  • c.dnspod.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-09-03 06:52:40
Valid until
2026-12-02 06:52:39
Validity
Within stored validity dates
Collection time
2026-10-20 16:02:36 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte52e324e4caea022aa063ed0513bc89cd33cb07283f6d8731627540b3a2cb91b

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-20 08:21:37 UTC

Primary outcome DNS inactivo reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Desconocido Probe Inconclusive 20% 2026-10-19 22:39:02 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-09 10:41:08 UTC last content: 2026-10-09 10:41:08 UTC current episode first observed: 2026-10-09 20:20:42 UTC observed RIP window: 2026-10-09 10:41:08 UTC → 2026-10-09 20:20:42 UTC · 9.66h midpoint estimate ≈ 2026-10-09 15:30:55 UTC · precision medium · 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.
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

6 / Los proveedores de seguridad de 92 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
Bfore.Ai PreCrime
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
SOCRadar

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of fortwexa.com · checked Oct 5, 2026

77
Needs Work
Performance
FCP
4.05s
First Contentful Paint
LCP
4.11s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
65ms
Total Blocking Time
SI
4.05s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-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
9.66
Estimate basis
Bounded by observations
Estimate precision
Medio

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history16

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

    Desconocido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

Earlier observations 11
  1. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    live_content→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  8. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  9. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  10. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  11. Availability monitor · First collection record

    Accesible

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/92 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Abuse report sent

    PD-20261005-8B515E

    abuse@forticore.digital
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    fortwexa.com

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

fortwexa.com

Datos y informes externos

Instantánea de evidencia enviada
Sent: Ledger records: 1 Case ID: PD-20261005-8B515E Recipient: abuse@forticore.digital
PDF notice generated
Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

6 evidence signal groups linked 1 stored notification records No verificado
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.

Official reporting routes

¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

¿Qué debo hacer ahora mismo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del 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.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos fortwexa.com)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

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?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/fortwexa.com"
  title="PhishDestroy threat report for fortwexa.com"
  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>