VirusTotal
10 / 92
रिपोर्ट करेंEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
bilzone.shop — असत्यापित. साक्ष्य सारांश: VirusTotal 10/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET); URLScan capture; PhishDestroy score 80/100.
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
10 / 92
रिपोर्ट करेंEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 community references
रिपोर्ट करेंCommunity publication references, not a vendor verdict or evidence of a common operator.
संग्रहित रिपोर्ट
A preserved page image documents what the collector received; a capture is not a safety verdict.
Report stored; verdict not recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
रिपोर्ट करेंA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
विवरणA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
bilzone.shop was observed with multiple source entries, including a PhishDestroy internal listing on 2026-10-16. The domain also had a VirusTotal scan with recorded detections, providing further technical context for its profile.
On 2026-10-16, bilzone.shop was listed in the PhishDestroy internal catalogue. VirusTotal checked the domain on 2026-10-11, recording 10 detections out of 92 total scanners. OTX recorded two pulses referencing the domain, with the most recent check on 2026-10-16. The domain's first observation in records also occurred on 2026-10-16.
PhishDestroy documents bilzone.shop in its internal listing, which is a record of domains reviewed by that source. VirusTotal provides a technical scan result, measuring how many security engines detected the domain during its check. OTX records pulses, which are references or reports contributed by its community, adding additional context to the domain's security profile. These sources together offer a snapshot of the domain's recorded presence across several intelligence platforms.
For bilzone.shop, preserve the PhishDestroy internal listing and VirusTotal scan records for future reference. Compare these with the OTX pulse entries to track any changes in external reporting. Review all dated evidence before making any further technical or security assessments involving this domain.
13 · datasets with records / 18 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
212.52.28.18 · DNS, TLS and retained responses
Location describes the IP network.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bilzone.shop/https://bilzone.shop/Content-Encoding: gzipContent-Type: text/plain;charset=UTF-8h3=":443"; ma=2592000gziptext/plain;charset=UTF-8Fri, 16 Oct 2026 17:35:21 GMTstrict-origin-when-cross-originchunkedAccept-Encoding1.1 CaddynosniffSAMEORIGIN1; mode=blockValues retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
Stored browser and crawler observations
इस होस्ट के लिए संग्रहीत क्रॉलर-बनाम-ब्राउज़र अवलोकन, साथ ही केइतारो-शैली ट्रैफ़िक वितरण प्रणालियों के लिए लाइव फिंगरप्रिंट जांच।
Local संग्रहीत 2026-10-16 17:35:21 यूटीसीलाइव जाँच का कोई परिणाम सहेजा नहीं गया है।
Collection history, report status and investigation channels
212.52.28.18.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
अज्ञात
stale_current_evidence
अज्ञात
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
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 ↗
bilzone.shop)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
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 और सार्वजनिक स्कैन साक्ष्य का उपयोग करके खतरे का विश्लेषण
अभी स्कैन करेंसंदिग्ध डोमेन हमारे थ्रेट डेटाबेस में जमा करें — समुदाय की सुरक्षा करें
रिपोर्ट करेंहाल की फ़िशिंग रिपोर्टें और उपलब्धता में परिवर्तन देखे गए
निगरानी करेंलाइव खतरों की निगरानी करें या यदि आपको लगता है कि यह एक गलत सकारात्मक है तो इस लिस्टिंग को चुनौती दें।
यह रिपोर्ट PhishDestroy के लिए उपलब्ध नवीनतम संग्रहीत साक्ष्य प्रस्तुत करती है। स्रोत टाइमस्टैम्प जहां उपलब्ध हों वहां दिखाए जाते हैं; संग्रहण के बाद उपलब्धता और विक्रेता के फैसले बदल सकते हैं।
2026-10-16 18:07:07 UTC के अनुसार, bilzone.shop को 10 सुरक्षा इंजनों से पता चला था।
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
यदि आपको लगता है कि यह सूची ग़लत है, तो एक अपील प्रस्तुत करें। हमारी कार्यप्रणाली के बारे में जानने के लिए, अक्सर पूछे जाने वाले प्रश्न पृष्ठ पर जाएँ।