VirusTotal
7 / 91
रिपोर्ट करेंEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“OBC bank”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@regtons.com.
The latest stored availability evidence still shows the domain reachable; 29 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.
obcfinance.com — अंतिम ज्ञात सक्रिय (HTTP 200). ब्रांड प्रतिरूपण: Binance; घोटाले का प्रकार: Impersonation. साक्ष्य सारांश: VirusTotal 7/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); URLQuery 1 alert; Spamhaus DBL_PHISH; PhishDestroy score 90/100. रजिस्ट्रार: Gransy, s.r.o.
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत 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.
7 / 91
रिपोर्ट करेंEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
1 threat-system alert
रिपोर्ट करेंAlerts refer to the preserved scan. They do not describe the current state of the site.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
रिपोर्ट करेंCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
संग्रहित रिपोर्ट
View stored capture ↗ रिपोर्ट करेंA preserved page image documents what the collector received; a capture is not a safety verdict.
विश्लेषण पूरा हुआ
रिपोर्ट करेंThis is the recorded automated analysis. Completion alone is not a safety verdict.
80/100
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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | obcfinance.com |
malicious | Sinkholed |
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.
obcfinance.com returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-17, and its registration date is listed as 2026-07-18.
The HTTP check dated 2026-10-01 recorded status 200 for obcfinance.com. A PageSpeed observation on 2026-09-17 recorded a performance score of 81. OTX was checked on 2026-09-19 and showed 4 pulses. VirusTotal, checked on 2026-09-29, recorded 7 detections across 91 scanners. The publisher-owned PhishDestroy catalogue listed obcfinance.com internally, and the registrar is recorded as Gransy, s.r.o.
The HTTP, PageSpeed, OTX, VirusTotal and PhishDestroy records were captured on different dates, so they describe separate moments rather than one synchronized snapshot. Because the observation dates differ, a reader can compare what each named source recorded at its own check time without treating any single record as current. The PhishDestroy listing and the VirusTotal detections come from distinct collection contexts, and their dates should be read alongside the other records rather than in isolation.
Retain the dated records for obcfinance.com, including the HTTP, PageSpeed, OTX, VirusTotal and PhishDestroy observations, so later checks can be compared against them. When reviewing obcfinance.com, compare each new observation with the earlier dated values and note where the dates differ. Avoid submitting sensitive information while the review is in progress.
23 · datasets with records / 8 · 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
Gransy, s.r.o. · 198.251.84.200 · DNS, TLS and retained responses
ns5.asurahosting.comns5.my-control-panel.comns6.asurahosting.comns6.my-control-panel.comobcfinance.compriority 0Location describes the IP network.
80ea9b6a70556b6029e74cd7b9aa8eee2c2eff02aac6637ba73241bd18e185bcSaved 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 obcfinance.com · checked Sep 17, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
इस होस्ट के लिए संग्रहीत क्रॉलर-बनाम-ब्राउज़र अवलोकन, साथ ही केइतारो-शैली ट्रैफ़िक वितरण प्रणालियों के लिए लाइव फिंगरप्रिंट जांच।
LiteSpeedस्कैनर नोट: alive_content: raw=ok; http=200; via=https_direct; server=LiteSpeed
1 · outbound report records
198.251.84.200.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→अज्ञात
probe_inconclusive
अज्ञात→live_content
content_served
live_content→अज्ञात
probe_inconclusive
अज्ञात→live_content
content_served
live_content→अज्ञात
probe_inconclusive
अज्ञात→live_content
content_served
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
protected→अज्ञात
stale_current_evidence
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
protected→अज्ञात
probe_inconclusive
अज्ञात→protected
captcha · challenge
अज्ञात
probe_inconclusive
6→7
6→Observation retained
5→6
4→5
पहुँच योग्य
16 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
187 संग्रहीत मिलते-जुलते डोमेन
187 में से 100 दिखाए जा रहे हैं
Original reports, independent checks and evidence links
PD-20260917-C6DB53 Recipient: abuse@regtons.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Recovery steps, reporting contacts and complaint drafts
यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।
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 ↗
obcfinance.com)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
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 के लिए उपलब्ध नवीनतम संग्रहीत साक्ष्य प्रस्तुत करती है। स्रोत टाइमस्टैम्प जहां उपलब्ध हों वहां दिखाए जाते हैं; संग्रहण के बाद उपलब्धता और विक्रेता के फैसले बदल सकते हैं।
कैप्चर की गई साइट ने पृष्ठ शीर्षक “OBC bank” प्रदर्शित किया और संभवतः Binance का प्रतिरूपण कर रही है।
2026-09-29 02:19:24 UTC के अनुसार, obcfinance.com को 7 सुरक्षा इंजनों से पता चला था।
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.
यदि आपको लगता है कि यह सूची ग़लत है, तो एक अपील प्रस्तुत करें। हमारी कार्यप्रणाली के बारे में जानने के लिए, अक्सर पूछे जाने वाले प्रश्न पृष्ठ पर जाएँ।