Is elastic.co a scam site? Scam, spam & reviews
Scores & key points
Overview
software business, developer of Elasticsearch
Caution signals ⓘ
No clear warnings detected.
Reputation
Review summary — elastic.co
Overall 79 (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 — elastic.co
Domain review
Hosting / AS: GOOGLE-CLOUD-PLATFORM, US — United States. Popularity: Tranco #2632, OPR 6.40/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC quarantine. Certificate valid until: 2026-01-08T14:11:59+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 GOOGLE-CLOUD-PLATFORM, US. HSTS Off (preload: Unknown). Applies 1/6 security headers. DNSSEC Off. Email security: SPF On, DMARC quarantine. 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
GSB clean
WebRisk clean
Certificate valid until: 2026-01-08T14:11:59+00:00.
Email security: SPF On, DMARC quarantine.
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 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.
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-20 13:59:39
Claim website ownership
Traffic signals
Performance
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 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;
Essentials
DMARC details
v=DMARC1; p=quarantine; rua=mailto:dmarc@elastic.co,mailto:dmarc_agg@vali.email;v=DMARC1; p=quarantine; rua=mailto:dmarc@elastic.co,mailto:dmarc_agg@vali.email;Threat 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.
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.
- The site heavily relies on third‑party resources.
For session/login cookies, always set Secure, HttpOnly, and SameSite.
Set‑Cookie (samples)
euid=afc91872-b546-472e-8cb1-2f0093157453; Expires=Tuesday, 19 January 2038 01:00:00 GMT; Path=/; Domain=.elastic.co;</code><br><code>euid=9b62c3f2-5ed8-4e7d-8f34-0696cefec5c2; Expires=Tuesday, 19 January 2038 01:00:00 GMT; Path=/; Domain=.elastic.co;
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. 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 bfc498c5db42045ba69da8bbef2ce724c9c9765d9967e4a02b6d60de45057413