Skip to main content

Security report for aeo.press

aeo.press · Technology · N/a

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

Security score

58/100

Risk levelMedium

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

aeo.press is a technology-focused platform specializing in optimizing websites for AI chatbots and large language models (LLMs). It targets Webflow developers and businesses aiming to improve their visibility in AI-driven search and conversational platforms. The company offers AI visibility reports, embedded AI chatbots, and analytics tools to enhance customer engagement through AI channels. The website is professionally designed with a modern tech stack including Ruby on Rails, Bootstrap, and various JavaScript libraries, hosted likely on AWS infrastructure. Security posture is solid with HTTPS and domain status protections, though improvements such as enabling DNSSEC and adding security headers are recommended. Privacy compliance is basic with privacy and terms pages present but lacking cookie consent mechanisms. WHOIS data shows inconsistencies with a future domain creation date, which raises some trust concerns despite the professional appearance and content of the site.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

5 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 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching aeo.press

This scan found 24 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
52
Security headers
65
Email security
55
DNS health
80
Network security
40
GDPR outside view
53
Average
58

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention aeo.press, from OffSeq Breach.

No leaked records found

Breach holds no records for aeo.press right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

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 operates in a niche technology sector focused on AI chatbot optimization, positioning itself as a valuable partner for Webflow developers and businesses transitioning to AI-first customer engagement. Its revenue model includes SaaS offerings and revenue sharing with developers. The platform fosters a community of AI and Webflow experts, enhancing client relationships and market reach. The lack of explicit contact emails or phone numbers suggests a lean operation or early-stage company. The use of modern analytics and marketing tools indicates a data-driven approach to growth. However, the domain's WHOIS anomalies and absence of detailed business registration information suggest the need for further validation of business legitimacy.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain status protections that prevent unauthorized changes. The presence of CSRF tokens in forms indicates attention to secure input handling. However, the absence of DNSSEC and security headers such as Content Security Policy or HSTS reduces the overall security posture. No explicit security or incident response policies are published, which could impact compliance with regulations like GDPR or NIS2. The site uses Google Analytics with bot detection, but cookie consent mechanisms are missing, potentially exposing privacy compliance risks. Overall, the security posture is adequate for a small technology service but requires enhancements to meet higher compliance and security standards.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement comprehensive security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a detailed security policy and incident response plan accessible to users and partners.
  4. Add a cookie policy and consent mechanism to comply with GDPR and other privacy regulations.
  5. Validate and update WHOIS information to reflect accurate registration data and improve trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
aeo.press
Description
aeo.press helps businesses improve their presence in Large Language Model (LLM) chat bots by optimizing content for LLM consumption, providing analytics on customer interactions, and offering tools to improve LLM-based customer engagement.
Key services
AI visibility reports, AI chatbot embedding, Content optimization for LLMs, Analytics on customer interactions
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 5.3.6, Google Analytics 4, Hotwired Turbo-Rails, Stimulus JS, Chartkick, D3.js, Marked.js
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status EPP protections (renew, transfer, update, delete prohibited)
  • CSRF tokens in forms

Analytics and tracking

Services
Google Analytics 4
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Google Analytics 4
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on AI chatbot optimization for businesses and Webflow developers.
  3. No explicit contact emails or phone numbers found; contact is via form only.
  4. No cookie policy or consent mechanism detected.
  5. Privacy and terms pages exist but are basic.
  6. Modern tech stack with Rails and popular JS libraries.
  7. Good use of HTTPS and domain status protections but missing DNSSEC and security headers.
  8. No evidence of adult or questionable content.
  9. Google Analytics 4 used for tracking with bot detection.
  10. WHOIS data contains anomalies that reduce domain trust score.
Technical notes

Notes

The website is built on a modern and robust technology stack centered around Ruby on Rails with Hotwired Turbo and Stimulus for frontend interactivity. It leverages Bootstrap for responsive design and includes advanced visualization libraries like D3.js and Chartkick. Hosting appears to be on AWS, inferred from DNS servers. Performance is optimized with asynchronous loading of analytics scripts and module preloading. Accessibility is basic but present, and SEO is supported through comprehensive meta tags including Open Graph and Twitter Cards. The site includes AI-driven features such as bot detection and an embedded AI chatbot interface. Technical risks include missing DNSSEC and security headers, which should be addressed to reduce attack surface and improve compliance.
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 aeo.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 aeo.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.