VirusTotal
16 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“BANKOMAT.CC bankomat.su bankomat shop , original domain”
Assessment based on the stored source evidence below. Review sources →
This domain www.http-bankomat.cc is currently active and classified as a high‑risk banking phishing site.
The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.
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.
16 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
2/14
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no match recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | www.http-bankomat.cc |
malicious | Sinkholed |
| Cloudflare DNS | www.http-bankomat.cc |
malicious | Sinkholed |
| OpenDNS | www.http-bankomat.cc |
phishing | Phishing Block |
| DigiCert UltraDNS | www.http-bankomat.cc |
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.
This domain www.http-bankomat.cc is currently active and classified as a high‑risk banking phishing site. The authoritative nameservers ns3.owlhost.net and ns4.owlhost.net resolve the domain to the IPv4 address 185.43.220.18, which is hosted in the Netherlands and attributed to the WIBO Group. HTTP requests receive a 301 redirect, and the site presents a TLS certificate issued by Let’s Encrypt (E7). The page title returned by the server is “BANKOMAT.CC bankomat.su bankomat shop , original domain”, indicating the use of multiple brand‑related terms. Technical fingerprints show PHP running on an Apache HTTP Server with Yandex.Metrika and Google Analytics scripts embedded. VirusTotal scans have flagged the domain in 17 of 91 security engines, and Gridinsoft assigns a trust score of 0/100. The domain appears on a single public blocklist and is listed as blocked by PhishDestroy. Registration data show the domain was created on 13 April 2022 through the registrar Gransy, s.r.o. No further public intelligence about the exact payload or credential collection page is available. Defenders should block resolution of 185.43.220.18 at the network perimeter, add www.http-bankomat.cc to URL filtering and email security policies, and monitor associated hostnames ns3.owlhost.net and ns4.owlhost.net for any additional malicious activity. Continuous re‑evaluation is advised in case the infrastructure changes.
20 · datasets with records / 11 · 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. · 185.43.220.18 · DNS, TLS and retained responses
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.
ns3.owlhost.netns4.owlhost.netLocation describes the IP network.
35ea2032ad7e5e8a174d12be87759c473e7565ba76b07d83616a1f13bff6fc4fhttp-bankomat.ccSaved 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 duplicate-disabled-178217.invalid · checked Mar 24, 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
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-178217.invalid', port=80): Max retries exceeded with url: / (Caused by
No live-check result has been retained.
Collection history, report status and investigation channels
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown
stale_current_evidence
Reachable→Unavailable
12 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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
duplicate-disabled-178217.invalid)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “BANKOMAT.CC bankomat.su bankomat shop , original domain”.
VirusTotal detections for duplicate-disabled-178217.invalid: 16 (2026-09-11 02:38:56 UTC).
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.
submit an appeal or review the FAQ page.