Is atlasnotes.app a scam site? Scam, spam & reviews
Scores & key points
Caution signals ⓘ
- [Low] Security headers such as HSTS and CSP are missing or insufficient.
- [Medium] Found 1 HTTP resources on an HTTPS page.
- [Low] Cookie security attributes are insufficient (total 2).
Reputation
Review summary — atlasnotes.app
Overall 77 (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 — atlasnotes.app
Domain review
Hosting / AS: SQUARESPACE - Squarespace, Inc., US — United States. Popularity: OPR 0.00/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC reject. Certificate valid until: 2026-05-01T14:09:42+00:00.
Shop / transaction review
No mixed content detected. Loads 1 HTTP resources (mixed content). Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.
Technical review
HTTP 200 Success · Server SQUARESPACE - Squarespace, Inc., US. HSTS Off (preload: Preloaded). Applies 3/6 security headers. DNSSEC Off. Email security: SPF On, DMARC reject. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://atlasnotes.app/.well-known/security.txt). Missing cookie attributes: Secure×0 / HttpOnly×1 / SameSite×1. Mixed content 1 items. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
GSB clean
WebRisk clean
Certificate valid until: 2026-05-01T14:09:42+00:00.
Email security: SPF On, DMARC reject.
Applies 3/6 security headers.
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 TLS‑RPT, it is harder to collect TLS failure signals and operational insight.
Cookies without Secure / HttpOnly / SameSite can be vulnerable to theft or session fixation attacks.
Mixed content increases the risk of eavesdropping and tampering. Standardize all resources on HTTPS.
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: 2026-02-01 01:06:01
Claim website ownership
Traffic signals
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
Set-Cookie: name=value; Path=/; Secure; HttpOnly; SameSite=Lax
crumb=Bf541K9QLZeeN2ZiYWQzYjc3OTcxMGY0NGUxZDVlNWJmNmFhOThk
Rewrite or update resource URLs to use HTTPS (e.g.,)
http://www.squarespace.com
@ 3600 MX 10 mail.atlasnotes.app.
Essentials
DMARC details
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=sv=DMARC1; p=reject; sp=reject; adkim=s; aspf=sThreat insight
- Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
- Mixed content increases the risk of eavesdropping and tampering. Standardize all resources on HTTPS.
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)
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
For session/login cookies, always set Secure, HttpOnly, and SameSite.
Set‑Cookie (samples)
crumb=BbAgW3hGSuRANWYyMzhkNmJiMWFiOGYxYWI0MjQ2MzUxMmMwMzMw;Secure;Path=/
User scenarios
If you make a payment on this site
Some technical or reputation signals suggest caution. Check the address bar, HTTPS and browser warnings before entering payment details. 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
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 d62010cb3d97cfa9cfc7f2f4270655f8c5766b643894ad74c4567d09c0eebaaf