The domain ffbpublic.online is a confirmed phishing site engaged in brand impersonation, specifically targeting the brand 'across'. This site posed an elevated risk by mimicking legitimate services to deceive users into disclosing sensitive information, though no crypto drainer kit was detected. As of the latest verification, ffbpublic.online has been taken offline, but prior activity classified it as a phishing scam.
Technical indicators confirm the malicious nature of ffbpublic.online. The domain was flagged by 2 of 95 VirusTotal security vendors, including Netcraft and Seclookup, and appeared on 1 security blocklist (PhishDestroy). Registered through Global Domain Group LLC on September 16, 2025, it resolved to the IP address 163.61.188.89, hosted under AS153568 NEW DHAKA HARDWARE in the US. No SSL certificate was issued, and the observed page title was 'ffbpublic - Dedicated to innovating, simplifying, and humanizing digital banking'. Nameservers were vip1.cupisweb.com and vip2.cupisweb.com, with trust scores of 0/100 (Gridinsoft) and 34/100 (Scamadviser).
Users who interacted with ffbpublic.online should immediately change any credentials entered on the site, enable two-factor authentication (2FA) on affected accounts, and monitor for unauthorized transactions or identity fraud. If financial or crypto assets were exposed, revoke any token approvals and transfer funds to a new, secure wallet. Report the domain to platforms like Google Safe Browsing, PhishTank, or local cybercrime authorities to aid in takedown efforts and prevent further victimization.
DOM Analysisanalyzed 2026年4月23日score 10/1003 brand signals
Submitted URLhttps://ffbpublic.online/
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:14:26 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:17:56 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:56 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:25 UTC · precision low · basis bounded
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.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Gridinsoft
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
353.95
Estimate basis
Bounded by observations
Estimate precision
Low
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='ffbpublic.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
ffbpublic.online
保存済みの結果
到達不能
Stored observation history11
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)
