polymarket[.]a2zcrypto[.]co[.]in
polymarket.a2zcrypto.co.in — Belum terverifikasi. Ringkasan bukti: VirusTotal 3/92 (ChainPatrol, alphaMountain.ai, Seclookup); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 78/100. Registrar: GoDaddy.
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
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.
Alur Tanggapan Ancaman Pipeline
Status Daftar Blokir Publik
Intelijen Domain
Rincian teknisDNS, SAN SSL, cap waktu
Analisis VirusTotal
Bukti & Laporan Eksternal
Apakah Anda Terpengaruh oleh Situs Ini?
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Periksa Domain Apa Pun
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan Phishing
Laporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanPemberitahuan Ancaman Real-Time
Laporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauTetap Terinformasi, Tetap Aman
Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive