Skip to main content

Security report for rose365.net

Other · N/a

Medium risk. 6 critical or high findings in Email security, Security headers and 2 other checks.

Security score

64/100

Risk levelMedium

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

The website www.rose365.net is currently inaccessible beyond a Cloudflare security challenge page that uses Turnstile captcha to verify visitors are not bots. This prevents access to any substantive content or business information. The domain WHOIS data is unavailable, with the raw WHOIS query returning no match, indicating either a privacy-protected registration or an unregistered domain. The expiry date is noted as August 15, 2026, but no registrar or registrant details are provided. Due to the lack of accessible content and registrant data, the business overview, market position, and key services cannot be determined. Technically, the site uses Cloudflare's security services and implements a Content-Security-Policy header, but no other technologies or CMS are identifiable. Security posture is limited by the inability to analyze the actual site content, but the presence of Cloudflare WAF and Turnstile captcha indicates some level of bot protection. Overall, the site scores low on content quality, business credibility, and privacy compliance due to the lack of visible information and policies. Strategic recommendations include making business and contact information publicly accessible, publishing privacy and cookie policies, and ensuring WHOIS data is complete and accurate to improve trust and compliance.

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

6 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

  4. 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 rose365.net

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
37
Security headers
65
Email security
60
DNS health
70
Network security
100
GDPR outside view
53
Average
64

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 accessible content and registrant information, no meaningful business intelligence can be derived. The domain appears to be protected or blocked by Cloudflare, and no social media, partner, or subsidiary domains are linked. There is no evidence of a defined business model, target customer segments, or revenue streams. The lack of transparency and public information severely limits any competitive or market positioning analysis.

Security posture

The website employs Cloudflare's security services including a WAF and Turnstile captcha, which provide protection against automated bots and some malicious traffic. A Content-Security-Policy header is present, which is a positive security control. However, the inability to access the actual website content prevents a full security assessment. No privacy policies, incident response contacts, or vulnerability disclosures are visible. The domain WHOIS data is missing, which raises concerns about transparency and legitimacy. Overall, the security posture is moderate in terms of perimeter defenses but weak in transparency and compliance.

Recommendations

  1. Make website content publicly accessible beyond the Cloudflare security challenge to allow proper analysis and user access.
  2. Publish comprehensive privacy and cookie policies to comply with GDPR and build user trust.
  3. Provide clear business contact information including emails and phone numbers on the website.
  4. Ensure WHOIS domain registration data is complete and publicly available to improve legitimacy and trust.
  5. Implement SEO best practices including metadata and structured data to improve search engine visibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Website is behind Cloudflare security challenge page with Turnstile captcha, blocking direct content access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
Cloudflare Turnstile, JavaScript, HTML5, CSS3
SEO
poor

Security

Observed score
30/100
Good practices seen
  • Use of Cloudflare security service
  • Content-Security-Policy header present

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 blocked by Cloudflare security challenge page
  2. No business or contact information visible
  3. No privacy, cookie, or terms of service policies found
  4. No forms or data collection fields detected
  5. No social media or external business links found except Cloudflare domains
  6. No metadata or structured data present
  7. No visible company branding or logo
  8. WHOIS data unavailable or domain not found in WHOIS database
  9. Security headers include Content-Security-Policy
  10. Website uses Cloudflare Turnstile captcha for bot protection
Technical notes

Notes

The website is hosted behind Cloudflare, utilizing their security and bot mitigation services including Turnstile captcha. The HTML content is minimal and serves only as a security verification page. No CMS or additional frameworks are detected. The site uses modern HTML5 and CSS3 standards with a Content-Security-Policy header. Performance and mobile optimization cannot be assessed due to blocked content. The technical infrastructure appears focused on security perimeter controls but lacks visible content delivery or user engagement features.
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 rose365.net. 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 rose365.net.

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.