VirusTotal
15 / 94
“FNBO | Credit Card Login”
15 / 94
6 threat-system alerts
Reportprovider verdict: malicious
Report5/14
DBL_PHISH
checked — no match recorded
12 community references
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
Report| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | fnbocreditus.credit |
phishing | Phishing Block |
| Cloudflare DNS | fnbocreditus.credit |
malicious | Sinkholed |
| Hagezi Threat Feed | fnbocreditus.credit |
malicious | Sinkholed |
| DigiCert UltraDNS | fnbocreditus.credit |
malicious | Sinkholed |
| Quad9 DNS | fnbocreditus.credit |
malicious | Sinkholed |
| DNS4EU | fnbocreditus.credit |
malicious | Sinkholed |
Analysis conducted on July 23, 2026 identifies fnbocreditus.credit as a credential‑phishing infrastructure targeting FNBO credit‑card customers. The domain was registered on March 07, 2026 through NiceNIC International Group Co., Limited and resolves to the IPv4 address 5.252.116.244, which is assigned to AS207569 I‑SERVERS LTD located in Russia. The site employed a Let's Encrypt R12 certificate, indicating HTTPS was active at the time of capture. HTTP traffic was served by Nginx behind Cloudflare, and client‑side libraries such as Chart.js, Tailwind CSS, Unpkg, jsDelivr, Tippy.js and jQuery CDN were detected, suggesting a typical modern web stack used to render the page titled “FNBO | Credit Card Login”.
The domain appears on a single security blocklist and is currently listed by PhishDestroy as taken offline. VirusTotal scans recorded 15 detections out of 94 participating engines, reinforcing the malicious classification. Gridinsoft assigned a trust score of 0 / 100, and the authoritative nameservers are a.dnspod.com and c.dnspod.com. The evidence confirms that the operator set up a short‑lived credential‑phishing site shortly after registration and then removed it, a pattern consistent with opportunistic campaigns.
Defenders should add the domain and its resolving IP to network‑level deny lists, monitor DNS queries for the associated dnspod.com nameservers, and enforce strict credential‑validation controls for FNBO‑related services. Continuous observation of the AS207569 prefix for newly registered domains using similar technology stacks is advisable, as the infrastructure may be reused in future campaigns. Organizations should also ensure that endpoint protection solutions are updated to reflect the 15 VirusTotal detections associated with this host.
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='fnbocreditus.credit', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
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.
c.dnspod.comLocation describes the IP network.
8d63e8b1e1a02b24a976c6b704951456dcb9b6f20f849b5f66cfa74bd58f9be9Saved 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 fnbocreditus.credit · checked Mar 8, 2026
18 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.
151 stored lookalike domains
Showing 100 of 151
Reported by 1 community member, first seen Mar 7, 2026
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
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