VirusTotal
8 / 91 engine detections
レポートを開く“RFP Invitation”
フィッシング: jalebinspice.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 8/91 (alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
8 / 91 engine detections
レポートを開く15/100
レポートを開く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
jalebinspice.com hosts an impersonation phishing page titled "RFP Invitation", built to look like a legitimate request for proposal sent to suppliers and contractors. Its targets are business users, especially people in sales, procurement and finance who routinely receive bid invitations. PhishDestroy first flagged it on 2026-09-17, and as of 2026-10-19 the site was still online and serving its phishing content.
RFP lures usually arrive by email as an invitation to review tender documents or submit a bid. The link leads to a page like this one, which asks the visitor to sign in with a work email account to view the files. Whatever is typed in goes to the operators, who can use the mailbox to read correspondence, launch invoice or payment-redirection fraud, and send the same lure to the victim's contacts from a trusted address.
On 2026-09-29, 8 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft, MalwareURL, SOCRadar and VIPRE. That is a modest but meaningful spread across independent vendors, so many filters will still let it through. The domain also appears in 4 AlienVault OTX threat pulses, which shows other researchers have linked it to malicious activity, and it is listed on the PhishDestroy blocklist.
The domain was registered through NameCheap, Inc. on 2024-05-06, more than two years before it was seen hosting this lure. An older domain like this gets past filters that treat newly registered names with suspicion, and the name itself has nothing to do with procurement. It resolves to 67.223.118.123 on Namecheap, Inc. hosting in the US. Its Let's Encrypt certificate gives the page a browser padlock, but that only shows the connection is encrypted, not that the site is trustworthy.
If you entered a password on this page, change it right away, along with any other account that uses the same password, and turn on two-factor authentication. Sign out all active sessions. Check your mailbox for new forwarding rules, filters or app authorizations you did not create, and warn your contacts not to trust recent RFP or invoice emails sent from your address. Security teams should block the domain and its IP, search mail logs for messages linking to it, and reset credentials for any user who clicked through.
dns2.namecheaphosting.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
bf271c1c01b82cd612557433b2ebb6d3e1989387925eeeb9ced4448713cad565mail.jalebinspice.comwww.jalebinspice.comSaved 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.
mail.jalebinspice.comDomain recordwww.jalebinspice.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of jalebinspice.com · checked Sep 17, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
jalebinspice.com
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
redirected→live_content
content_served
不明→redirected
http_redirect
live_content→redirected
http_redirect
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
4 community references
View sourceNo threat flag
View source8/91 engine detections
View sourcejalebinspice.com
View sourceListed 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 ↗
jalebinspice.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.