Skip to main content

Security report for llmo.press

Technology · N/a

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

57/100

Risk levelMedium

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

llmo.press is a technology-focused platform aimed at helping businesses optimize their content for Large Language Model (LLM) chatbots, bridging the gap between traditional SEO and AI-driven customer engagement. The company is currently in private beta and offers services including content optimization for LLM consumption, analytics on customer interactions, and tools to improve AI-based engagement. The website is professionally designed using modern web technologies such as Ruby on Rails, Hotwired Turbo, and Bootstrap, hosted on AWS infrastructure. However, the site lacks critical compliance documents such as privacy and cookie policies, and no phone or physical contact information is provided beyond a single company email. Security posture is moderate with HTTPS enabled and CSRF tokens present, but no DNSSEC or security headers are implemented, and the WHOIS data shows suspicious inconsistencies including a domain creation date in the future, which impacts trustworthiness. Overall, the site demonstrates good technical implementation and content quality but requires improvements in privacy compliance, security best practices, and domain legitimacy to enhance business credibility and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

6 findings rated critical or high. Fix these first.

  1. 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 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';…

  2. 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

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching llmo.press

This scan found 23 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. See sample alerts.

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
52
Security headers
65
Email security
55
DNS health
80
Network security
40
GDPR outside view
50
Average
57

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

The business targets companies seeking to improve their visibility and engagement within AI chatbots and LLM platforms, positioning itself in a niche market of LLM optimization. Its B2B SaaS model focuses on providing analytics and optimization tools to enhance AI-driven customer interactions. The private beta status indicates an early-stage company likely small in size, with no public parent or subsidiary relationships. The platform leverages modern web frameworks and cloud hosting, suggesting a scalable infrastructure. The lack of extensive contact information and compliance documentation may limit customer trust and adoption. No partnerships or related domains were identified, indicating a standalone operation at this stage.

Security posture

The website employs HTTPS with valid SSL, includes CSRF tokens for form security, and restricts domain operations via prohibitive WHOIS status flags. However, it lacks DNSSEC, security headers such as Content-Security-Policy or X-Frame-Options, and does not publish a privacy policy or cookie consent mechanism, which are critical for GDPR compliance. No incident response or vulnerability disclosure information is available. The domain WHOIS data is inconsistent and suspicious, which may raise concerns about legitimacy. Overall, the security maturity is moderate but requires enhancements in DNS security, HTTP headers, and compliance documentation to reduce risk and improve trust.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  4. Add terms of service and incident response contact information to improve transparency and trust.
  5. Validate and correct WHOIS registration data to ensure domain legitimacy and consistency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
llmo.press helps businesses improve their presence in Large Language Model (LLM) chat bots. The platform bridges the gap between businesses and LLM platforms by optimizing content for LLM consumption, providing analytics on customer interactions, and offering tools to continuously improve LLM-based customer engagement.
Key services
LLM content optimization, Customer interaction analytics, Tools for improving LLM-based engagement
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 5.3.6, Hotwired Turbo-Rails, Stimulus JS, Marked.js, Chartkick, Chart.bundle.js, Rails ActiveStorage
Frameworks
Ruby on Rails
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • CSRF tokens present in meta tags
  • Client-side security controls (e.g., clientUpdateProhibited domain status)

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is in private beta with limited public information
  2. No privacy or cookie policies found
  3. Contact limited to single company email
  4. No phone numbers or physical addresses provided
  5. No social media links detected
  6. Modern tech stack with Rails and Hotwired
  7. No security.txt or vulnerability disclosure found
  8. No security headers detected in HTML content
  9. Domain WHOIS data inconsistent and suspicious
Technical notes

Notes

The website is built on a modern Ruby on Rails stack utilizing Hotwired Turbo and Stimulus for frontend interactivity, with Bootstrap for responsive design. It uses third-party libraries such as Marked.js for markdown parsing and Chartkick for data visualization. Hosting is on AWS infrastructure as indicated by DNS servers. The site loads external resources from trusted CDNs and Google Fonts. Performance is moderate with good mobile optimization and basic accessibility features. SEO optimization is basic with meta tags and Open Graph data but lacks structured data like JSON-LD. No CMS is detected, indicating a custom or framework-based build. Technical risks include missing security headers and incomplete compliance documentation.
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 llmo.press. 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 llmo.press.

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.