Seguridad de dominio e inteligencia sobre amenazas
com-a.my
“Suspected Phishing | Cloudflare”
Registrador
Gname
Resolved IP
104.21.11.185
Registered
15/09/2026
Veredicto de amenaza
Crítico88/100
Disponibilidad
Accesible · acceso restringidoRespuesta accesible; El contenido de la página no fue verificado.Observado Source: HTTP probe
Señales de riesgo
VirusTotal detecciones: 2/89Coincidencias de la lista de bloqueo almacenadas: 2URLQuery threat systems: 1 alertSuplantación de marca: CloudflareDominio joven: 29 días de antigüedadÚltimo activo conocido
Motores de seguridad que informan una detección: 2. Listas de bloqueo públicas que informan una coincidencia: 2. 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 complaint@gname.com.
The latest stored availability evidence still shows the domain reachable; 26 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
26 days
Reports sent
1
Latest case ID
PD-20260918-8AE5DA
Current status
HTTP 403 at latest stored check
Resumen del informe
com-a.my — Accesible · acceso restringido (HTTP 403). Suplantación de marca: Cloudflare; Tipo de estafa: Impersonation. Resumen de las pruebas: VirusTotal 2/89 (CRDF, Forcepoint ThreatSeeker); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 88/100. Registrador: Gname.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
Stored evidence for com-a.my: VirusTotal recorded 2 detections among 89 scanners on 2026-09-18. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for com-a.my. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 2 detections among 89 scanners in the stored snapshot dated 2026-09-18. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-18 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for com-a.my in the snapshot dated 2026-09-18. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains com-a.my as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed com-a.my on 2026-09-18. The MetaMask and SEAL blocklist snapshot is dated 2026-09-18 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-15. A URLScan reference was stored on 2026-09-18 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 104.21.11.185 as the observed address in this record. The registration date for com-a.my is recorded as 2026-09-15. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The com-a.my record states that VirusTotal recorded 2 detections among 89 scanners on 2026-09-18. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-18. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 104.21.11.185. The supported conclusion is bounded to the exact stored observations for com-a.my. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to com-a.my during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain com-a.my as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to com-a.my. The stored record does not justify extending that rule to 104.21.11.185 or to other infrastructure records.
Análisis de detección y evasión
Comprobación del enmascaramiento y la distribución del tráfico
Aún no se ha escaneadoAún no se ha registrado ninguna diferencia entre los rastreadores y los navegadores
Observaciones almacenadas de rastreadores frente a navegadores para este servidor, además de una comprobación en tiempo real de la huella digital para sistemas de distribución de tráfico al estilo Keitaro.
Indicador de camuflaje almacenado
Aún no se ha escaneado
Último escaneo de camuflaje
Encabezado del servidor detectado por el escáner
cloudflare
Nota del escáner:cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Respuesta del proveedor durante la exploración: cloudflare_phishing_interstitial
Comprobación de huellas dactilares en directo en TDS
Siete huellas de Keitaro, además de una comparación entre el rastreador y el navegador, que se ejecutan desde el escáner PhishDestroy cuando este panel está abierto.
RegistroCreado 15/09/2026 (29d · Very New!)—Expires 15/09/2027
Estado HTTP403 Forbidden
Elapsed Since First Report1h
Qué contabilizamos
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Accesible · acceso restringido.
Qué contiene cada informe
Los registros de informes salientes almacenados pueden hacer referencia a evidencia disponible en ese momento, como veredictos de proveedores, datos de registro, detalles de alojamiento, clasificaciones o capturas de pantalla. Esta página no infiere la carga útil entregada, el recibo, el acuse de recibo o la acción exacta por parte de un destinatario.
Detalles técnicosProvenance & timestamps
Primera detección18/09/2026
DOM Analysisanalyzed 18/09/2026score 88/1001 brand signal
Submitted URLhttp://com-a.my/
Favicon Hash
ID del caso
Título de la página
Suspected Phishing | Cloudflare
Impersonates
Cloudflare
Certificado TLS
Hostname coverage not recorded·
Emitido por Let's Encrypt / YE2· stored validity ends in 62 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.11.185
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
La reputación de Edge-IP no se atribuye a este dominio.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-18 09:26:36 UTC
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.
Tecnologías · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Cloudflare Browser Insights is a tool that measures the performance of websites from the perspective of users.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of com-a.my· checked Sep 18, 2026
100
Good
Performance
FCP
1.52s
First Contentful Paint
LCP
1.52s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.6s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-18 11:03:50 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-18 09:26:27 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.11.185.
Proceso de respuesta ante amenazas Pipeline
Descubrimiento
Analysis
Notifications
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Amenaza detectada
com-a.my detectados y puestos en cola para su análisis completo
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
El dominio sigue siendo accesible o tiene acceso restringido; controles futuros pueden actualizar esta observación.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
5 evidence signal groups linked1 reports recordedAccesible · acceso restringido
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.
¡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 →
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
Infraestructura e informes relacionados
Las relaciones almacenadas se agrupan por el atributo de coincidencia exacta. Un proveedor o registrador compartido por sí solo no prueba la propiedad común.
Enlace directo Comparte un registro o un kit de phishing idéntico.
Señal de apoyo Comparte infraestructura o una marca de destino; no es prueba de que se trate de un único operador.
Solo para consulta Incluido en la lista de navegación; no comparte ningún atributo con este host.
Mapa de infraestructuras · com-a.my
Cada línea representa un motivo por el que un dominio está vinculado a este servidor. El tamaño de los nodos indica las detecciones de VirusTotal y los nodos con línea discontinua ya están fuera de línea. A continuación se incluyen las listas completas.
El contenido coincide8
El mismo hash del favicon o el mismo título de página que este servidor.
Registrados a través del mismo proveedor de registro. Un proveedor de registro presta servicio a millones de clientes que no tienen relación entre sí, por lo que este dato solo agrupa los registros, en lugar de demostrar que exista un vínculo.
(FR)
