Is opuree.com a scam site? Scam, spam & reviews
Scores & key points
Caution signals ⓘ
- [Low] WHOIS information is masked/private.
Reputation
Review summary — opuree.com
Overall 89 (Mostly safe)Multiple security indicators are favorable and there are few major risk signals.
Strengths
- Valid SSL/TLS certificate
- HSTS enabled
- CSP enabled
- Domain age ≥ 1 year
Weaknesses
- SPF not configured
- DMARC not configured
Detailed review — opuree.com
Domain review
Domain created: 2017-03-23T15:02:05Z (≈ 8y 8m). Registrar: NAMECHEAP INC. Hosting / AS: CLOUDFLARENET, US. Popularity: Tranco #681550, OPR 1.98/10. Reputation: GSB clean WebRisk clean. Certificate valid until: 2026-01-21T11:28:08+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 CLOUDFLARENET, US. HSTS Off (preload: Unknown). Applies 5/6 security headers. DNSSEC Off. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 8y 8m) (created on 2017-03-23T15:02:05Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-01-21T11:28:08+00:00.
Applies 5/6 security headers.
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.
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.
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-11-17 11:28:35
Claim website ownership
Performance
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
v=spf1 include:_spf.google.com ~all
v=DMARC1; p=quarantine; rua=mailto:dmarc@opuree.com; ruf=mailto:dmarc@opuree.com; fo=1
@ 3600 MX 10 mail.opuree.com.
Essentials
Threat insight
- Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
- Without SPF, resistance to email sender spoofing is low. We recommend setting SPF records on any domain that sends email.
- If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.
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)
Before entering payment or personal information, verify the site operator/contact, HTTPS enforcement (HSTS), and the presence of DMARC and TLS‑RPT.
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum ccf51138f303940631fbaa9d03f91a78c8b3210a4ba4c99f7c93c7dc35896b62
Analyzing
Collecting various signals and public data.
- Start
- Fetch DNS / WHOIS
- Check HTTP response
- Verify SSL/TLS
- Query reputation
- Collect PageSpeed data
- Analyze security headers
- Check email security
- Integrate extended signals
- Build report