polymarket[.]a2zcrypto[.]co[.]in
polymarket.a2zcrypto.co.in — No verificado. Resumen de las pruebas: VirusTotal 3/92 (ChainPatrol, alphaMountain.ai, Seclookup); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 78/100. Registrador: GoDaddy.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
The domain polymarket.a2zcrypto.co.in was registered through GoDaddy on May 08, 2026 and is hosted on a Google Cloud infrastructure. DNS resolution points to the IPv4 address 34.111.179.208, which geolocates to the United States. The authoritative name servers are fattouche.ns.cloudflare.com and margaret.ns.cloudflare.com, indicating the use of Cloudflare’s DNS services. An SSL certificate issued by Let’s Encrypt (certificate identifier E8) is active, and the web server returns HTTP status code 200 for all requests, suggesting a functional front‑end.
Infrastructure analysis shows that the domain’s IP belongs to a cloud provider commonly leveraged for rapid deployment of malicious sites, reducing the cost of takedown. The presence of Cloudflare name servers can obscure the true origin of the hosting server, complicating attribution. The domain’s short lifespan—less than three months—combined with its recent creation aligns with typical patterns of phishing infrastructure that aim to evade early detection.
Reputation data confirms that the site is flagged by multiple security blocklists, including PhishDestroy, MetaMask, and SEAL, and appears on three independent blocklists. VirusTotal scans reported that 5 out of 95 security vendors flagged the domain as malicious, and Gridinsoft assigned a trust score of 0 out of 100, reinforcing the high‑risk classification. The threat is currently active, and the risk level has been designated as high.
Defenders should add polymarket.a2zcrypto.co.in to network‑level deny lists and enforce URL filtering to block user access. Continuous monitoring of the associated IP address and DNS records is recommended, as the infrastructure could be repurposed for additional campaigns. Incident response teams should also consider sinkholing the domain or coordinating with the hosting provider to accelerate takedown, while maintaining awareness of potential re‑hosting on alternative cloud services.
Proceso de respuesta ante amenazas Pipeline
Estado de la lista de bloqueados pública
Inteligencia de dominios
Detalles técnicosDNS, SAN de SSL, marcas de tiempo
Análisis de VirusTotal
Datos y informes externos
¿Te ha afectado esta página web?
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.
Informa a las autoridades locales
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Comprobar cualquier dominio
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraDenunciar un intento de phishing
Envía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarFlujo de amenazas en tiempo real
Informes de phishing recientes y cambios de disponibilidad observados
MonitorizarMantente informado, mantente a salvo
Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.