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

Score
72
HTTP status
307
https://willowstack.com/
SSL/TLS
Valid
2026-02-14T06:56:39+00:00
Server/AS
AMAZON-02, US
216.198.79.1
Open site

Scores & key points

Security
Reputation
Scam risk

Caution signals

No clear warnings detected.

Reputation

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

Review summary — willowstack.com

Overall 72 (Use with caution)

Some security settings are missing or not disclosed, so it should be used with care.

Strengths

  • Valid SSL/TLS certificate
  • HSTS enabled
  • SPF configured
  • DMARC configured

Weaknesses

  • CSP not set

Detailed review — willowstack.com

Domain review

Domain created: 2025-06-05T15:55:16Z (≈ 6m). Registrar: GoDaddy.com, LLC. Hosting / AS: AMAZON-02, US — United States. Popularity: OPR 0.00/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC reject. Certificate valid until: 2026-02-14T06:56:39+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 307 Redirect · Server AMAZON-02, US. HSTS Off (preload: None). Applies 1/6 security headers. DNSSEC Off. Email security: SPF On, DMARC reject. MTA‑STS policy: None. security.txt: not available. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 6m) (created on 2025-06-05T15:55:16Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-02-14T06:56:39+00:00.

Email security: SPF On, DMARC reject.

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:21:12
Email

Traffic signals

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

Performance

Field LCP-ms
Field INP-ms
Field CLS-
Lab LCP6085.8ms
Lab TBT41ms
Mobile score61
Lab LCP2168.4ms
Lab TBT122ms
Desktop score75
https://willowstack.com/

Security headers

  • HSTS
  • Content‑Security‑Policy
  • X‑Content‑Type‑Options
  • X‑Frame‑Options
  • Referrer‑Policy
  • Permissions‑Policy
Set CSP
This is a minimal CSP example. Adjust allowed sources to your project.
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
Prevent content type sniffing
add_header X-Content-Type-Options "nosniff" always;
Prevent clickjacking
add_header X-Frame-Options "SAMEORIGIN" 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;

Domain lineage

  1. 2025-06-05
    Domain registered: 2025-06-05T15:55:16Z

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB 0%
SPF Configured
DMARC Configured
DNSSEC No
Cookie security Absent
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): reject
DKIM alignment (adkim): r
SPF alignment (aspf): r
Aggregate reports (rua): mailto:dmarc_rua@onsecureserver.net
TXT: v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;
HTTP status307
Server AMAZON-02, US
CDN / Hosting AWS CloudFront
HSTSNo
Valid until2026-02-14T06:56:39+00:00
IssuerLet's Encrypt / R13
Registrant / organizationAMAZON-02, US
RegistrarGoDaddy.com, LLC
ASN16509
Network216.198.79.0/24
Title-
Final URL: https://willowstack.com/

Threat insight

Mostly safe (risk 18/100)
  • 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.

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 16509 / AMAZON-02

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 8685fc5e6f904c50472202c85d47391b686f81f33f4ca072eb1428960cdedc42

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