Skip to main content

Security report for rifetheme.com

Other · N/a

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

67/100

Risk levelMedium

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

The website at apollo13themes.com/rife/ is currently inaccessible beyond a security verification page that employs Google reCAPTCHA invisible to prevent automated access. This indicates the presence of a Web Application Firewall or similar bot protection mechanism, which blocks direct content retrieval and analysis. The domain is registered with Tucows Domains Inc. since 2016, showing a stable and legitimate registration history. However, the lack of visible business information, privacy policies, or contact details on the accessible page limits the ability to assess the company's market position or services. Technically, the site uses Bootstrap 5.3.3 and Google reCAPTCHA v3, but lacks DNSSEC and visible security headers, which are areas for improvement. Overall, the security posture is moderate due to bot protection but lacks transparency and compliance indicators.

Scanned

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

6 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 rifetheme.com

This scan found 22 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
95
Security headers
15
Email security
70
DNS health
70
Network security
100
GDPR outside view
50
Average
67

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 rifetheme.com, from OffSeq Breach.

No leaked records found

Breach holds no records for rifetheme.com 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

Due to the content being blocked by a security verification page, no direct business information, such as company name, services, or market positioning, is available. The domain name suggests a theme provider business, likely targeting web developers or designers. The domain age and registration status support legitimacy, but no further business intelligence can be extracted from the current page.

Security posture

The site employs Google reCAPTCHA v3 invisible as a bot mitigation measure, which is a positive security control. However, the absence of DNSSEC, security headers, and visible privacy or security policies reduces overall security maturity. The domain registration status with clientTransferProhibited and clientUpdateProhibited flags adds protection against unauthorized changes. No incident response or vulnerability disclosure information is available, indicating potential gaps in security transparency.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security.
  2. Implement and publish comprehensive privacy and cookie policies to improve compliance and user trust.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the website.
  4. Provide clear contact information and incident response channels to improve transparency and support.
  5. Review and optimize SSL/TLS configuration to ensure strong encryption and HTTPS enforcement.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Page is a security verification challenge with Google reCAPTCHA invisible and a loading spinner, indicating a WAF or bot protection mechanism blocking direct access to content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Bootstrap 5.3.3, Google reCAPTCHA v3
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
40/100
Good practices seen
  • Use of Google reCAPTCHA v3 invisible for bot protection

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Google reCAPTCHA
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 behind a security verification page using Google reCAPTCHA invisible.
  2. No visible business or contact information on the page.
  3. No privacy, cookie, or terms of service policies found on this page.
  4. No email addresses, phone numbers, or social media links detected.
  5. Technical stack includes Bootstrap 5.3.3 and Google reCAPTCHA v3.
  6. Domain WHOIS data shows a stable registration with Tucows Domains Inc., created in 2016 and expiring in 2026.
  7. DNSSEC is not enabled, which is a security improvement opportunity.
  8. No security headers detected in the provided HTML content.
  9. Page is likely a bot protection gate, preventing full content analysis.
Technical notes

Notes

The website uses modern front-end technology with Bootstrap 5.3.3 and integrates Google reCAPTCHA v3 for bot protection. Hosting appears to be managed via StackDNS based on nameservers. The page content is minimal and serves as a security gate rather than a full website, limiting performance and SEO analysis. Mobile optimization and accessibility are basic due to the minimal content. No CMS or backend platform is identifiable from the provided data. The lack of DNSSEC and security headers indicates technical debt in security best practices.
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 rifetheme.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 rifetheme.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.