Skip to main content

Security report for bits.media

bits.media · Finance · Russia

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

64/100

Risk levelMedium

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

Bits.media is a Russian-language media platform specializing in cryptocurrency, blockchain, and DeFi news and analysis. It offers a variety of services including news updates, mining reviews, price tracking, calculators, and a forum for community engagement. The site targets Russian-speaking crypto enthusiasts, investors, and professionals, positioning itself as a reputable source of crypto-related information in the region. Technically, the website is built on the Bitrix CMS platform, utilizing modern JavaScript libraries and analytics tools such as Google Analytics and Yandex Metrica. The site is mobile-optimized and features a professional design with clear navigation. Security-wise, the site enforces HTTPS and uses CAPTCHA on subscription forms but lacks some recommended security headers and explicit privacy and cookie policies. The WHOIS data is incomplete due to TLD restrictions, which slightly reduces domain trustworthiness. Overall, the website demonstrates a solid business and technical foundation with room for improvement in privacy compliance and security best practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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. 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 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

    • 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

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

Keep watching bits.media

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
49
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
35
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

Bits.media operates as an important entity within the finance and technology sectors, focusing on cryptocurrency and blockchain media. Its business model revolves around content provision, advertising, and community engagement through forums and tools. The platform maintains partnerships with various crypto-related service providers and event organizers, enhancing its ecosystem. The site’s consistent content updates and active social media presence indicate a stable user base and growth potential. Revenue streams likely include advertising, sponsored content, and affiliate partnerships. The absence of detailed company registration data suggests a need for enhanced transparency to boost business credibility further.

Security posture

The website maintains a moderate security posture with HTTPS enabled and no visible exposure of sensitive data. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options is a gap that could be exploited. The lack of published security policies and incident response contacts limits transparency and preparedness for security incidents. The use of third-party analytics and advertising scripts introduces potential risks that require regular auditing. No critical vulnerabilities were detected in the visible content. Enhancing security headers, publishing security policies, and implementing comprehensive privacy and cookie policies would significantly improve the security maturity of the platform.

Recommendations

  1. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Publish clear and comprehensive privacy and cookie policies with user consent mechanisms to comply with GDPR and other privacy regulations.
  3. Establish and publicize an incident response plan and vulnerability disclosure policy to improve transparency and security readiness.
  4. Regularly audit third-party scripts and dependencies to identify and mitigate potential vulnerabilities.
  5. Enhance WHOIS transparency or provide additional company registration information on the website to improve trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
bits.media
Description
Новости криптовалют, финтеха, блокчейна, майнинга, DeFi. Обзоры майнеров, курсы биткоина, форков и альткоинов, калькулятор биткоин.
Key services
Cryptocurrency news, Mining reviews, Price tracking, Calculators, Forums, Advertising services
Content quality
good
Branding
consistent

Technology

Stack
Bitrix CMS, jQuery, Google Tag Manager, Google Analytics, Yandex Metrica, LazyLoad JS, Dexie.js
Frameworks
Bitrix Framework
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of CAPTCHA in subscription form

Analytics and tracking

Services
Google Analytics, Yandex Metrica
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Yandex Metrica
Marketing tools
Yandex Metrica
Transparency
basic

Site quality

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

Key observations

  1. Website is a Russian-language cryptocurrency news and information portal.
  2. Content is rich, regularly updated, and professionally presented.
  3. No privacy or cookie policies are explicitly found on the site.
  4. WHOIS data is unavailable or unsupported for this TLD, limiting domain trust analysis.
  5. No security headers detected in the HTML source; HTTPS is used.
  6. Multiple external tracking and analytics services are used.
  7. Contact emails use the site domain, indicating legitimate contact points.
  8. No phone numbers or physical addresses found.
  9. No evidence of adult or unsafe content.
  10. Advertising banners and partner links are present but appear relevant to the crypto industry.
Technical notes

Notes

The website is built on the Bitrix CMS platform, leveraging modern JavaScript libraries such as jQuery and Dexie.js for client-side functionality. It integrates Google Tag Manager, Google Analytics, and Yandex Metrica for analytics and user tracking. The site uses lazy loading for images to improve performance and is mobile-optimized with responsive design elements. While the technical stack is modern and functional, the absence of some security headers and privacy compliance features indicates technical debt in security and compliance areas. Performance is moderate, with opportunities to optimize loading times further. Accessibility features are basic, suggesting room for improvement to meet higher standards.
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 bits.media. 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 bits.media.

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.