VirusTotal
1 / 92
engines flag the domain
“Outlook — Launching secure cloud browser...”
ImitatesMicrosoft
Outlook Connecting to secure mail server...
The page displays Outlook branding and a login prompt that mimics Microsoft’s OWA interface, indicating brand impersonation and credential theft attempts.
Automated reading of the page content, not a manual finding.
1 / 92
engines flag the domain
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 188.114.97.1 · TLS: Google Trust Services
malicious
Each check shows its own collection time. Zero detections do not guarantee safety.
Microsoftなりすまし: owa-microsoft-share-com.jict.info — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 2/92 (CRDF, DNS8); CF Radar malicious; PhishDestroy score…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 92 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開く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
owa-microsoft-share-com.jict.info is an impersonation phishing page built to look like Microsoft Outlook. Its hostname strings together "owa", "microsoft", "share" and "com" to resemble a Microsoft shared-document link, but it sits under the unrelated jict.info domain. It targets people who use Outlook for work or personal email. PhishDestroy first saw it on 2026-10-17. The site has been offline since 2026-10-18 and showed no threatening content when checked on 2026-10-19.
The page carried the title "Outlook — Launching secure cloud browser...", which reads like a Microsoft loading screen. Pages like this usually arrive as a "document shared with you" email and lead to a fake Outlook or Microsoft sign-in form. Whatever the victim types there, their email address and password, sometimes along with a one-time code, goes straight to the operators. A stolen Outlook account gives them the mailbox, contacts and any services tied to that Microsoft login, and they often use it to send the same lure to the victim's colleagues.
Independent detection was thin. On 2026-10-17, only 2 of 92 VirusTotal engines flagged the domain, CRDF and DNS8. Apart from PhishDestroy, no blocklist listed it. Low counts are common for short-lived phishing hosts that disappear before most vendors review them, so a near-clean VirusTotal result here is not a sign the page was safe.
The jict.info domain was registered through NameCheap, Inc. on 2025-10-17, exactly a year before PhishDestroy detected the phishing subdomain. A domain that sits unused for a while tends to look less suspicious than a brand-new one. Traffic went through Cloudflare (AS13335, US), which hides the real origin server. The page stayed live for only about a day before it went offline.
If you entered your Microsoft or Outlook credentials on this page, change that password right away and change it on any other site where you used the same one. Then review your account's recent sign-in activity, sign out all active sessions and turn on or re-register two-factor authentication. Check your mailbox for new forwarding rules or inbox rules you did not create, and warn your contacts about any odd messages sent from your account. Security teams should block the domain and search mail logs for the "secure cloud browser" lure. Watch for Microsoft 365 sign-ins from unfamiliar locations after 2026-10-17.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
44001765c9719ef29168781bfbeb1450ac4e5b6e1ee4a3908da3e26fb515fa66jict.infoSaved 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 owa-microsoft-share-com.jict.info · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://owa-microsoft-share-com.jict.info/Content-Type: text/html; charset=UTF-8Server: cloudflareX-Powered-By: ExpressCache-Control: public, max-age=0CF-Cache-Status: DYNAMICContent-Encoding: gzipcf0808a61ec571e0c4975663903b288009d55502ac0445d9948983b339a5cf6eh3=":443"; ma=86400public, max-age=0DYNAMICa4bb1fffa8aa39d8-YYZkeep-alivegziptext/html; charset=UTF-8Sat, 17 Oct 2026 00:18:15 GMTTue, 13 Oct 2026 01:07:52 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=F5ElFQL73INgLxOZ21b8mUB8cWL9Ks54hokx09f592Iow7Cj13%2FlMS3%2FbdOIk74dY8k3Kx9oPRegpyFEphsoamypNcULJG7b0GC7%2F8r7DiZUvqjHr9VfwprOdI%2BNWzAAefXjcEWcloudflarecfCacheStatus;desc="DYNAMIC"chunkedExpressValues retained by the collector; long values may be shortened during collection.
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.
不明→inactive
expired_landing_page · lifecycle_notice_page
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
1→2
到達可能
No threat flag
View source2/92 engine detections
View sourceowa-microsoft-share-com.jict.info
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
owa-microsoft-share-com.jict.info
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 ↗
owa-microsoft-share-com.jict.info)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.