Is xtremdiet.com a scam site? Scam, spam & reviews
Scores & key points
Caution signals ⓘ
- [Low] Without SPF/DMARC, email sender spoofing risk is increased.
Reputation
Review summary — xtremdiet.com
Overall 81 (Mostly safe)Multiple security indicators are favorable and there are few major risk signals.
Strengths
- Valid SSL/TLS certificate
- DMARC configured
- Domain age ≥ 1 year
Weaknesses
- HSTS not set
- CSP not set
- SPF not configured
Detailed review — xtremdiet.com
Domain review
Domain created: 2010-05-14T20:17:22Z (≈ 15y 7m). Registrar: NameCheap, Inc.. Hosting / AS: PLANETHOSTER-8, CA — Canada. Popularity: OPR 2.09/10. Reputation: GSB clean WebRisk clean. Email security: SPF Off, DMARC None. Certificate valid until: 2026-03-04T13:08:24+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 301 Redirect · Server PLANETHOSTER-8, CA. HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF Off, DMARC None. 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 (≈ 15y 7m) (created on 2010-05-14T20:17:22Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-03-04T13:08:24+00:00.
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.
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-27 17:42:43
Claim website ownership
Traffic signals
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=spf1 include:_spf.google.com ~all
Domain lineage
-
2010-05-14Domain registered: 2010-05-14T20:17:22Z
Essentials
DMARC details
v=DMARC1; p=none; rua=mailto:postmaster@xtremdiet.comv=DMARC1; p=none; rua=mailto:postmaster@xtremdiet.comThreat 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.
- Without SPF, resistance to email sender spoofing is low. We recommend setting SPF records on any domain that sends email.
- HTTP resources found on HTTPS page
- 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)
- Unencrypted (HTTP) resources are being loaded.
- Suspicious JavaScript obfuscation patterns have been observed.
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
If possible, configure the site to use HTTPS only and replace HTTP resources in the page with HTTPS. If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels.
Show examples of HTTP resources
http://code.jquery.com/jquery-latest.min.js
Set‑Cookie (samples)
375ee4adddc531350538f71a34bd12a7=ont435da8hk15n8atpdnvq0tk3; path=/; secure</code><br><code>virtuemart=ont435da8hk15n8atpdnvq0tk3
User scenarios
If you make a payment on this site
Entering card, bank or wallet details on this site is high risk. Only proceed after confirming the official domain via trusted channels. Mixed or non-encrypted (HTTP) resources or weak TLS can expose payment data or session tokens on some networks.
If you log in or enter personal data
Entering passwords or sensitive identifiers on this site is high risk. Account takeover or identity abuse is more likely; verify the official domain or app first. 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 12e224ea4799d7808a1751c988b938ed7547f59b2b6bbe1dffb7aaabdc082817