Skip to main content

Security report for yandex.kz

Яндекс · Technology · Kazakhstan

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

Security score

83/100

Risk levelLow

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

Yandex.kz is a regional domain of Yandex, a leading technology company specializing in internet search and related services primarily in Russia and CIS countries. The website offers a comprehensive search engine platform supporting text, voice, and image search, targeting a broad general audience. The site is well-branded, professionally designed, and optimized for desktop platforms with good performance and accessibility features. Technically, it leverages modern JavaScript technologies, including React and performance monitoring APIs, hosted on Yandex's own infrastructure. Security posture is strong with HTTPS enforced and internal analytics for error and performance monitoring, though explicit security policies and incident response contacts are not publicly visible. Privacy compliance indicators such as privacy and cookie policies are not detected in the provided content, representing an area for improvement. Overall, the domain registration and website content are consistent and legitimate, reflecting a mature enterprise-level digital presence.

Scanned

This is an earlier scan of yandex.kz. View the latest report

NIS2 and GDPR posture

GDPR outside view
65/ 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

3 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 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 11 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
80
Security headers
75
Email security
90
DNS health
85
Network security
100
GDPR outside view
65
Average
83

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 operates as a major player in the technology sector, focusing on internet search and digital services. The business model revolves around providing search and related services, monetized likely through advertising and partnerships. The target market includes internet users in Kazakhstan and surrounding regions, leveraging localized domains and language support. The company maintains a strong brand presence with consistent design and trust signals. While no explicit contact or compliance information is found in the analyzed content, the domain age and WHOIS data support a credible and established business entity. The ecosystem includes multiple regional domains and services, indicating a broad partnership and subsidiary network.

Security posture

The website demonstrates a good security posture with HTTPS enabled and use of modern web security practices such as referrer policies and internal error reporting. However, the absence of explicit security policies, vulnerability disclosure programs, and incident response contacts limits transparency and readiness perception. No vulnerabilities or exposed sensitive data were detected in the content. The internal analytics system (Ya.Rum) indicates active monitoring of performance and errors, which supports proactive security management. To enhance security maturity, publishing formal security policies and contact channels for security incidents is recommended.

Recommendations

  1. Publish clear and accessible privacy and cookie policies to improve compliance and user trust.
  2. Implement and disclose a formal security policy and incident response contact information.
  3. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Add security headers such as Content Security Policy (CSP) and HTTP Strict Transport Security (HSTS) explicitly.
  5. Enhance transparency around data collection and retention practices to align with GDPR and other regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Яндекс
Description
Яндекс предоставляет интернет search services including websites, images, music, and goods search. It supports text, voice, and image search to solve everyday and scientific tasks.
Key services
Internet search, Image search, Music search, Product search, Voice search
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, IntersectionObserver, PerformanceObserver, XMLHttpRequest, Beacon API
Frameworks
React (implied by react.inited event)
Platforms
Desktop
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of CSP and referrer policy implied by meta tags

Analytics and tracking

Services
Ya.Rum (Yandex internal)
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Ya.Rum (Yandex internal analytics)
Marketing tools
Yandex internal analytics and error reporting
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible and not blocked by WAF or security challenges
  2. No explicit privacy, cookie, or terms of service pages detected in the provided HTML snippet
  3. Strong use of internal analytics and error reporting scripts
  4. No direct contact information or security incident contacts found in the HTML
  5. Website uses modern web technologies and good performance optimizations
  6. Content is professional, relevant, and targeted at a general audience
Technical notes

Notes

The website uses a modern tech stack with JavaScript frameworks (React implied), performance monitoring via PerformanceObserver and IntersectionObserver APIs, and advanced error reporting mechanisms. Hosting is managed by Yandex's own infrastructure, ensuring reliable and fast delivery. The site is optimized for desktop with responsive design considerations and accessibility features. SEO is supported by comprehensive meta tags and Open Graph data. There is no evidence of legacy or vulnerable libraries. Technical debt appears low, but opportunities exist to improve security header implementation and privacy compliance disclosures.
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. 78/100Low19 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.