VirusTotal
2 / 91 engine detections
रिपोर्ट खोलें“Claim Refund”
ब्लॉकलिस्ट में डोमेन: coinpayments.network — अंतिम ज्ञात सक्रिय (HTTP 200). साक्ष्य सारांश: VirusTotal 2/91 (Chong Lua Dao, Gridinsoft); 1 external blocklist…
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
2 / 91 engine detections
रिपोर्ट खोलें3/14
55/100
रिपोर्ट खोलें23 community references
रिपोर्ट खोलेंprovider verdict: clean
रिपोर्ट खोलेंNo threat flag
रिपोर्ट खोलेंNo malicious flag
रिपोर्ट खोलेंResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain is flagged as a high‑risk generic phishing site with a crypto‑refund lure. The zone was registered on 21 Feb 2026 through Name.com, Inc. and is hosted on Amazon’s AS16509 network in Germany, resolving to 35.157.26.135. The web server presents a valid Let's Encrypt certificate (E8) and advertises Netlify and HTTP Strict Transport Security. The site appears on two public blocklists and is currently blocked by PhishDestroy and ScamSniffer; Gridinsoft assigns a trust score of 0/100. VirusTotal reports that 2 of 93 scanners have identified malicious activity. The page title “Claim Refund” aligns with the reported crypto‑scam classification. Nameservers are provided by NSOne (dns1‑dns4.p08.nsone.net). HTTP response code is 200, indicating the page is reachable. At present, no additional payload or credential‑collection details have been observed, and the exact phishing kit remains unknown. Defenders should immediately block the domain and its associated IP address, update intrusion‑detection signatures to flag Netlify‑hosted sites with HSTS that reference “coinpayments.network”, and monitor outbound traffic for connections to the AS16509 range. Continuous re‑scanning is advised to capture any future changes to the site’s content or hosting infrastructure.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
एज-आईपी प्रतिष्ठा इस डोमेन के लिए जिम्मेदार नहीं है।
dns1.p08.nsone.netLocation describes the IP network.
c8fd8dd39ca7bc1d94207c88ddebfb186de246df70b68b03297baa543796e8b7Saved 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 coinpayments.network · checked Jun 26, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=Netlify
coinpayments.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
अज्ञात→live_content
content_served
2→2
2→3
2/91 engine detections
View source23 community references
View sourceNo threat flag
View sourcecoinpayments.network
View sourcePage captured
View source1 समुदाय सदस्य ने रिपोर्ट किया; पहली बार 21/02/2026 को देखा गया
Listed domains receive at least one abuse report; this entry has no retained notification history.
यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।
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 ↗
coinpayments.network)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
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
संग्रहीत ब्लॉकलिस्ट, WHOIS, DNS और सार्वजनिक स्कैन साक्ष्य का उपयोग करके खतरे का विश्लेषण
अभी स्कैन करेंसंदिग्ध डोमेन हमारे थ्रेट डेटाबेस में जमा करें — समुदाय की सुरक्षा करें
रिपोर्ट करेंहाल की फ़िशिंग रिपोर्टें और उपलब्धता में परिवर्तन देखे गए
निगरानी करेंलाइव खतरों की निगरानी करें या यदि आपको लगता है कि यह एक गलत सकारात्मक है तो इस लिस्टिंग को चुनौती दें।
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.