Skip to main content

Security report for ruptly.agency

Ruptly · Media · Russia

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

Security score

62/100

Risk levelMedium

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

Ruptly is a media agency specializing in video content distribution, targeting registered users who require access to their services. The website functions primarily as a login portal restricting access to authorized users, with contact provided via email for further inquiries. The business operates in the media sector and appears to be a medium-sized entity based in Russia, although the domain WHOIS data shows privacy protection and an anomalous future creation date, which raises some concerns about registration transparency. Technically, the website employs modern frontend technologies including React, service workers, and Cloudflare DNS hosting. It uses Yandex Metrika for analytics and tracking, indicating moderate user tracking practices. The site is mobile optimized and includes accessibility features, but SEO optimization and content richness are basic. The cookie consent mechanism is present and functional, though no privacy policy or terms of service are visible, which impacts compliance. From a security perspective, HTTPS is enforced and the domain status includes clientTransferProhibited, which are positive indicators. However, no DNSSEC is enabled, no security headers are detected, and there is no published security policy or incident response information. The domain's privacy protection and unusual creation date reduce trustworthiness somewhat. Overall, the security posture is moderate but could be improved with better transparency and security controls. The overall risk assessment suggests a functional but basic media content platform with moderate security and privacy compliance. Strategic recommendations include enabling DNSSEC, publishing privacy and security policies, adding security headers, and clarifying domain registration details to enhance trust and compliance.

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

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

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

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

Keep watching ruptly.agency

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
75
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
50
Average
62

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

Ruptly positions itself as a media content provider focusing on video services accessible to registered users. Its business model appears to be subscription or registration-based access to proprietary media content. The company targets media consumers and clients requiring video content services. The use of privacy protection in WHOIS and Cloudflare DNS suggests a focus on operational security and privacy. However, the domain's future creation date is inconsistent with typical business timelines, which may indicate recent or placeholder registration. The lack of visible social media presence or phone contact limits direct customer engagement channels. The company likely generates revenue through media licensing or subscription fees. The partnership ecosystem is not evident from the data, and no subsidiaries or parent companies are identified. The website branding is consistent but content quality is basic, indicating room for growth in digital maturity and market presence.

Security posture

The website enforces HTTPS and uses clientTransferProhibited domain status, which are positive security indicators. The use of Cloudflare DNS and service workers demonstrates modern infrastructure adoption. However, the absence of DNSSEC and security headers such as Content-Security-Policy or X-Content-Type-Options weakens the security posture. No security policy or incident response contacts are published, limiting transparency and preparedness. The site collects user credentials via a login form but does not show explicit security measures like multi-factor authentication or CAPTCHA. Analytics via Yandex Metrika introduces moderate user tracking, which should be balanced with privacy compliance. The domain WHOIS privacy protection is justified but the anomalous creation date reduces trust. Overall, the security maturity is moderate with room for improvement in policy publication, header implementation, and domain security.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and terms of service to improve compliance and user trust.
  3. Implement security headers such as Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security.
  4. Provide clear incident response contact information and consider publishing a security.txt file.
  5. Clarify domain registration details and correct the anomalous creation date to enhance legitimacy and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ruptly
Description
Ruptly is a media agency providing video content services, targeting registered users who require access to their content. The site restricts access to registered users and offers contact via email for further information.
Key services
Video content distribution, Media services
Content quality
basic
Branding
consistent

Technology

Stack
React, Cloudflare DNS, Yandex Metrika, Service Worker, Modernizr
Frameworks
React
Performance
moderate
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • clientTransferProhibited domain status
  • Service worker registration

Analytics and tracking

Services
Yandex Metrika
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Yandex Metrika
Marketing tools
Yandex Metrika
Transparency
basic

Site quality

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

Key observations

  1. Website is a login page restricting access to registered users
  2. No privacy policy or terms of service found on the page
  3. Cookie consent banner present with acceptance and settings options
  4. Contact email provided for service inquiries
  5. No phone numbers or physical addresses found
  6. No social media links detected
  7. Modern frontend technologies used (React, service workers)
  8. Yandex Metrika used for analytics and tracking
  9. No explicit security policy or incident response information published
  10. No visible security headers detected in HTML content
Technical notes

Notes

The website uses a modern React-based frontend with service worker support for enhanced performance and offline capabilities. Hosting is via Cloudflare DNS, providing resilience and DDoS protection. Yandex Metrika is integrated for analytics, indicating moderate tracking. The site is mobile optimized and includes accessibility features such as skip links. However, SEO optimization is basic with minimal meta tags and no Open Graph or JSON-LD structured data detected. The login form collects email and password with autocomplete disabled for security. No CMS is detected, suggesting a custom or proprietary platform. Performance is moderate with preloading of CSS and JS assets. Technical debt appears low but could be improved with enhanced SEO and security header implementation.
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 ruptly.agency. 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 ruptly.agency.

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.