Skip to main content

Security report for yandex.kz

Яндекс · Technology · Kazakhstan

Low risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

78/100

Risk levelLow

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

Yandex.kz is a regional internet search engine portal operated by Yandex, a leading technology company in Russia and CIS countries. The site offers comprehensive search services including web, image, music, and product search, supporting multiple input methods such as text, voice, and image-based queries. It targets a broad general audience in Kazakhstan and surrounding regions, positioning itself as a primary gateway to internet resources. The business model centers on advertising and platform services, leveraging Yandex's extensive technology infrastructure. Technically, the website employs modern JavaScript frameworks and performance monitoring tools, including Yandex's proprietary Real User Monitoring (Ya.Rum) and Yandex Metrika analytics. The site is hosted on Yandex's infrastructure with fast loading times and good mobile optimization. Accessibility and SEO practices are well implemented, contributing to a high-quality user experience. From a security perspective, the site uses HTTPS with strong SSL configurations and implements error monitoring and logging. However, explicit privacy and cookie policies are not found in the provided content, and no direct contact channels for security incidents are visible. Security headers are minimal but present. There are no detected vulnerabilities or suspicious patterns, indicating a mature security posture but with room for improvement in transparency and compliance documentation. Overall, Yandex.kz is a professional, trustworthy, and technically advanced website serving as a key internet search portal in Kazakhstan. Strategic recommendations include publishing clear privacy and cookie policies, providing security incident contact information, and enhancing security headers to further strengthen compliance and user trust.

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

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

    • 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. 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching yandex.kz

This scan found 13 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. See sample alerts.

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
70
Security headers
75
Email security
90
DNS health
85
Network security
100
GDPR outside view
50
Average
78

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

Yandex.kz operates as a regional branch of Yandex N.V., a major technology company specializing in internet search and related services. The site leverages Yandex's brand and technology to serve the Kazakhstani market, offering localized content and language options. Its competitive advantage lies in its comprehensive search capabilities, integration of voice and image search, and strong brand recognition. Revenue streams primarily come from advertising and platform services. The target customers are general internet users in Kazakhstan and Russian-speaking populations. The company shows indicators of growth and digital maturity, supported by a robust partnership ecosystem within Yandex's corporate structure. Operationally, the site maintains high standards of content quality and user experience, reinforcing its market position.

Security posture

The security maturity of Yandex.kz is solid, with HTTPS enforced and SSL configured to a high standard. The site employs advanced client-side monitoring for performance and error tracking, indicating proactive security and reliability management. However, the absence of explicit privacy and cookie policies, as well as lack of visible incident response contacts, suggests gaps in compliance and transparency. No vulnerable libraries or exposed sensitive data were detected in the analyzed content. The site would benefit from implementing a security.txt file and enhancing HTTP security headers such as Content Security Policy and HSTS. Overall, the security posture is strong but could be improved to meet best practices and regulatory requirements fully.

Recommendations

  1. Publish comprehensive privacy and cookie policies accessible from the homepage.
  2. Implement a cookie consent mechanism to comply with GDPR and similar regulations.
  3. Provide clear contact information for security incidents, including dedicated security and abuse email addresses.
  4. Add a security.txt file to facilitate vulnerability disclosure and improve transparency.
  5. Enhance HTTP security headers with CSP, HSTS, and X-Frame-Options to mitigate common web attacks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Яндекс
Description
Яндекс предоставляет интернет-поиск, включая сайты, изображения, музыку, товары, и помогает решать задачи от повседневных вопросов до научной работы. Поиск возможен текстом, голосом или по картинке.
Key services
Internet search, Image search, Music search, Product search, Voice search, Image-based search
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, IntersectionObserver, PerformanceObserver, XMLHttpRequest, Beacon API, Web Vitals monitoring
Frameworks
React (implied by react.inited event), Ya.Rum (Yandex Real User Monitoring)
Platforms
Desktop web
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of Content Security Policy scripts (implied by script nonce)
  • Real User Monitoring for performance and error tracking
  • Error logging and throttling implemented

Analytics and tracking

Services
Yandex Metrika
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
AdFox
Tracking pixels
Yandex Metrika
Marketing tools
Yandex Metrika, Yandex Real User Monitoring
Transparency
good

Site quality

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

Key observations

  1. Website is a major internet search engine localized for Kazakhstan.
  2. Content is fully accessible with no blocking or WAF challenges.
  3. No explicit privacy, cookie, or terms of service pages found in the provided HTML snapshot.
  4. Strong technical implementation with modern JavaScript and performance monitoring.
  5. Security practices are good but could be improved with explicit policies and security.txt.
  6. No direct contact information or security incident channels found in the HTML.
  7. Use of Yandex's own analytics and advertising platforms.
  8. Branding and content are consistent and professional.
Technical notes

Notes

The website demonstrates a modern and robust technical infrastructure, utilizing advanced JavaScript features, performance monitoring APIs, and Yandex's proprietary Real User Monitoring tools. The tech stack includes React and other contemporary web technologies, ensuring a responsive and fast user experience. Hosting is managed within Yandex's own infrastructure, providing reliability and scalability. The site is well-optimized for mobile devices and accessibility, with structured metadata and Open Graph tags supporting SEO. Technical debt appears minimal, and the architecture supports ongoing modernization and integration with Yandex's broader ecosystem. Potential risks include reliance on multiple third-party scripts which should be regularly audited for security.
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

Earlier scans of this domain

  1. 83/100Low17 findingsView report
Reviews of this site

Share your experience with yandex.kz. 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 yandex.kz.

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.