ScamLens analyzed oj.jo using 90+ threat intelligence sources and assigned a trust score of 73/100, classifying it as safe.
Trust Score: 73/100
Risk Level: Trusted
This result is still in the investigation range, so the domain alone is not enough for a decision. The next step is to cross-check the email, phone number, company identity, and scenario.
Quick Answer
This result is still in the investigation range, so the domain alone is not enough for a decision. The next step is to cross-check the email, phone number, company identity, and scenario.
Positive Signals
- + Google Safe Browsing: Safe
- + HTTPS encryption supported
Concerns
- - Cross-domain redirect detected
Score Breakdown
Was this assessment accurate?
oj.jo looks legitimate
No threat feeds have flagged this domain. Use standard online-safety habits.
- Bookmark the official URLScammers often clone legitimate brands at look-alike domains. A saved bookmark protects you from typos.
- Watch for unexpected payment requestsEven legitimate sites can be hijacked. Treat unsolicited 'urgent payment' prompts as suspicious.
- Verify HTTPS + the exact spellingConfirm the lock icon, and inspect the domain letter-by-letter before entering passwords or card details.
Trust but verify — open this domain on unrelated security services and compare the verdict.
Sign in to run the AI risk analysis
The threat-intelligence signals below are available to everyone. The plain-language AI risk summary is generated on demand for signed-in users — sign in (free) to run it for this domain.
Threat-intelligence sources
Checked across 27 sources — 1 flagged this domain
Show source breakdown
Threat-intelligence sources
Checked across 27 sources — 1 flagged this domain
- safe_browsing clean
- urlhaus clean
- cloudflare_radar clean
- cert_transparency clean
- alienvault_otx clean
- phishstats clean
- virustotal clean
- ipqs clean
- abuseipdb clean
- securitytrails clean
- phishdestroy clean
- threatfox clean
- shodan_internetdb clean
- phishtank clean
- urlscan clean
- rdap clean
- maltiverse clean
- dns_security clean
- wanted_domains clean
- darkweb clean
- openphish flagged
- scam_blocklist clean
- maltrail clean
- crypto_scam_feed clean
- phishing_army clean
- hagezi_tif clean
- red_flag_domains clean
ScamLens aggregates real-time signals from 90+ commercial and open-source threat-intelligence providers including Google Safe Browsing, VirusTotal, PhishTank, URLhaus, ThreatFox, Cloudflare Radar, OTX, IPQS, GoPlus, Honeypot.is, and more. A flagged signal is evidence; the absence of flags is not proof of safety. Use the signals below alongside community reports to decide.
Advanced Scan
Comprehensive data lookup across premium sources
- Website history verification
- Detailed WHOIS information
- Reverse WHOIS association
- Traffic rank analysis
- Company registration check
AI Deep Investigation
Cross-check the story, claims, and supporting evidence before you decide
- Everything in Advanced Scan
- AI website content analysis
- AI cross-reference verification
- Claim authenticity validation
- Detailed report with evidence
Comprehensive Investigation
Full-spectrum investigation with company deep search & social intelligence
- Everything in Deep Investigation
- AI company background search
- Social media intelligence
- Detailed suspicious point analysis
- Event timeline & entity connections
This analysis is for informational purposes only and does not constitute a legal determination.
Security Sources
Domain Information
- DNSSEC
- Disabled
SSL/TLS Certificate
No data available
Redirect Chain
1 hopCross-domain redirect detected
This domain redirects to a different domain. This is commonly used by phishing sites to evade detection.
oj.jo → juma.jo
oj.jo
Status: 301Final destination
juma.jo
Server Information
- IP Address
- 192.250.239.61
- Hosting Provider
- WHG Hosting Services Ltd
- ASN
- AS51713 WHG Hosting Services Ltd
- Server Location
- London, United Kingdom
- Organization
- WHG Hosting Services Ltd
Related Intelligence
Technical Details (DNS / Headers / Subdomains)
DNS Records
Email Security
SPF Configured DMARC Not Configured| Type | Value |
|---|---|
| A | 192.250.239.61 |
| MX | 0 oj.jo |
| NS | ns4.mysecurecloudhost.com |
| NS | ns1.mysecurecloudhost.com |
| NS | ns2.mysecurecloudhost.com |
| NS | ns3.mysecurecloudhost.com |
| TXT | v=spf1 +a +mx +ip4:192.250.239.61 include:spf.mysecurecloudhost.com ~all |
HTTP Security Headers
1/6upgrade-insecure-requests
Channels / Subdomains
No data available
Community Reports
Log in to report and share your experience
Continue Investigating
The result is still in the investigation range. Cross-check the email, phone, and entity data next
Medium-risk domains are easiest to misread when you only check one signal. The decision gets more reliable once you cross-check the email, phone number, company identity, and business scenario together.
Recommended First
Analyze the related email or invoice
Confirm whether the billing notice, restriction alert, or support email actually matches the site.
Check the company or seller identity
Compare the domain against the company identity, merchant profile, or hiring details.
Check the related phone number
If the actor wants a callback, phone verification, or one-time code readout, verify that number next.
Open the matching scenario guide
If the case involves investing, shopping, or recovery services, verify it through the matching scenario guide.
The results are based on multiple third-party data sources and AI models. False positives or negatives may occur. This report should not be used as the sole basis for any decision. Please verify with additional sources.
Verify the related evidence objects first
Medium-risk cases are easiest to misread when you only check one signal. Verify the email, phone, and entity before deciding whether to report or stop the transaction.
If you already paid or exposed account access, skip the investigation loop and move into the action plan.
Related Security Guides
Learn more about how to protect yourself from this type of threat.
Understanding this threat
FAQ
Is oj.jo safe to visit?
oj.jo received a trust score of 73/100 from ScamLens, based on analysis of 30+ threat intelligence sources. No significant threats were detected. The site appears safe and trustworthy.
Was oj.jo flagged by any threat databases?
oj.jo was flagged by 1 out of 30+ threat intelligence sources. Specifically flagged by: openphish. The detected threat categories include: general threat.
How old is oj.jo?
Registration date information for oj.jo is not publicly available through WHOIS records, which can itself be a risk indicator.
Does oj.jo use HTTPS and have a valid SSL certificate?
ScamLens could not verify the SSL certificate details for oj.jo during this scan. Treat this as unavailable evidence, not as proof that the site is safe or unsafe.
What security headers does oj.jo implement?
oj.jo is missing important security headers: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Strict-Transport-Security, Referrer-Policy, Permissions-Policy. Missing security headers can leave visitors vulnerable to cross-site scripting (XSS) and other web-based attacks.
What does the ScamLens community think about oj.jo?
No community votes or reports have been submitted for oj.jo yet. You can be the first to share your experience.
Where is oj.jo hosted?
oj.jo is hosted by WHG Hosting Services Ltd in London, United Kingdom (ASN: ASAS51713 WHG Hosting Services Ltd).
What should I do about oj.jo?
Based on our analysis, oj.jo appears safe. You can proceed with normal caution. Always verify URLs manually and avoid clicking suspicious links.
Is this report useful?
Use this report to prompt others to keep cross-checking the email, phone number, and entity details instead of clearing it too early.
Forward to your parents — they deserve to browse safely too.
About this analysis
This report is generated from real-time data across 90+ threat intelligence sources, combined with AI analysis and community feedback.
Learn about our scoring methodology | Last analyzed: August 7, 2026