Skip to main content

Security report for raye7.com

Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

44/100

Risk levelHigh

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

The website raye7.com currently serves as a minimal placeholder with no substantive content beyond a client-side redirect to a /lander path. There is no visible business information, metadata, or user-facing content to analyze. The domain is registered and active but lacks a valid SSL certificate, resulting in no HTTPS support and a poor security posture. DNS records are basic with no DNSSEC or CAA records, and MX records point to smtp.google.com, which may be a misconfiguration. Overall, the site appears to be under development or inactive. From a technical perspective, the infrastructure is minimal with hosting likely on Amazon AWS based on IP addresses. No modern web technologies, frameworks, or CMS platforms are detected. Performance metrics are unavailable due to lack of content. Security best practices are not implemented, with no security headers, no HSTS, and no certificate transparency compliance. Security posture is weak, with critical issues including lack of HTTPS and absence of security policies or headers. No privacy or cookie policies are present, indicating non-compliance with GDPR or other privacy regulations. No contact or business information is available, limiting trust and credibility. Given these factors, the overall risk is elevated due to lack of security controls and transparency. Strategic recommendations include immediate implementation of HTTPS, deployment of security headers, addition of privacy and cookie policies, and publication of business and contact information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching raye7.com

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

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

Due to the absence of any business-related content or metadata on the website, no meaningful business intelligence can be derived. The domain registration is recent and consistent but provides no insight into market positioning, business model, or services. No partnerships or subsidiaries are identified. The lack of content suggests the business is either in early stages or the website is not actively maintained.

Security posture

The security posture of raye7.com is currently poor. The absence of an SSL certificate and HTTPS support is a critical vulnerability that exposes users to interception and undermines trust. No security headers or policies are implemented, and no incident response or vulnerability disclosure mechanisms are evident. DNSSEC and CAA are not enabled, reducing DNS security. The site does not demonstrate GDPR compliance or data protection readiness. Overall, the site is vulnerable to multiple attack vectors and lacks basic security hygiene.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable HSTS with includeSubDomains and preload to enforce HTTPS usage.
  4. Publish comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  5. Add clear contact and business information to improve credibility and trust.
  6. Configure DNSSEC and CAA records to enhance DNS security.
  7. Establish an incident response process and publish vulnerability disclosure information.
  8. Develop substantive website content with proper metadata and SEO optimization.
  9. Perform a full security audit to identify and remediate additional vulnerabilities.
  10. Improve website performance and accessibility to enhance user experience.
Technical notes

Notes

The website infrastructure is minimal with two A records pointing to IPs likely hosted on Amazon AWS. DNS is managed via GoDaddy nameservers without DNSSEC or CAA records. No SSL certificate is installed, and no TLS protocols are enabled, resulting in no HTTPS support. The HTTP headers are minimal with only content-type and date. The site serves a single HTML page with a JavaScript redirect to /lander and no other resources or metadata. No CMS, frameworks, or analytics tools are detected. Performance data is unavailable due to lack of content. The technical implementation is immature and requires significant development and security improvements.
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 raye7.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 raye7.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.