# Yandex Security Rating, Vendor Risk Report, and Data Breaches

> This is a plain-markdown summary of [https://www.upguard.com/security-report/yandex](https://www.upguard.com/security-report/yandex), generated for AI agents and LLMs. Security scores and check results reflect UpGuard's independent analysis and are kept in sync with the source page. Visit the source URL for the full interactive report.

Yandex operates a search engine and provides internet-related services and products in Russia and neighboring regions. The company offers email, maps, navigation, cloud storage, music streaming, and ride-hailing services through its web platform and mobile applications.

## Overview
- Domain: yandex.ru
- Grade: B (Good)
- Score: 666 / 950
- Last scan: August 18, 2026
- Industry: Tech
- Website: https://www.yandex.ru
- Employees: 2k+
- Location: Moscow, Russia
- CEO: Arkady Volozh

## Vendor risk summary
This vendor risk report is based on UpGuard's continuous monitoring of Yandex's security posture using open-source, commercial, and proprietary threat intelligence feeds. The results are summarized into a security rating based on the analysis of hundreds of individual checks across five risk categories: website security, email security, phishing & malware, brand & reputation risk, and network security.

## Security categories

### Website Security

- Fail — HttpOnly cookies not used
  - When HttpOnly cookies are not used, the cookies can be accessed on the client, which enables certain type of client-side attacks. The website configuration should be changed to enforce HttpOnly cookies.
- Pass — Secure cookies used
  - Using secure cookies reduces the risk of third parties intercepting information contained in these cookies.
- Pass — Server information header not exposed
  - Ensuring the server information header is not exposed reduces the ability of attackers to exploit certain vulnerabilities.
- Pass — X-Powered-By header not exposed
  - Information about specific technology used on the server is obscured.
- Pass — Referrer policy is not unsafe-url
  - The website's Referrer Policy is not configured to allow unsafe information to be sent in the referrer header.
- Pass — ASP.NET version header not exposing specific ASP.net version
  - Ensuring the ASP.NET version header is not exposing a specific version makes it harder for attackers to exploit certain vulnerabilities.
- Pass — ASP.NET version header not exposed
  - Ensuring the ASP.NET version header is not exposed makes it harder for attackers to exploit certain vulnerabilities.
- Pass — No unmaintained page detected
  - The page appears to be maintained.

### Email

- Fail — DMARC policy is p=none
  - DMARC policy is p=none. This provides no protection against fraudulent emails. The DMARC policy should be migrated to p=quarantine, and eventually p=reject.
- Fail — SPF policy uses ~all
  - Sender Policy Framework (SPF) record is too lenient as to which domains are allowed to send email on the domain's behalf. This record should preferably not use the ~all mechanism, as this does not instruct the mail receiver to reject messages from unauthorised sources. When DMARC is not being enforced, -all should be used on the SPF record.
- Pass — DMARC policy exists
  - DMARC protects against fraudulent emails being sent from a domain.
- Pass — SPF enabled
  - Sender Policy Framework (SPF) records prevent spammers from sending messages with forged addresses.
- Pass — SPF syntax correct
  - Sender Policy Framework (SPF) record passes basic syntax checks.
- Pass — SPF ptr mechanism not used
  - Sender Policy Framework (SPF) record does not include the ptr mechanism.

### Network

- Pass — No ports are open
  - No open ports were detected.

### DNS

- Fail — DNSSEC not enabled
  - DNSSEC records prevent third parties from forging the records that guarantee a domain's identity. DNSSEC should be configured for this domain.
- Fail — CAA not enabled
  - The domain does not contain a valid Certification Authority Authorization (CAA) record. A CAA record indicates which Certificate Authorities (CAs) are authorized to issue certificates for a domain.
- Pass — No unregistered MX records detected
  - No unregistered MX records that could lead to receiving mail on behalf of the target organization were detected.

### Encryption

- Fail — HTTP Strict Transport Security (HSTS) not enforced
  - Without HSTS enforced, people browsing this site are more susceptible to man-in-the-middle attacks. The server should be configured to support HSTS.
- Fail — Weak cipher suites supported in TLS 1.2
  - Weak cipher suites can potentially be broken by a well resourced attacker, and should not be supported by the server unless very old devices or browsers must be supported.
- Pass — Certificate not found on our revoked certificate list
  - The site's certificate chain was checked against our list of revoked certificates.
- Pass — SSL available
  - SSL is supported for this site.
- Pass — HTTP requests are redirected to HTTPS
  - All HTTP requests are redirected to HTTPS.
- Pass — Hostname matches SSL certificate
  - The site's hostname matches the SSL certificate.
- Pass — SSL has not expired
  - SSL certificate has not expired.
- Pass — Trusted SSL certificate
  - The certificate presented by this domain was issued by a trusted certificate authority.
- Pass — No insecure SSL/TLS versions available
  - No insecure SSL/TLS versions are available for this site.
- Pass — SSL certificate chain present in server response
  - A complete SSL certificate chain was presented by the server for this domain.
- Pass — SSL chain certificates do not expire within 20 days
  - SSL intermediate and root certificates do not expire within 20 days.
- Pass — SSL expiration period shorter than 398 days
  - The SSL certificate presented by the server has an expiration period shorter than 398 days.
- Pass — SSL has more than 20% of its valid period remaining
  - SSL certificate does not expire in less than 20% of its total valid period.
- Pass — Strong SSL algorithm
  - Industry standard SHA-256 encryption in use.
- Pass — Strong public certificate key length
  - The site's public certificate provides at least 112 bits of security strength.

### Data leakage

- Pass — No infostealer malware detected
  - Our scans have not found any evidence of infostealer malware infections associated with this organisation's domain.

### IP/Domain Reputation

- Fail — Suspected phishing site
  - This IP/domain has been reported as a phishing site in the last 30 days. The server should be checked and any offending software removed.
- Pass — No reports of botnet activity in the last 30 days
  - This IP/domain has not been reported as a source of botnet activity in the last 30 days.
- Pass — No reports of brute force login attempts in the last 30 days
  - This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 30 days.
- Pass — No reports of malware distribution in the last 30 days
  - This IP/domain has been reported for distributing malware in the last 30 days.
- Pass — No reports of unsolicited scanning in the last 30 days
  - This IP/domain has not been reported for performing unsolicited scanning in the last 30 days.
- Pass — No reports of botnet activity in the last 90 days
  - This IP/domain has not been reported as a source of botnet activity in the last 90 days.
- Pass — No reports of brute force login attempts in the last 90 days
  - This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 90 days.
- Pass — No reports of malware distribution in the last 90 days
  - This IP/domain has been reported for distributing malware in the last 90 days.
- Pass — No reports of unsolicited scanning in the last 90 days
  - This IP/domain has not been reported for performing unsolicited scanning in the last 90 days.

### Vulnerability Management

- Pass — Not vulnerable to CVE-2014-0160 (Heartbleed)
  - A bug in OpenSSL's implementation of the TLS heartbeat extension allows access to portions of memory on the targeted host e.g. cryptographic keys and passwords.
- Pass — Not vulnerable to CVE-2014-3566 (POODLE)
  - The server does not support SSLv3, and is not vulnerable to the POODLE attack.
- Pass — Not vulnerable to CVE-2015-0204 (FREAK)
  - The server does not offer RSA_EXPORT cipher suites, so clients are not vulnerable to the FREAK attack.
- Pass — Not vulnerable to CVE-2015-4000 (Logjam)
  - The server is using strong Diffie-Hellman parameters and is not vulnerable to the Logjam attack.

---
Full interactive report: https://www.upguard.com/security-report/yandex
Security Reports Policy: https://www.upguard.com/security-report-policy
