Is lumenfield.com a scam site? Scam, spam & reviews

Score
88
HTTP status
301
https://lumenfield.com/
SSL/TLS
Valid
2026-02-03T23:54:51+00:00
Server/AS
CLOUDFLARESPECTRUM Cloudflare, Inc., US
198.202.211.1
Open site

Scores & key points

Security
Reputation
Scam risk

Caution signals

No clear warnings detected.

Reputation

Open PageRank 4.72 / 10
Tranco 636708 Global
Source: top-1m.csv

Review summary — lumenfield.com

Overall 88 (Mostly safe)

Multiple security indicators are favorable and there are few major risk signals.

Strengths

  • Valid SSL/TLS certificate
  • HSTS enabled
  • CSP enabled
  • SPF configured
  • DMARC configured
  • Domain age ≥ 1 year

Weaknesses

Detailed review — lumenfield.com

Domain review

Domain created: 2020-09-11T20:46:59Z (≈ 5y 3m). Registrar: CSC Corporate Domains, Inc.. Hosting / AS: CLOUDFLARESPECTRUM Cloudflare, Inc., US — United States. Popularity: Tranco #636708, OPR 4.72/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC reject. Certificate valid until: 2026-02-03T23:54:51+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 CLOUDFLARESPECTRUM Cloudflare, Inc., US. HSTS Off (preload: None). Applies 3/6 security headers. DNSSEC Off. Email security: SPF On, DMARC reject. MTA‑STS policy: None. security.txt: not available. Missing cookie attributes: Secure×0 / HttpOnly×0 / SameSite×0. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 5y 3m) (created on 2020-09-11T20:46:59Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-02-03T23:54:51+00:00.

Email security: SPF On, DMARC reject.

Applies 3/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.

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.

Without MTA‑STS, SMTP TLS enforcement is weaker.

Without security.txt, the vulnerability disclosure channel is unclear and response may be delayed.

Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.

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-19 09:12:46
Email

Traffic signals

UTM source -
UTM medium -
ref / from -
Shortened URLs on page 0

Performance

Field LCP-ms
Field INP-ms
Field CLS-
Lab LCP-ms
Lab TBT-ms
Mobile score-
Mobile measurement error: request_failed
Lab LCP2163ms
Lab TBT196ms
Desktop score76
https://lumenfield.com/

Security headers

  • HSTS
  • Content‑Security‑Policy
  • X‑Content‑Type‑Options
  • X‑Frame‑Options
  • Referrer‑Policy
  • Permissions‑Policy
Prevent content type sniffing
add_header X-Content-Type-Options "nosniff" always;
Set Referrer‑Policy
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
Set Permissions‑Policy
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
Add MX records
@  3600  MX  10  mail.lumenfield.com.

Domain lineage

  1. 2020-09-11
    Domain registered: 2020-09-11T20:46:59Z

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB 0%
SPF Configured
DMARC Configured
DNSSEC No
Cookie security No issues detected
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): reject
Aggregate reports (rua): mailto:dmarc_rua@emaildefense.proofpoint.com
Failure reports (ruf): mailto:dmarc_ruf@emaildefense.proofpoint.com
TXT: v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.comv=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
HTTP status301
Server CLOUDFLARESPECTRUM Cloudflare, Inc., US
CDN / Hosting Cloudflare CDN
HSTSNo
Valid until2026-02-03T23:54:51+00:00
IssuerGoogle Trust Services / WE1
Registrant / organizationCLOUDFLARESPECTRUM Cloudflare, Inc., US
RegistrarCSC Corporate Domains, Inc.
ASN209242
Network198.202.211.0/24
Title301 Moved Permanently
Final URL: https://lumenfield.com/

Threat insight

Mostly safe (risk 0/100)
  • Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.

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.

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.

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.

Server location

United States (US) · ASN 209242 / Cloudflare London, LLC

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 2e3e3d2ee0e3b64507a27cf943a1e637bccd2c3ad1c79d594063602d9d44a6cc

Analyzing

Collecting various signals and public data.

  1. Start
  2. Fetch DNS / WHOIS
  3. Check HTTP response
  4. Verify SSL/TLS
  5. Query reputation
  6. Collect PageSpeed data
  7. Analyze security headers
  8. Check email security
  9. Integrate extended signals
  10. Build report