ussban.migfid.online was a phishing page impersonating U.S. Bank and aimed at its online banking customers. The subdomain "ussban" is a near-miss spelling of the bank's name, chosen to pass a quick glance in a text message or email. PhishDestroy first detected it on 2026-08-30. The site has been offline since 2026-09-11, and on 2026-10-19 the domain no longer resolved in DNS.
How the scam works
The page carried the title "Bot Verification", while urlscan.io matched its content to U.S. Bank and generic banking login templates. That gap between a neutral-looking title and a banking-brand classification is worth noting. Pages like this usually open with a fake human check that makes the visit feel routine, then lead to a copy of the bank's sign-in screen. Whatever the victim types there goes straight to the operators. That can include username and password, one-time codes, card details or identity information. With those, attackers can try to take over the account, move money or reuse the credentials elsewhere.
Evidence
On 2026-09-02, 8 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft, Netcraft, SOCRadar and desenmascara.me. That is a modest share, but the vendors are independent of each other and include established phishing feeds such as Netcraft and ESET. urlscan.io returned a malicious verdict and identified the U.S. Bank branding directly. PhishDestroy lists the domain on its own blocklist.
Infrastructure
The domain was registered on 2026-08-29 through HOSTINGER operations, UAB, and PhishDestroy caught it the very next day. That timing fits a domain set up for a short campaign. It was hosted on the FranTech Solutions network in Luxembourg and used a free Let's Encrypt certificate. The padlock in the browser therefore proved nothing about who ran the site. The whole operation lasted about two weeks before going dark on 2026-09-11.
What to do
If you entered U.S. Bank credentials on this page, change your online banking password right away using the bank's official app or a typed-in address. Do the same anywhere else you reused that password. Call the number on the back of your card, report the phishing, and ask the bank to review recent transactions and reset or reissue any card you entered. Re-enroll your two-factor authentication and watch for follow-up calls or texts pretending to be the bank's fraud team. Security teams should block the domain and related subdomains, search mail and proxy logs for visits since 2026-08-29, and treat any user who submitted data as a compromised banking account.
Registration (base domain)migfid.online · Created Aug 29, 2026 (52d · New)—Expires Aug 29, 2027
Time to First Unavailability11 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 DetectedAug 30, 2026
Submitted URLhttps://ussban.migfid.online/
Favicon Hash
ICANN OVERSIGHTRegistration: migfid.online
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For the registrable domain migfid.online behind this subdomain, 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
198.251.84.200
Network ASN
AS53667
Organization
FranTech Solutions
Observed location
Luxembourg, LU
Server header
LiteSpeed
Nameservers 2
ns5.asurahosting.com
ns6.asurahosting.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-08-30 10:56:03
Valid until
2026-11-28 10:56:02
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-08-30 19:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb5e69ee47dc80c155af3afe49d9d6e6b32143f350df8d1819fe15687c9eacac3Certificate names · 1 SANs
www.ussban.migfid.online
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-19 01:13:35 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-06 22:16:43 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-06 22:16:43 UTC → 2026-09-30 16:14:55 UTC · 569.97hmidpoint estimate ≈ 2026-09-18 19:15:49 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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.ussban.migfid.onlineDomain record
The original observation time is not recorded for these hostnames.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · ussban.migfid.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches8
Same favicon hash or the same page title as this host.
5 evidence signal groups linked0 stored notification recordsContent 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.
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 →
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 ussban.migfid.online)
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)
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
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.
(LT)
