Skip to main content

Security report for sajari.com

Algolia SAS · Technology · France

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

0–100, higher is better. How it is calculated

The domain sajari.com is registered to Algolia SAS, a French technology company established in 2009, specializing in search technology. However, the website content is currently inaccessible, returning a 403 Forbidden error with minimal HTML content. This prevents any direct analysis of the website's business offerings, policies, or technical implementation. The domain registration data is consistent and legitimate, but the lack of accessible content significantly limits the ability to assess the company's digital maturity or security posture. No metadata, forms, or contact information are available for review. The site appears to be hosted on Google Cloud DNS infrastructure, but DNSSEC is not enabled, representing a potential security enhancement opportunity. Overall, the website is currently non-functional from a user perspective, which negatively impacts trust and credibility.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

Need hands-on remediation? Email guard@offseq.com

Keep watching sajari.com

This scan found 26 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
72
Security headers
15
Email security
55
DNS health
75
Network security
100
GDPR outside view
40
Average
60

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Based on WHOIS data, Algolia SAS is the registrant, a known entity in the technology sector, likely related to search services. The domain age and registration details align with an established business. However, the lack of accessible website content means no insights into market positioning, business model, or customer engagement can be derived. No partner or subsidiary domains were identified. The absence of contact details or policies on the site limits transparency and user trust.

Security posture

The website currently returns a 403 Forbidden error, indicating restricted access or blocking, but no specific WAF vendor was identified. No security headers or SSL configuration details are available for analysis. DNSSEC is not enabled, which is a security best practice omission. No vulnerability disclosure or incident response information is present. The lack of accessible content and security policies suggests a low security maturity level from a user perspective. Recommendations include enabling HTTPS, implementing security headers, enabling DNSSEC, and publishing clear security and privacy policies.

Recommendations

  1. Restore website accessibility to allow full content and policy review.
  2. Enable HTTPS with a valid SSL certificate and verify proper configuration.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Enable DNSSEC to improve domain security.
  5. Publish comprehensive privacy, cookie, terms of service, and security policies on the website.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error with minimal HTML content indicating access is blocked or restricted. No specific WAF vendor identified. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
Algolia SAS
Content quality
poor

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No metadata, forms, scripts, or external links found in the HTML content.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact information or social media links found.
  5. WHOIS data shows a legitimate registration with a reputable registrar and organization.
  6. DNSSEC is not enabled, which is a security improvement opportunity.
  7. Nameservers indicate hosting on Google Cloud DNS infrastructure.
  8. No security headers or SSL configuration details available due to lack of content.
  9. Content safety rating is safe due to lack of content.
  10. AI scoring is heavily penalized due to blocked content.
Technical notes

Notes

Due to the 403 Forbidden error and minimal HTML content, no technical stack, CMS, or scripts could be detected. The domain uses Google Cloud DNS nameservers, indicating cloud hosting infrastructure. DNSSEC is not enabled. No metadata or SEO elements are present. Performance, mobile optimization, and accessibility cannot be assessed. The site requires restoration of content and technical elements to enable a full technical evaluation.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with sajari.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review sajari.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.