www.financepaybnk.xyz is a confirmed brand impersonation threat targeting Mastercard users. Detected by 3/95 security vendors, this domain poses elevated risk.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
This domain, www.financepaybnk.xyz, is flagged as a brand impersonation threat specifically targeting Mastercard customers. Analysis indicates the infrastructure was designed to mimic legitimate financial services, likely to deceive users into submitting sensitive payment credentials or personal information under false pretenses. The page title, 'Finance Pay Bnk,' closely resembles official Mastercard payment portals, increasing the likelihood of successful social engineering attacks against unsuspecting victims. Infrastructure analysis reveals multiple technical indicators supporting the malicious classification. The domain was registered on April 18, 2025, through OwnRegistrar, Inc., and currently resolves to the IP address 192.3.190.186. Security vendors have flagged the domain in VirusTotal, with 3 out of 95 engines detecting malicious activity. Additionally, the domain appears on one security blocklist, further corroborating its fraudulent nature. The Gridinsoft trust score of 0/100 underscores the high-risk assessment associated with this infrastructure. Users who visited www.financepaybnk.xyz should take immediate remedial actions to mitigate potential exposure. First, clear all browser cache and cookies to remove any residual tracking elements. Second, monitor financial accounts linked to Mastercard for unauthorized transactions or suspicious activity. If credentials were entered, reset passwords immediately and enable multi-factor authentication where available. Consider reporting the incident to the impersonated brand’s fraud department for further investigation and potential account protection measures.
DOM Analysisanalyzed 2026年4月24日score 71/1001 brand signal
Submitted URLhttps://www.financepaybnk.xyz/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-281.invalid', port=80): Max retries exceeded with url: / (Caused by New
duplicate-disabled-281.invalid
Stored observation history1
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
