Skip to main content

Security report for rrss.lv

Red Rose · Other · Latvia

High risk. 8 critical or high findings in GDPR outside view, Security headers and 2 other checks.

Security score

47/100

Risk levelHigh

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

Red Rose is a small Latvian dance studio specializing in strip-plastic dance classes aimed at empowering women through dance. The website is built on WordPress and uses common plugins such as W3 Total Cache and Google reCAPTCHA to enhance performance and security. The site is well structured with clear navigation and content relevant to its target audience. Security posture is moderate with HTTPS enabled and reCAPTCHA protecting forms, but lacks security headers and visible privacy or cookie policies. WHOIS data could not be retrieved due to query limits, but the domain appears legitimate and consistent with a small local business. Overall, the site is professional and trustworthy but could improve privacy compliance and security best practices.

Scanned

NIS2 and GDPR posture

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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  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 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 rrss.lv

This scan found 25 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
62
Security headers
45
Email security
70
DNS health
75
Network security
20
GDPR outside view
10
Average
47

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 operates in a niche market offering dance classes and events for women, including beginner courses, private lessons, hen parties, and wedding dances. It targets local Latvian women interested in fitness and self-confidence through dance. The business model is service-oriented with revenue likely from class fees and event bookings. The website shows consistent branding and a clear value proposition but lacks advanced marketing or analytics tools. Partnerships appear limited to a web design company. Growth potential exists in expanding offerings or digital presence.

Security posture

The website uses HTTPS and integrates Google reCAPTCHA to protect forms, which are positive security measures. However, it lacks important HTTP security headers such as Content-Security-Policy and X-Frame-Options, which could expose it to clickjacking or content injection risks. No vulnerability disclosure or incident response information is provided, indicating limited security maturity. The absence of privacy and cookie policies also suggests compliance gaps with GDPR. Overall, the security posture is moderate but could be significantly improved with basic security headers and privacy documentation.

Recommendations

  1. Implement standard security headers (CSP, X-Frame-Options, X-Content-Type-Options) to enhance protection against common web attacks.
  2. Publish a comprehensive privacy policy and cookie consent banner to improve GDPR compliance and user trust.
  3. Regularly update WordPress core and plugins to mitigate vulnerabilities.
  4. Add an incident response contact or security policy page to demonstrate security readiness.
  5. Consider integrating analytics tools with privacy-respecting configurations to better understand user behavior and improve marketing.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Red Rose
Description
Red Rose is a dance studio specializing in strip-plastic dance, aimed at helping women become more confident, feminine, and beautiful. They offer beginner groups, basic groups, individual lessons, hen parties, and other dance-related services.
Key services
Iesācēju grupa (Beginner group), Pamatgrupa (Basic group), Individuālās nodarbības (Individual lessons), Vecmeitu ballītes (Hen parties), Dāvanu kartes (Gift cards), Kāzu deja (Wedding dance), Strečings (Stretching)
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Google reCAPTCHA, W3 Total Cache, Autoptimize
Frameworks
WordPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Google reCAPTCHA integration on forms

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Google reCAPTCHA
Transparency
poor

Site quality

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

Key observations

  1. Website is a WordPress-based dance studio site targeting Latvian women.
  2. No WHOIS data available due to query limit error.
  3. No privacy or cookie policy found on the site.
  4. Contact information is clearly provided including phone and email.
  5. Site uses HTTPS and Google reCAPTCHA for form security.
  6. No visible security headers detected.
  7. No adult or explicit content detected.
  8. No advertising or analytics beyond reCAPTCHA detected.
  9. Navigation and content are clear and well structured.
  10. No vulnerability disclosure or security policy pages found.
Technical notes

Notes

The website is built on WordPress 6.1.7 with common performance plugins like W3 Total Cache and Autoptimize. It uses jQuery and Google reCAPTCHA for client-side functionality and form protection. The site is mobile optimized with responsive design and lazy loading images. Performance is moderate with some optimization but no advanced CDN or analytics detected. The lack of security headers and privacy mechanisms indicates technical debt in security and compliance areas. Hosting provider details are not discernible from the content. Overall, the technical infrastructure is typical for a small business WordPress site but could benefit from modernization and enhanced security controls.
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 rrss.lv. 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 rrss.lv.

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.