VirusTotal
6 / 92 engine detections
レポートを開く“FDIC Secure — Business Hours”
フィッシング: fdicsecure.net — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 92 engine detections
レポートを開く15/100
レポートを開くDBL_PHISH
4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
fdicsecure.net is an impersonation phishing page that borrows the name of the Federal Deposit Insurance Corporation, the US agency that insures bank deposits. Its page title, "FDIC Secure — Business Hours", is styled to look like an official service portal. It targets bank customers and anyone worried about the safety of their deposits. PhishDestroy first flagged it on 2026-09-05, and as of 2026-10-19 the site was still online with its content live.
Fake FDIC portals exploit the agency's authority. Visitors are told their deposits, insurance coverage or a frozen account need attention, then steered into forms or a call with a fake "agent". A title like "Business Hours" suggests a staffed office, which makes it more believable when victims are asked to phone in, verify their identity or send money. Victims can lose online banking logins, Social Security numbers, card details and identity documents. Some are also talked into transferring funds to a "protected" account that the scammers control. The real FDIC does not ask the public for account credentials or payments to safeguard deposits.
Six of 92 VirusTotal engines flag the domain as of 2026-10-19: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a minority of engines, but the flags come from several independent vendors. Spamhaus lists the domain on its DBL with a phishing designation, which feeds mail filters widely. The domain also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-06-25 through Fewmoretaps OU, operating as Trustname.com. PhishDestroy flagged it about ten weeks later. It is hosted on RouterHosting LLC in the United States, which matches the American audience a fake FDIC site would want. It uses a free Let's Encrypt certificate, so the browser padlock only means the connection is encrypted. It says nothing about who runs the site.
If you entered a banking password on this site, change it immediately from your bank's official app, and turn on or reset two-factor authentication. If you shared your Social Security number, card details or identity documents, call your bank using the number on your card. Freeze your credit with the three bureaus and report the incident to the FDIC and the FTC. If you sent money, ask your bank to recall the transfer right away. Defenders should block the domain at DNS, proxy and email gateways and search mail logs for messages linking to it.
chelsea.ns.cloudflare.comhuxley.ns.cloudflare.comLocation describes the IP network.
a575fd76e6450fb6f94f91baef9bfc35508bbc999daf1abd218e43928ec002c1www.fdicsecure.netSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.fdicsecure.netDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of fdicsecure.net · checked Sep 5, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
2→3
到達可能
6/92 engine detections
View source4 community references
View sourceNo threat flag
View sourcefdicsecure.net
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
fdicsecure.net
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
fdicsecure.net)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.