Skip to security report
Analytics Dashboard
Domain security report
owa-microsoft-share-com.jict.info favicon

owa-microsoft-share-com.jict.info

“Outlook — Launching secure cloud browser...”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Server error The latest stored response was inconclusive Observed · HTTP probe
Risk signals
VirusTotal detections: 2/92 Automated brand label: Microsoft
Oct 17, 2026 Microsoft CDN
API
Registrar
NameCheap
Resolved IP
188.114.96.3
Registered
Oct 17, 2025
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
2 det.
CF Radar
Malicious
URLScan
URLScan
Report ↗
TLS Certificate
Hostname mismatch
Google Trust Services / WE1 · Certificate hostname mismatch
Age
12 mo
Observed status
Server error 503
PhishDestroy
DestroyList
Listed

Source evidence

7 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

2 / 92

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Phishing
View full Cloudflare Radar report

Evidence Summary

Critical
VirusTotal
2/92
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

The domain owa-microsoft-share-com.jict.info was recorded in a VirusTotal scan on 2026-10-17, which documented 2 detections from 92 scanners. On the same date, a PageSpeed check measured a performance score of 100 for this domain.

Recorded Evidence

VirusTotal recorded 2 detections out of 92 scanners for owa-microsoft-share-com.jict.info on 2026-10-17. PhishDestroy included this domain in its internal listing as of 2026-10-17. A PageSpeed evaluation on 2026-10-17 documented a performance score of 100.

Interpretation

VirusTotal contains a scan-based record that measures how many security engines flagged owa-microsoft-share-com.jict.info. PhishDestroy’s internal listing documents the domain’s presence in a publisher-maintained catalogue, which is a different type of evidence from automated scanner results. The PageSpeed performance score provides a technical measurement of web performance as observed on its recorded date.

Recommended Actions

For owa-microsoft-share-com.jict.info, preserve the VirusTotal and PhishDestroy records for future comparison with subsequent scans and listings. Use the PageSpeed performance result to track any changes in technical performance over time. Reference all dated records to provide context for any new findings.

Data coverage & collection

20 · datasets with records / 11 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
2 / 92 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
NameCheap, Inc.Collection time not recorded
Network & DNS
188.114.96.3 · 0 · nameserversCollection time not recorded
TLS certificate
Google Trust Services / WE1
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
100/100 · mobile performance
Availability history
1 · stored state changes
Source observation history
2 · stored source events
IP reputation
Network-level observations
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

NameCheap, Inc. · 188.114.96.3 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) NameCheap US(US)
Abuse contact["abuse@namecheap.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for jict.info →
Registration (base domain)jict.info · Created Oct 17, 2025 (364d) — Expires Oct 17, 2026
HTTP Status503 Error
Technical detailsProvenance & timestamps
First DetectedOct 17, 2026
DOM Analysisanalyzed Oct 17, 2026score 71/1001 brand signal
Submitted URLhttp://owa-microsoft-share-com.jict.info/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-07 01:09:27
Valid until
2027-01-05 02:07:00
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-17 01:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint44001765c9719ef29168781bfbeb1450ac4e5b6e1ee4a3908da3e26fb515fa66
Certificate names · 1 SANs
  • jict.info

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.96.3rapiddns.io

Latest Classified Outcome 2026-10-17 10:00:30 UTC

Primary outcome Unknown reason: Origin unreachable 20% confidence
Attribution mechanism: Http 5xx source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Unknown Origin unreachable Http 5xx 20% 2026-10-17 10:00:30 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 00:17:25 UTC
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.
Technologies · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 1 detection
CRDF
DNS8
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of owa-microsoft-share-com.jict.info · checked Oct 17, 2026

100
Good
Performance
FCP
1.53s
First Contentful Paint
LCP
1.53s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.83s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://owa-microsoft-share-com.jict.info/
Outlook
Response
HTTP 200
HTML body
6.9 KB
Compressed
2.1 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
X-Powered-By: Express
Cache-Control: public, max-age=0
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: cf0808a61ec571e0c4975663903b288009d55502ac0445d9948983b339a5cf6e
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
Cache-Control
public, max-age=0
cf-cache-status
DYNAMIC
CF-RAY
a4bb1fffa8aa39d8-YYZ
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sat, 17 Oct 2026 00:18:15 GMT
Last-Modified
Tue, 13 Oct 2026 01:07:52 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=F5ElFQL73INgLxOZ21b8mUB8cWL9Ks54hokx09f592Iow7Cj13%2FlMS3%2FbdOIk74dY8k3Kx9oPRegpyFEphsoamypNcULJG7b0GC7%2F8r7DiZUvqjHr9VfwprOdI%2BNWzAAefXjcEW
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
X-Powered-By
Express

Values retained by the collector; long values may be shortened during collection.

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Not found
/robots.txt
HTTP response
404
Observed at
2026-10-17 00:18:19 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Sitemap

Not found
/sitemap.xml
HTTP response
404
Observed at
2026-10-17 00:18:19 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

security.txt

Not found
/.well-known/security.txt
HTTP response
404
Observed at
2026-10-17 00:18:19 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
cloudflare
Capture routing
Local archived 2026-10-17 00:18:19 UTC

Scanner note: transient_503: raw=transient_503; http=503; via=http_proxy; server=cloudflare

Title shown to the security scanner503 Service Unavailable
Title shown to a browser visitorOutlook — Launching secure cloud browser...
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-10-17 00:47:51 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: DNS8.
  2. Threat First Observed 2026-10-17 00:17:25 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. VirusTotal · Detection count

    1→2

  2. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  3. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
owa-microsoft-share-com.jict.info detected and queued for full analysis
Oct 17, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Oct 17, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
2/92 recorded on VirusTotal
Oct 17, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as Security threats, Phishing, phishing
Brand Impersonation
Impersonation of Microsoft
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Oct 17, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
VT Detection +1
+1 new detection (1 → 2): DNS8
Oct 17, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Oct 17, 2026
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 2 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Server error

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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 owa-microsoft-share-com.jict.info)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: owa-microsoft-share-com.jict.info

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Outlook — Launching secure cloud browser...”. Apparent target: Microsoft.

VirusTotal detections for owa-microsoft-share-com.jict.info: 2 (2026-10-17 00:47:51 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/owa-microsoft-share-com.jict.info"
  title="PhishDestroy threat report for owa-microsoft-share-com.jict.info"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>