Is ockim.com a scam site? Scam, spam & reviews
Scores & key points
Caution signals ⓘ
- [Low] Security headers such as HSTS and CSP are missing or insufficient.
- [Low] Without SPF/DMARC, email sender spoofing risk is increased.
- [Low] Cookie security attributes are insufficient (total 3).
Reputation
Review summary — ockim.com
Overall 80 (Mostly safe)Multiple security indicators are favorable and there are few major risk signals.
Strengths
- Valid SSL/TLS certificate
- SPF configured
- Domain age ≥ 1 year
Weaknesses
- HSTS not set
- CSP not set
- DMARC not configured
Detailed review — ockim.com
Domain review
Domain created: 2024-04-11T02:36:38Z (≈ 1y 8m). Registrar: Network Solutions, LLC. Hosting / AS: ORACLE-BMC-31898, US — United States. Popularity: OPR 1.98/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC None. Certificate valid until: 2026-03-13T19:30:11+00:00.
Shop / transaction review
No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.
Technical review
HTTP 200 Success · Server ORACLE-BMC-31898, US. HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF On, DMARC None. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. Missing cookie attributes: Secure×1 / HttpOnly×1 / SameSite×1. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 1y 8m) (created on 2024-04-11T02:36:38Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-03-13T19:30:11+00:00.
Email security: SPF On, DMARC None.
No mixed content detected.
Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.
Checking payment page security (HTTPS enforcement, form target host consistency, script integrity) along with customer support and return policy gives a more accurate sense of real‑world trust.
In parallel, applying security headers, automated certificate renewal, email domain protection (DMARC/TLS‑RPT), and removing mixed content will improve overall reliability and delivery/search stability.
Explanation — risks and areas to improve
Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.
Without DNSSEC, trust relies solely on parent name servers and DNS tampering risks can be higher in some environments.
If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.
Without MTA‑STS, SMTP TLS enforcement is weaker.
Without TLS‑RPT, it is harder to collect TLS failure signals and operational insight.
Without security.txt, the vulnerability disclosure channel is unclear and response may be delayed.
Cookies without Secure / HttpOnly / SameSite can be vulnerable to theft or session fixation attacks.
This analysis is an automated, data‑based opinion for reference only. Please verify the information yourself before paying or downloading anything.
About this report
- First analysis: -
- Last updated: 2025-12-22 23:10:15
Claim website ownership
Traffic signals
Performance
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload" always;
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
v=DMARC1; p=quarantine; rua=mailto:dmarc@ockim.com; ruf=mailto:dmarc@ockim.com; fo=1
Set-Cookie: name=value; Path=/; Secure; HttpOnly; SameSite=Lax
user-agent=30af564988215430fd9294bb2bb828dd
Domain lineage
-
2024-04-11Domain registered: 2024-04-11T02:36:38Z
Essentials
Threat insight
- Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
- Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.
- If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.
- Suspicious JavaScript patterns detected
The risk score of this site is calculated by combining browser security headers, SSL status, mixed content, email domain protection (SPF/DMARC), redirect/obfuscation patterns, and the results of Google Safe Browsing and WebRisk. There are currently few clear signs of malicious behavior, but insufficient security headers or email protection can increase the risk of phishing or man‑in‑the‑middle attacks. Before entering important information, re‑check the domain spelling and how you reached the site (ads, DMs, shortened URLs, etc.). Before entering payment or personal information, verify operator information (company/contact), HTTPS enforcement, DMARC/TLS‑RPT, and check for mixed content.
Deep scan (HTML / headers)
- Suspicious JavaScript obfuscation patterns have been observed.
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels. For session/login cookies, always set Secure, HttpOnly, and SameSite.
Set‑Cookie (samples)
PHPSESSID=e70391e8c489a2805dce4f98c8a9a681; path=/</code><br><code>mobile=false</code><br><code>user-agent=03c946fff4cc943209c8fdb153e5ec9b
User scenarios
If you make a payment on this site
No strong malicious signs were found, but online payments always carry some risk. Double-check the amount, payee and refund policy before you pay. Missing or weak DMARC lets attackers send spoofed payment emails. Type the domain manually instead of clicking links in unexpected messages.
If you log in or enter personal data
No clear malicious patterns were found, but treat passwords and 2FA codes as highly sensitive. Avoid reusing passwords across sites. Missing cookie security attributes or cross-domain POST forms can make sessions easier to steal or misuse. After logging in, watch for unusual account or billing activity.
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum fc13c6b84bbc87cf858bda3a228fcae673640fbbcd4cbe8105f8c1bfaecf6cdb