Skip to security report
Domain security report
duplicate-disabled-178217.invalid favicon

duplicate-disabled-178217.invalid

“BANKOMAT.CC bankomat.su bankomat shop , original domain”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 16/89 URLQuery threat systems: 4 alerts Scam type: Banking Phishing
Mar 24, 2026
API
Registrar
Gransy, s.r.o
Resolved IP
185.43.220.18
Registered
Apr 13, 2022
3 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
Report overview

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.

Additional indicators at a glance

VirusTotal
VirusTotal
16 det.
URLQuery
URLQuery
4 threat alerts
DNS Security
2/14
CF Radar
Malicious
URLScan
URLScan
TLS Certificate
Hostname mismatch
Let's Encrypt · Certificate hostname mismatch
Age
4.5 yr
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed

Source evidence

10 · sources

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.

VirusTotal

16 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

4 threat-system alerts

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

DNS blocks

2/14

Observation time not recorded
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

PhishStats

checked — no match recorded

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Observation time not recorded
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
DNS Provider Blocks 2 / 14
Cloudflare Family Cloudflare Security
Threat Detection Systems 4 alerts
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
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Evidence Summary

Critical
VirusTotal
16/89
URLScan
Stored capture

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.

Data coverage & collection

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.

Recorded dataPartial recordUTC
VirusTotal
16 / 89 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
4 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
PhishStats
Dated lookup retained
Cloudflare Radar
maliciousCollection time not recorded
DNS security filters
2 / 14 · provider blocksCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Gransy, s.r.o.Collection time not recorded
Network & DNS
185.43.220.18 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
3 · retained captures
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
75/100 · mobile performance
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Page analysis
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Forensic Intelligence

Form submission targets 1
send.php

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Gransy, s.r.o. · 185.43.220.18 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 12, 2026
RegistrationCreated Apr 13, 2022
Time to First Unavailability 30 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedMar 24, 2026
Submitted URLhttps://www.http-bankomat.cc/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
185.43.220.18
Network ASN
AS59939
Organization
WIBO Group
Observed location
Amsterdam, NL
Server header
Apache/2
Nameservers 2
  • ns3.owlhost.net
  • ns4.owlhost.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-02-25 23:39:00
Valid until
2026-05-26 23:38:59
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-25 08:36:23 UTC
Collection source
PhishDestroy collector
Certificate fingerprint35ea2032ad7e5e8a174d12be87759c473e7565ba76b07d83616a1f13bff6fc4f
Certificate names · 1 SANs
  • http-bankomat.cc

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-15 01:16:21 UTC

Primary outcome Unknown reason: Stale Current Evidence 0% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-15 01:16:21 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-23 02:12:19 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
Y
Yandex.Metrika
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 89 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of duplicate-disabled-178217.invalid · checked Mar 24, 2026

75
Needs Work
Performance
FCP
0.91s
First Contentful Paint
LCP
6.06s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
177ms
Total Blocking Time
SI
2.56s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not observed No cloaking was observed in the stored scan

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan

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

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-09-25 01:31:10 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown

    stale_current_evidence

  2. Availability monitor · Recorded state

    Reachable→Unavailable

Threat Response Pipeline

Discovery
Analysis
Monitoring

12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
duplicate-disabled-178217.invalid detected and queued for full analysis
Mar 24, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
16/89 recorded on VirusTotal
Sep 11, 2026
DNS Security Blocks
Blocked by 2 of 14 checked DNS providers: Cloudflare family, Cloudflare security
CF Radar: Malicious
Cloudflare Radar classified this domain as Phishing, phishing, Security threats
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 16, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Sep 25, 2026
DestroyList Published
Mar 24, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
717 hours elapsed from detection to the first unavailable observation.
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including duplicate-disabled-178217.invalid)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: duplicate-disabled-178217.invalid

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.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/duplicate-disabled-178217.invalid"
  title="PhishDestroy threat report for duplicate-disabled-178217.invalid"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>