Skip to main content

Security report for roeye.com

Other · N/a

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

Security score

69/100

Risk levelMedium

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

The website roeye.com is currently inaccessible due to a CloudFront 403 error indicating that requests are blocked, possibly due to traffic or configuration issues. This prevents any meaningful extraction of business, security, or compliance information from the site content. The domain is registered with Amazon Registrar, Inc. since 2008, indicating a mature domain age, but no registrant details or privacy protection are present. The lack of accessible content and security policies severely limits the ability to assess the company's market position, services, or compliance posture. Technically, the site is hosted on AWS infrastructure but lacks DNSSEC and visible security headers. The security posture cannot be evaluated due to the blocking mechanism. Overall, the site scores very low on content quality, technical implementation, security, privacy compliance, and business credibility due to inaccessibility.

Scanned

This is an earlier scan of roeye.com. View the latest report

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

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

  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

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

Keep watching roeye.com

This scan found 21 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
77
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
50
Average
69

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

No business intelligence data could be extracted from the website due to the access block. The domain age suggests a potentially established entity, but no information about market positioning, business model, or partnerships is available. No contact details, certifications, or trust indicators are present. The domain uses AWS DNS services but no further technical or business ecosystem information is available.

Security posture

The security posture assessment is limited by the lack of accessible content. The domain does not have DNSSEC enabled, which is a recommended security practice. The site is protected by AWS CloudFront which is currently blocking access, indicating some level of security control. No security headers or SSL configuration details were found. No incident response or vulnerability disclosure information is available. Overall, the security maturity cannot be fully assessed but the blocking suggests some protective measures are in place.

Recommendations

  1. Resolve the CloudFront 403 error to restore website accessibility for proper analysis and user access.
  2. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  3. Implement and publish comprehensive privacy, cookie, and security policies to improve compliance and trust.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website.
  5. Ensure HTTPS is properly configured and enforced site-wide to protect data in transit.
Site observations

Automated reading of the public site. Ratings are indicative.

CloudFront detected. 403 ERROR page generated by CloudFront indicating request blocked due to traffic or configuration error. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

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 a CloudFront 403 error.
  2. No metadata, structured data, or visible content available for analysis.
  3. No contact information, policies, or business details found on the site.
  4. Domain is registered with Amazon Registrar, Inc. since 2008 and is active until 2026.
  5. DNSSEC is not enabled, which is a security improvement opportunity.
  6. No security headers or SSL configuration details available from provided data.
  7. No scripts, forms, or external links beyond AWS DNS servers and ICANN references found.
  8. Website currently provides no trust or business credibility signals.
  9. Analysis incomplete due to WAF/security mechanisms. For accurate analysis, please contact guard@offseq.com
Technical notes

Notes

The website is hosted on AWS infrastructure with DNS managed by Amazon Registrar, Inc. The domain is mature, created in 2008, but DNSSEC is not enabled. The site currently returns a CloudFront 403 error blocking access, preventing analysis of the tech stack, CMS, or performance. No metadata, scripts, or forms are present in the accessible content. The lack of visible SEO or accessibility features suggests technical debt or misconfiguration. The hosting provider is reliable but the current configuration blocks legitimate access, which is a critical operational risk.
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

Earlier scans of this domain

  1. 69/100Medium30 findingsView report
Reviews of this site

Share your experience with roeye.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 roeye.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.