Hardenize Report: yandex.com

Web Security Overview

HTTPS

Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) is an HTTPS extension that instructs browsers to remember sites that use encryption and enforce strict security requirements. Without HSTS, active network attacks are easy to carry out.

For important sites VERY IMPORTANT medium EFFORT

HSTS Preloaded

HSTS Preloading is informing browsers in advance about a site's use of HSTS, which means that strict security can be enforced even on the first visit. This approach provides best HTTPS security available today.

For important sites VERY IMPORTANT medium EFFORT

Content Security Policy

Content Security Policy (CSP) is an additional security layer that enables web sites to control browser behavior, creating a safety net that can counter attacks such as cross-site scripting.

For important sites IMPORTANT high EFFORT

Email Security Overview

STARTTLS

All hosts that receive email need encryption to ensure confidentiality of email messages. Email servers thus need to support STARTTLS, as well as provide decent TLS configuration and correct certificates.

For all sites VERY IMPORTANT low EFFORT

SPF

Sender Policy Framework (SPF) enables organizations to designate servers that are allowed to send email messages on their behalf. With SPF in place, spam is easier to identify.

For important sites IMPORTANT low EFFORT

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism that allows organizations to specify how unauthenticated email (identified using SPF and DKIM) should be handled.
There are issues with this site's DMARC configuration.

For important sites IMPORTANT low EFFORT

DNS Zone

The global DNS infrastructure is organized as a series of hierarchical DNS zones. The root zone hosts a number of global and country TLDs, which in turn host further zones that are delegated to their customers. Each organization that controls a zone can delegate parts of its namespace to other zones. In this test we perform detailed inspection of a DNS zone, but only if the host being tested matches the zone.

Test passed

Everything seems to be well configured. Well done.

Nameserver Names

Nameservers can be referred to by name and by address. In this section we show the names, which can appear in the NS records, the referrals from the parent zone, and the SOA record. In some situations, servers from the parent zone respond authoritatively, in which case we will include them in the list as well.

Nameserver	Operational	IPv4	IPv6	Sources
ns1.yandex.net. 213.180.193.1 2a02:6b8::1				NS REFERRAL
ns1.yandex.ru. STEALTH PRIMARY 213.180.193.1 2a02:6b8::1				SOA
ns2.yandex.net. 93.158.134.1 2a02:6b8:0:1::1				NS REFERRAL

Nameserver Addresses

This section shows the configuration of all discovered nameservers by their IP address. To find all applicable nameservers, we inspect the parent zone nameservers for names and glue and then the tested zone nameservers for NS records. We then resolve all discovered names to IP addresses. Finally, we test each address individually.

Nameserver	Sources	Payload Size
213.180.193.1 PRIMARY ns1.yandex.ru. ns1.yandex.net. PTR: ns1.yandex.net.	NAME	4096
93.158.134.1 ns2.yandex.net. PTR: ns2.yandex.net.	NAME	4096
2a02:6b8:0:1::1 ns2.yandex.net. PTR: ns2.yandex.net.	NAME	4096
2a02:6b8::1 PRIMARY ns1.yandex.ru. ns1.yandex.net. PTR: ns1.yandex.net.	NAME	4096

Start of Authority (SOA) Record

Start of Authority (SOA) records contain administrative information pertaining to one DNS zone, especially the configuration that's used for zone transfers between the primary nameserver and the secondaries. Only one SOA record should exist, with all nameservers providing the same information.

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	ns1.yandex.ru.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	sysadmin.yandex.ru.
Zone serial or version number.Serial number	2023041993
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	3,600 seconds (about 1 hour)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	900 seconds (about 15 minutes)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval	2,592,000 seconds (about 30 days)
TTL for purposes of negative response caching. Negative cache TTL	900 seconds (about 15 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	3,600 seconds (about 1 hour)

Analysis

No problems detected with the zone configuration

Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

Below are all DNS queries we submitted during the zone inspection.

	ID	Server	Transport	Question Name	Type	Status

DNS Records

Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.

Test passed

Everything seems to be well configured. Well done.

DNS Records

These are the results of individual DNS queries against your nameserver for common resource record types.

Name	TTL	Type	Data
yandex.com.	600	A	5.255.255.77
yandex.com.	600	A	77.88.55.88
yandex.com.	600	A	77.88.44.55
www.yandex.com.	600	CNAME	yandex.com.
yandex.com.	1200	AAAA	2a02:6b8:a:0:0:0:0:a
yandex.com.	3600	CAA	0 issuewild "globalsign.com"
yandex.com.	3600	CAA	0 issue "globalsign.com"
yandex.com.	1200	MX	10 mx.yandex.ru.
yandex.com.	172800	NS	ns1.yandex.net.
yandex.com.	172800	NS	ns2.yandex.net.
yandex.com.	3600	SOA	ns1.yandex.ru. sysadmin.yandex.ru. 2023041993 3600 900 2592000 900
_sip._tls.yandex.com.	600	CNAME	any.yandex.ru.
_sipfederationtls._tcp.yandex.com.	600	CNAME	any.yandex.ru.
_xmpp-client._tcp.yandex.com.	86400	SRV	5 0 5222 xmpp.yandex.ru.
_xmpp-server._tcp.yandex.com.	86400	SRV	5 0 5269 xmpp.yandex.ru.
yandex.com.	1200	TXT	"google-site-verification=FVk3gum7zZLdkqi96ypScROFMew0wMetq1Gpu4rkzPI"
yandex.com.	1200	TXT	"_globalsign-domain-verification=c_B4BykwG18xfpQp0gUTKLpY-KRJ7eiLQGHK4wlBwL"
yandex.com.	1200	TXT	"v=spf1 redirect=_spf.yandex.ru"
yandex.com.	1200	TXT	"5849d1f0fc8a9e73d82dfed9f2c33931"
yandex.com.	1200	TXT	"facebook-domain-verification=625igbkehyfptcek6nh1hz7q4s3h4a"
yandex.com.	1200	TXT	"facebook-domain-verification=gy3xj2e9mxu0vtcdgqcznoaxoaiv63"
_dmarc.yandex.com.	3600	TXT	"v=DMARC1; p=none; fo=1; rua=mailto:dmarc_agg@auth.returnpath.net,mailto:dmarc-rua@yandex.ru; ruf=mailto:dmarc_afrf@auth.returnpath.net"
_mta-sts.yandex.com.	600	CNAME	any.yandex.ru.
_smtp._tls.yandex.com.	600	CNAME	any.yandex.ru.

Backing DNS Queries

Below are all DNS queries we submitted while inspecting the resource records.

	ID	Server	Question Name	Type	Status

DNSSEC

DNSSEC is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses; it's intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice. DNSSEC is controversial, with the industry split largely between those who think it's essential and those who believe that it's problematic and unnecessary.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Useful DNSSEC Tools

Certification Authority Authorization

CAA (RFC 8659) is a new standard that allows domain name owners to restrict which CAs are allowed to issue certificates for their domains. This can help to reduce the chance of misissuance, either accidentally or maliciously. In September 2017, CAA became mandatory for CAs to implement.

Test passed

Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host	yandex.com
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	globalsign.com flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	globalsign.com flags: 0

Analysis

Issuance of S/MIME certificates not restricted

This policy doesn't restrict the issuance of S/MIME certificates. Consider using the `issuemail` directive to restrict which CAs, if any, can issue.

Issuance of BIMI not restricted

This policy doesn't restrict issuance of BIMI certificates. Consider using the `issuevmc` directive to restrict which CAs, if any, can issue.

CAA policy restricts issuance

Great. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.

Policy doesn't use reporting

This policy doesn't use reporting, which means that there is no way to contact you when a violation is detected. The CAA RFC defines the iodef property that can be used for this purpose. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

An internet hostname can be served by zero or more mail servers, as specified by MX (mail exchange) DNS resource records. Each server can further resolve to multiple IP addresses, for example to handle IPv4 and IPv6 clients. Thus, in practice, hosts that wish to receive email reliably are supported by many endpoint.

Test passed

Everything seems to be well configured. Well done.

Server

Preference

Operational

STARTTLS

TLS

PKI

DNSSEC

DANE

mx.yandex.ru
77.88.21.249
PTR: mxfront.stable.qloud-b.yandex.net

10

Analysis

Limited testing of third-party SMTP servers

We employ limited testing of third-party SMTP servers because they tend to be used by a great many domain names. Because we also continuously test a great many domain names, we want to avoid sending too many near-identical connections to these SMTP servers. It doesn't serve a practical purpose and also tends to get us on their bad side. TLS protocol testing, in particular, requires a lot of connections, which mean that we're often treated like spammers, even though we don't send any email. When testing third-party servers we may check only IP address per SMTP destination. When this is the case, the list of IP addresses shown here may not be complete. Further, in some situations with top services, we may show only the TLS configuration from a representative sample of their servers.

Some SMTP server assessments contain partial information

Comprehensive TLS assessments require many connections, which is exactly what many SMTP servers don't like. We implement a two-tier assessment approach. To give you some results as fast as possible, we perform shallow assessments that use only one connection per SMTP server. We then have a background process that performs complete assessments slowly, trying to accommodate each server individually. The results presented here contain partial information. If you come back later we may be able to provide complete assessment results.

Email TLS (SMTP)

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: mx.yandex.ru (77.88.21.249)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp256r1 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits)

Analysis

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Partial results shown

SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.

Relaxed TLS assessment criteria applied to SMTP on port 25

We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

Email Certificates (SMTP)

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed

Everything seems to be well configured. Well done.

Certificate #1

Leaf certificate

mx.yandex.ru
Issuer: GlobalSign nv-sa
Not Before: 28 Nov 2024 08:36:48 UTC
Not After: 28 May 2025 20:59:59 UTC (expires in 1 month 29 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mx.yandex.ru mx.yandex.net
Subject DN	CN=mx.yandex.ru, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	31295bab64bf5e0404a915572303b804ad7f37be
Serial	6349bd41b35c94cf522555c3
Not Before	28 Nov 2024 08:36:48 UTC
Not After	28 May 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Parent Certificate	http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
CRL	http://crl.globalsign.com/gsrsaovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gsrsaovsslca2018
Certificate Transparency
Signed Certificate Timestamps	28 Nov 2024 08:36:49 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 28 Nov 2024 08:36:49 UTC \| DigiCert Nessie2025 Log \| Qualified 28 Nov 2024 08:36:49 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	c217babd430dbca260f98788a59c47b91b641dc6
SHA256	677dcda67db1aaff757f2e38b5a4ff8358bfcc1338585d24ebd9ba71bba01d00
SPKI SHA256	84d3a69f1f342caebdeeffea8787c8027070afb23338c5723736205fa3631d56

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

mx.yandex.ru | 677dcda
Not After: 28 May 2025 20:59:59 UTC (expires in 1 month 29 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mx.yandex.ru mx.yandex.net
Subject DN	CN=mx.yandex.ru, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	31295bab64bf5e0404a915572303b804ad7f37be
Serial	6349bd41b35c94cf522555c3
Not Before	28 Nov 2024 08:36:48 UTC
Not After	28 May 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Parent Certificate	http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
CRL	http://crl.globalsign.com/gsrsaovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gsrsaovsslca2018
Certificate Transparency
Signed Certificate Timestamps	28 Nov 2024 08:36:49 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 28 Nov 2024 08:36:49 UTC \| DigiCert Nessie2025 Log \| Qualified 28 Nov 2024 08:36:49 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	c217babd430dbca260f98788a59c47b91b641dc6
SHA256	677dcda67db1aaff757f2e38b5a4ff8358bfcc1338585d24ebd9ba71bba01d00
SPKI SHA256	84d3a69f1f342caebdeeffea8787c8027070afb23338c5723736205fa3631d56

Intermediate certificate

GlobalSign RSA OV SSL CA 2018 | b676ffa
Not After: 21 Nov 2028 00:00:00 UTC (expires in 3 years 7 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Serial	1ee5f221dfc623bd4333a8557
Not Before	21 Nov 2018 00:00:00 UTC
Not After	21 Nov 2028 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
Certification Authority	GlobalSign nv-sa
Validation Type	Not Applicable
Authority Key Identifier	keyid:8ff04b7fa82e4524ae4d50fa639a8bdee2dd1bbc
CRL	http://crl.globalsign.com/root-r3.crl
OCSP	http://ocsp2.globalsign.com/rootr3
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	dfe83023062b997682708b4eab8e819aff5d9775
SHA256	b676ffa3179e8812093a1b5eafee876ae7a6aaf231078dad1bfb21cd2893764a
SPKI SHA256	8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05

Intermediate certificate

GlobalSign | 445eec7
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
Subject Key Identifier	8ff04b7fa82e4524ae4d50fa639a8bdee2dd1bbc
Serial	1ee5f169dff97352b6465d66a
Not Before	19 Sep 2018 00:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
CRL	http://crl.globalsign.com/root.crl
OCSP	http://ocsp.globalsign.com/rootr1
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	0bbfab97059595e8d1ec48e89eb8657c0e5aae71
SHA256	445eec78bc61215044a0379656aa2d5db5e42f76cb70b8d14c2077aa943d4ebb
SPKI SHA256	706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	40000000001154b5ac394
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	b1bc968bd4f49d622aa89a81f2150152a41d829c
SHA256	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Email DANE (SMTP)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SPF

Sender Policy Framework (SPF) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf. This simple mechanism can be used to reduce the effect of email spoofing and cut down on spam.

Test passed

Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location	yandex.com
SPF version used by this policy.v	spf1
This modifier is intended for consolidating both authorizations and policy into a common set to be shared within a single administrative domain. redirect	_spf.yandex.ru

Analysis

SPF policy found

Policy text: v=spf1 redirect=_spf.yandex.ru

Location: yandex.com

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy DNS lookups under limit

Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 3

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.yandex.ru
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf-ipv6.yandex.ru
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf-ipv4-yc.yandex.ru
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf-ipv6.yandex.ru
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a02:6b8:c00::/40
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a02:6b8:0:1472::/64
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a02:6b8:0:1619::/64
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a02:6b8:0:1a2d::/64
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a02:6b8:0:801::/64
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf-ipv4-yc.yandex.ru
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	178.154.239.80/28
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	178.154.239.72/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	178.154.239.144/28
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	178.154.239.136/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	178.154.239.208/28
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	178.154.239.200/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.250.56.16/28
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.250.56.80/28
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.250.56.144/28
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

Test failed

We've detected serious problems that require your immediate attention.

DMARC Policy Information

The location from which we obtained this policy.Policy location	_dmarc.yandex.com
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	none
Configures failure reporting.fo	1
Addresses to which aggregate feedback is to be sent.rua	mailto:dmarc_agg@auth.returnpath.net,mailto:dmarc-rua@yandex.ru
Addresses to which message-specific failure information is to be reported.ruf	mailto:dmarc_afrf@auth.returnpath.net

Analysis

DMARC policy found

Policy: v=DMARC1; p=none; fo=1; rua=mailto:dmarc_agg@auth.returnpath.net,mailto:dmarc-rua@yandex.ru; ruf=mailto:dmarc_afrf@auth.returnpath.net

Host: _dmarc.yandex.com

Valid external destination

Permission record location: yandex.com._report._dmarc.auth.returnpath.net

External destination: mailto:dmarc_agg@auth.returnpath.net

Permission record contents: v=DMARC1

Invalid external destination

This policy uses an external report destination that is not authorized because the permission record doesn't exist. Please refer to RFC 7489, Section 7.1, for instructions how to correct this problem.

Expected permission record location: yandex.com._report._dmarc.yandex.ru

External destination: mailto:dmarc-rua@yandex.ru

DMARC policy is invalid

Your DMARC policy is invalid.

MTA Strict Transport Security

SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SMTP TLS Reporting

SMTP TLS Reporting (RFC 8460), or TLS-RPT for short, describes a reporting mechanism and format by which systems sending email can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations. TLS-RPT can be used with DANE or MTA-STS.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

HTTP (80)

To observe your HTTP implementation, we submit a request to the homepage of your site on port 80, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

URL: http://yandex.com/

Analysis

HTTP connection failed

We were not able to successfully complete this request.

Message: Internal error

URL: http://www.yandex.com/

Analysis

HTTP connection failed

We were not able to successfully complete this request.

Message: Internal error

HTTP (443)

To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.

Test passed

Everything seems to be well configured. Well done.

URL: https://yandex.com/

1

https://yandex.com/

HTTP/1.1 200 Ok

Report-To	{ "group": "network-errors", "max_age": 100, "endpoints": [{"url": "https://dr.yandex.net/nel", "priority": 1}, {"url": "https://dr2.yandex.net/nel", "priority": 2}]}
Link	<https://yastatic.net/react/18.2.0/react-with-dom.min.js>; rel="preload"; as="script"; crossorigin="anonymous";
Link	<//yastatic.net/s3/frontend/yandex-int/mini-suggest/_/uzQeBecG.js>; rel="preload"; as="script"; crossorigin="anonymous";
Link	<https://yastatic.net/s3/home-static/_/nova/ac1b95cf7dbb1397eb35fbc4c132fce9bb855798c43182f09e97bc64c0ad94af.js>; rel="preload"; as="script"; crossorigin="anonymous";
Last-Modified	Sat, 29 Mar 2025 12:27:51 GMT
Reporting-Endpoints	default="https://yandex.com/portal/front/reports/?slots=912288%2C0%2C21&region=87&reqid=1743251271746343-10805090992510838290-balancer-l7leveler-kubr-yp-vla-41-BAL&dc=sas&page=desktop.global&enableOtherTypes=0"
Content-Security-Policy	img-src .verify.yandex.ru .ya.ru .yandex.ru ya.ru yabs.yandex.by yabs.yandex.kz yabs.yandex.ru yabs.yandex.uz yandex.ru yandex.com 'self' yastatic.net data: mc.admetrica.ru mc.yandex.com .mc.yandex.ru adstat.yandex.ru mc.yandex.ru favicon.yandex.net avatars.mds.yandex.net;script-src 'nonce-ICpjzF4ERry4fgPmeh0lNQ==' mc.yandex.com yastatic.net yandex.com mc.yandex.ru .mc.yandex.ru adstat.yandex.ru surveys.yandex.ru 'unsafe-eval';child-src .ya.ru .yandex.ru ya.ru yandex.ru mc.yandex.ru mc.yandex.md mc.yandex.com yandex.com .ya.ru .yandex.ru ya.ru yandex.ru;style-src 'unsafe-inline' yastatic.net;report-uri https://csp.yandex.net/csp?project=morda&from=morda.big.com&showid=1743251271746343-10805090992510838290-balancer-l7leveler-kubr-yp-vla-41-BAL&h=home-mordago-stable-web-backend-367.sas.yp-c.yandex.net&yandexuid=4108382901743251271&&version=2025-03-28-798&adb=0;media-src yastatic.net;connect-src .strm.yandex.net mc.yandex.com yandex.com yastatic.net yastat.net mc.yandex.ru .mc.yandex.ru adstat.yandex.ru mc.admetrica.ru surveys.yandex.ru .yandex.net an.yandex.ru yandex.ru;default-src 'self' yastatic.net yastat.net;font-src yastatic.net
Vary	Cookie,Accept-Language,Accept-Encoding
Cache-Control	no-cache,no-store,max-age=0,must-revalidate
X-Frame-Options	DENY
X-Yandex-Req-Id	1743251271746343-10805090992510838290-balancer-l7leveler-kubr-yp-vla-41-BAL
X-Content-Type-Options	nosniff
Expires	Sat, 29 Mar 2025 12:27:51 GMT
Set-Cookie	yandex_gid=87; Path=/; Domain=yandex.com; Expires=Mon, 28 Apr 2025 12:27:51 GMT; Secure; SameSite=None
Set-Cookie	yp=1745843271.ygu.1; Path=/; Domain=yandex.com; Expires=Tue, 27 Mar 2035 12:27:51 GMT; Secure; SameSite=None
Set-Cookie	yuidss=4108382901743251271; Path=/; Domain=yandex.com; Expires=Tue, 27 Mar 2035 12:27:51 GMT; Secure; SameSite=None
Set-Cookie	is_gdpr=0; Path=/; Domain=.yandex.com; Expires=Mon, 29 Mar 2027 12:27:51 GMT; SameSite=None; Secure
Set-Cookie	is_gdpr_b=CKKpXBDftwI=; Path=/; Domain=.yandex.com; Expires=Mon, 29 Mar 2027 12:27:51 GMT; SameSite=None; Secure
Set-Cookie	_yasc=lO90Ro1NVzgt9cks91DPQGJiGy/X6T9opO1k/ljc5H2VKkhI58HQQ2H/rKEX9DRpnDY=; domain=.yandex.com; path=/; expires=Tue, 27 Mar 2035 12:27:51 GMT; secure
Set-Cookie	i=M1bxftpBr+UPb10FL5pt7b+Xk4dYLZjMImzi5q+PsfPMpYAjJ3UMJIRw7U4IYYWZqPfUOkI8AYKfczYz1eGZBU2Ru5Y=; Expires=Mon, 29-Mar-2027 12:27:51 GMT; Domain=.yandex.com; Path=/; Secure; HttpOnly; SameSite=None
Set-Cookie	yandexuid=4108382901743251271; Expires=Mon, 29-Mar-2027 12:27:51 GMT; Domain=.yandex.com; Path=/; Secure; SameSite=None
Set-Cookie	yashr=7560396241743251271; Path=/; Domain=.yandex.com; Expires=Sun, 29 Mar 2026 12:27:51 GMT; SameSite=None; Secure; HttpOnly
Set-Cookie	receive-cookie-deprecation=1; Path=/; Domain=.yandex.com; Expires=Sun, 29 Mar 2026 12:27:51 GMT; SameSite=None; Secure; HttpOnly; Partitioned
Set-Cookie	bh=YMfOn78GaiPcytG2Abvxn6sE+taGzAi1zO7rA/y5r/8H3/3DkQnzgfb3Dg==; Path=/; Domain=.yandex.com; Expires=Sun, 03 May 2026 12:27:51 GMT; SameSite=None; Secure
Accept-CH	Sec-CH-UA-Platform-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA, Sec-CH-UA-Full-Version-List, Sec-CH-UA-WoW64, Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Platform, Sec-CH-UA-Full-Version, Viewport-Width, DPR, Device-Memory, RTT, Downlink, ECT, Width
Content-Type	text/html; charset=UTF-8
Strict-Transport-Security	max-age=31536000; includeSubDomains
NEL	{"report_to": "network-errors", "max_age": 100, "success_fraction": 0.001, "failure_fraction": 0.1}
P3P	policyref="/w3c/p3p.xml", CP="NON DSP ADM DEV PSD IVDo OUR IND STP PHY PRE NAV UNI"
Date	Sat, 29 Mar 2025 12:27:51 GMT
Transfer-Encoding	chunked

URL: https://www.yandex.com/

Analysis

HTTP connection failed

We were not able to successfully complete this request.

Message: Internal error

WWW TLS

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: www.yandex.com (2a02:6b8:a:0:0:0:0:a)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.yandex.com (77.88.55.88)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: yandex.com (2a02:6b8:a:0:0:0:0:a)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: yandex.com (77.88.44.55)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.yandex.com (5.255.255.77)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: yandex.com (77.88.55.88)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.yandex.com (77.88.44.55)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: yandex.com (5.255.255.77)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

WWW Certificates

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed

Everything seems to be well configured. Well done.

Certificate: yandex.com

Leaf certificate

*.xn--d1acpjx3f.xn--p1ai
Issuer: GlobalSign nv-sa
Not Before: 04 Dec 2024 17:11:48 UTC
Not After: 03 Jun 2025 20:59:59 UTC (expires in 2 months 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	.xn--d1acpjx3f.xn--p1ai .yandex.tr yandex.tr .yandex.az yandex.az .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs *.yandex.aero yandex.aero xn--d1acpjx3f.xn--p1ai
Subject DN	CN=*.xn--d1acpjx3f.xn--p1ai, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	bdcc5883ba5f6defa55e6db3cf0fbf20d029af47
Serial	406101de1711d6eb2f599681
Not Before	04 Dec 2024 17:11:48 UTC
Not After	03 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign ECC OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:587b8e752afe6180aa904001aed6e807466e3f48
Parent Certificate	http://secure.globalsign.com/cacert/gseccovsslca2018.crt
CRL	http://crl.globalsign.com/gseccovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gseccovsslca2018
Certificate Transparency
Signed Certificate Timestamps	04 Dec 2024 17:11:50 UTC \| DigiCert Nessie2025 Log \| Qualified 04 Dec 2024 17:11:50 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 04 Dec 2024 17:11:50 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	890da05776774cb6538e804806b99ef7a8a7582f
SHA256	93475f546be5586c0eb9a5c82cc223480c3f116088284ebb0139a18f154fc86f
SPKI SHA256	1803370d8186a30751548612d9ee5cb14a0c2b21de5c5914176e4b76f632af5d

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

*.xn--d1acpjx3f.xn--p1ai | 93475f5
Not After: 03 Jun 2025 20:59:59 UTC (expires in 2 months 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	.xn--d1acpjx3f.xn--p1ai .yandex.tr yandex.tr .yandex.az yandex.az .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs *.yandex.aero yandex.aero xn--d1acpjx3f.xn--p1ai
Subject DN	CN=*.xn--d1acpjx3f.xn--p1ai, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	bdcc5883ba5f6defa55e6db3cf0fbf20d029af47
Serial	406101de1711d6eb2f599681
Not Before	04 Dec 2024 17:11:48 UTC
Not After	03 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign ECC OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:587b8e752afe6180aa904001aed6e807466e3f48
Parent Certificate	http://secure.globalsign.com/cacert/gseccovsslca2018.crt
CRL	http://crl.globalsign.com/gseccovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gseccovsslca2018
Certificate Transparency
Signed Certificate Timestamps	04 Dec 2024 17:11:50 UTC \| DigiCert Nessie2025 Log \| Qualified 04 Dec 2024 17:11:50 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 04 Dec 2024 17:11:50 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	890da05776774cb6538e804806b99ef7a8a7582f
SHA256	93475f546be5586c0eb9a5c82cc223480c3f116088284ebb0139a18f154fc86f
SPKI SHA256	1803370d8186a30751548612d9ee5cb14a0c2b21de5c5914176e4b76f632af5d

Intermediate certificate

GlobalSign ECC OV SSL CA 2018 | 87c7155
Not After: 21 Nov 2028 00:00:00 UTC (expires in 3 years 7 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=GlobalSign ECC OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	587b8e752afe6180aa904001aed6e807466e3f48
Serial	1ee5f2295424905f90191a8dc
Not Before	21 Nov 2018 00:00:00 UTC
Not After	21 Nov 2028 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign ECC Root CA - R5
Certification Authority	GlobalSign nv-sa
Validation Type	Not Applicable
Authority Key Identifier	keyid:3de629489bea07ca21444a26de6eded283d09f59
CRL	http://crl.globalsign.com/root-r5.crl
OCSP	http://ocsp2.globalsign.com/rootr5
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	953e42ee8d627ced52b96adfc02226b5de130417
SHA256	87c71553445eb3c33c3e0710711b99e9c7773f04d91ac38a9f4c082ee24101ea
SPKI SHA256	289a5e7685c6f9177a2099d878e263c548e568310323c2b5bc2041833789902e

Intermediate certificate

GlobalSign | f349954
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: EC 384 bits (SHA384withRSA)
View details

Subject DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign ECC Root CA - R5
Subject Key Identifier	3de629489bea07ca21444a26de6eded283d09f59
Serial	751e3f53e3185933e95f08eceead0297
Not Before	19 Jun 2019 00:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
CRL	http://crl.globalsign.com/root.crl
OCSP	http://ocsp.globalsign.com/rootr1
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	45769b5127dc1755424becb568c70b4339833fbe
SHA256	f349954e8fb6d44011bcb789d97d9a2cb2032bd5f0b598d1fb8a099f5848d523
SPKI SHA256	7e0ead76bb6819dc2f54511a84354f6e8b307b9dd82058ea6c004f01d9dda5df

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	40000000001154b5ac394
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	b1bc968bd4f49d622aa89a81f2150152a41d829c
SHA256	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Certificate: www.yandex.com

Leaf certificate

*.xn--d1acpjx3f.xn--p1ai
Issuer: GlobalSign nv-sa
Not Before: 04 Dec 2024 17:11:48 UTC
Not After: 03 Jun 2025 20:59:59 UTC (expires in 2 months 5 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	.xn--d1acpjx3f.xn--p1ai .yandex.tr yandex.tr .yandex.az yandex.az .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs *.yandex.aero yandex.aero xn--d1acpjx3f.xn--p1ai
Subject DN	CN=*.xn--d1acpjx3f.xn--p1ai, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	bdcc5883ba5f6defa55e6db3cf0fbf20d029af47
Serial	406101de1711d6eb2f599681
Not Before	04 Dec 2024 17:11:48 UTC
Not After	03 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign ECC OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:587b8e752afe6180aa904001aed6e807466e3f48
Parent Certificate	http://secure.globalsign.com/cacert/gseccovsslca2018.crt
CRL	http://crl.globalsign.com/gseccovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gseccovsslca2018
Certificate Transparency
Signed Certificate Timestamps	04 Dec 2024 17:11:50 UTC \| DigiCert Nessie2025 Log \| Qualified 04 Dec 2024 17:11:50 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 04 Dec 2024 17:11:50 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	890da05776774cb6538e804806b99ef7a8a7582f
SHA256	93475f546be5586c0eb9a5c82cc223480c3f116088284ebb0139a18f154fc86f
SPKI SHA256	1803370d8186a30751548612d9ee5cb14a0c2b21de5c5914176e4b76f632af5d

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

*.xn--d1acpjx3f.xn--p1ai | 93475f5
Not After: 03 Jun 2025 20:59:59 UTC (expires in 2 months 5 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	.xn--d1acpjx3f.xn--p1ai .yandex.tr yandex.tr .yandex.az yandex.az .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs *.yandex.aero yandex.aero xn--d1acpjx3f.xn--p1ai
Subject DN	CN=*.xn--d1acpjx3f.xn--p1ai, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	bdcc5883ba5f6defa55e6db3cf0fbf20d029af47
Serial	406101de1711d6eb2f599681
Not Before	04 Dec 2024 17:11:48 UTC
Not After	03 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign ECC OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:587b8e752afe6180aa904001aed6e807466e3f48
Parent Certificate	http://secure.globalsign.com/cacert/gseccovsslca2018.crt
CRL	http://crl.globalsign.com/gseccovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gseccovsslca2018
Certificate Transparency
Signed Certificate Timestamps	04 Dec 2024 17:11:50 UTC \| DigiCert Nessie2025 Log \| Qualified 04 Dec 2024 17:11:50 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 04 Dec 2024 17:11:50 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	890da05776774cb6538e804806b99ef7a8a7582f
SHA256	93475f546be5586c0eb9a5c82cc223480c3f116088284ebb0139a18f154fc86f
SPKI SHA256	1803370d8186a30751548612d9ee5cb14a0c2b21de5c5914176e4b76f632af5d

Intermediate certificate

GlobalSign ECC OV SSL CA 2018 | 87c7155
Not After: 21 Nov 2028 00:00:00 UTC (expires in 3 years 7 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=GlobalSign ECC OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	587b8e752afe6180aa904001aed6e807466e3f48
Serial	1ee5f2295424905f90191a8dc
Not Before	21 Nov 2018 00:00:00 UTC
Not After	21 Nov 2028 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign ECC Root CA - R5
Certification Authority	GlobalSign nv-sa
Validation Type	Not Applicable
Authority Key Identifier	keyid:3de629489bea07ca21444a26de6eded283d09f59
CRL	http://crl.globalsign.com/root-r5.crl
OCSP	http://ocsp2.globalsign.com/rootr5
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	953e42ee8d627ced52b96adfc02226b5de130417
SHA256	87c71553445eb3c33c3e0710711b99e9c7773f04d91ac38a9f4c082ee24101ea
SPKI SHA256	289a5e7685c6f9177a2099d878e263c548e568310323c2b5bc2041833789902e

Intermediate certificate

GlobalSign | f349954
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: EC 384 bits (SHA384withRSA)
View details

Subject DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign ECC Root CA - R5
Subject Key Identifier	3de629489bea07ca21444a26de6eded283d09f59
Serial	751e3f53e3185933e95f08eceead0297
Not Before	19 Jun 2019 00:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
CRL	http://crl.globalsign.com/root.crl
OCSP	http://ocsp.globalsign.com/rootr1
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	45769b5127dc1755424becb568c70b4339833fbe
SHA256	f349954e8fb6d44011bcb789d97d9a2cb2032bd5f0b598d1fb8a099f5848d523
SPKI SHA256	7e0ead76bb6819dc2f54511a84354f6e8b307b9dd82058ea6c004f01d9dda5df

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	40000000001154b5ac394
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	b1bc968bd4f49d622aa89a81f2150152a41d829c
SHA256	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Certificate: yandex.com

Leaf certificate

*.yandex.az
Issuer: GlobalSign nv-sa
Not Before: 05 Dec 2024 12:18:51 UTC
Not After: 04 Jun 2025 20:59:59 UTC (expires in 2 months 6 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.yandex.az .yandex.tr yandex.tr .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs .yandex.aero yandex.aero *.xn--d1acpjx3f.xn--p1ai xn--d1acpjx3f.xn--p1ai yandex.az
Subject DN	CN=*.yandex.az, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	3e3c8a38578d5bd5ad52dfab2233bdbfc055e377
Serial	50bc4c333c486a6a04a12633
Not Before	05 Dec 2024 12:18:51 UTC
Not After	04 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Parent Certificate	http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
CRL	http://crl.globalsign.com/gsrsaovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gsrsaovsslca2018
Certificate Transparency
Signed Certificate Timestamps	05 Dec 2024 12:18:53 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	fb9e1a6153b3e8c630e720dbc8a3aaa1b6fb865a
SHA256	3ee595585a21636de40d60520c5a72079cfdd5f29e5f446e0df35fd024af3743
SPKI SHA256	0900745e8e03cd143ea35f44c78964f724e15b8131a1e2eb6e3c10b880363799

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

*.yandex.az | 3ee5955
Not After: 04 Jun 2025 20:59:59 UTC (expires in 2 months 6 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.yandex.az .yandex.tr yandex.tr .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs .yandex.aero yandex.aero *.xn--d1acpjx3f.xn--p1ai xn--d1acpjx3f.xn--p1ai yandex.az
Subject DN	CN=*.yandex.az, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	3e3c8a38578d5bd5ad52dfab2233bdbfc055e377
Serial	50bc4c333c486a6a04a12633
Not Before	05 Dec 2024 12:18:51 UTC
Not After	04 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Parent Certificate	http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
CRL	http://crl.globalsign.com/gsrsaovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gsrsaovsslca2018
Certificate Transparency
Signed Certificate Timestamps	05 Dec 2024 12:18:53 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	fb9e1a6153b3e8c630e720dbc8a3aaa1b6fb865a
SHA256	3ee595585a21636de40d60520c5a72079cfdd5f29e5f446e0df35fd024af3743
SPKI SHA256	0900745e8e03cd143ea35f44c78964f724e15b8131a1e2eb6e3c10b880363799

Intermediate certificate

GlobalSign RSA OV SSL CA 2018 | b676ffa
Not After: 21 Nov 2028 00:00:00 UTC (expires in 3 years 7 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Serial	1ee5f221dfc623bd4333a8557
Not Before	21 Nov 2018 00:00:00 UTC
Not After	21 Nov 2028 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
Certification Authority	GlobalSign nv-sa
Validation Type	Not Applicable
Authority Key Identifier	keyid:8ff04b7fa82e4524ae4d50fa639a8bdee2dd1bbc
CRL	http://crl.globalsign.com/root-r3.crl
OCSP	http://ocsp2.globalsign.com/rootr3
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	dfe83023062b997682708b4eab8e819aff5d9775
SHA256	b676ffa3179e8812093a1b5eafee876ae7a6aaf231078dad1bfb21cd2893764a
SPKI SHA256	8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05

Intermediate certificate

GlobalSign | 445eec7
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
Subject Key Identifier	8ff04b7fa82e4524ae4d50fa639a8bdee2dd1bbc
Serial	1ee5f169dff97352b6465d66a
Not Before	19 Sep 2018 00:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
CRL	http://crl.globalsign.com/root.crl
OCSP	http://ocsp.globalsign.com/rootr1
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	0bbfab97059595e8d1ec48e89eb8657c0e5aae71
SHA256	445eec78bc61215044a0379656aa2d5db5e42f76cb70b8d14c2077aa943d4ebb
SPKI SHA256	706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	40000000001154b5ac394
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	b1bc968bd4f49d622aa89a81f2150152a41d829c
SHA256	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Certificate: www.yandex.com

Leaf certificate

*.yandex.az
Issuer: GlobalSign nv-sa
Not Before: 05 Dec 2024 12:18:51 UTC
Not After: 04 Jun 2025 20:59:59 UTC (expires in 2 months 6 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.yandex.az .yandex.tr yandex.tr .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs .yandex.aero yandex.aero *.xn--d1acpjx3f.xn--p1ai xn--d1acpjx3f.xn--p1ai yandex.az
Subject DN	CN=*.yandex.az, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	3e3c8a38578d5bd5ad52dfab2233bdbfc055e377
Serial	50bc4c333c486a6a04a12633
Not Before	05 Dec 2024 12:18:51 UTC
Not After	04 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Parent Certificate	http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
CRL	http://crl.globalsign.com/gsrsaovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gsrsaovsslca2018
Certificate Transparency
Signed Certificate Timestamps	05 Dec 2024 12:18:53 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	fb9e1a6153b3e8c630e720dbc8a3aaa1b6fb865a
SHA256	3ee595585a21636de40d60520c5a72079cfdd5f29e5f446e0df35fd024af3743
SPKI SHA256	0900745e8e03cd143ea35f44c78964f724e15b8131a1e2eb6e3c10b880363799

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

*.yandex.az | 3ee5955
Not After: 04 Jun 2025 20:59:59 UTC (expires in 2 months 6 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.yandex.az .yandex.tr yandex.tr .yandex.by yandex.by .yandex.co.il yandex.co.il .yandex.com yandex.com .yandex.com.am yandex.com.am .yandex.com.ge yandex.com.ge .yandex.com.tr yandex.com.tr .yandex.ee yandex.ee .yandex.fr yandex.fr .yandex.kz yandex.kz .yandex.lt yandex.lt .yandex.lv yandex.lv .yandex.md yandex.md .yandex.ru yandex.ru .yandex.tj yandex.tj .yandex.tm yandex.tm .yandex.uz yandex.uz .ya.ru ya.ru .yandex.de yandex.de .yandex.org yandex.org .yandex.net yandex.net .yandex.jobs yandex.jobs .yandex.aero yandex.aero *.xn--d1acpjx3f.xn--p1ai xn--d1acpjx3f.xn--p1ai yandex.az
Subject DN	CN=*.yandex.az, O=YANDEX LLC, L=Moscow, ST=Moscow, C=RU
Subject Key Identifier	3e3c8a38578d5bd5ad52dfab2233bdbfc055e377
Serial	50bc4c333c486a6a04a12633
Not Before	05 Dec 2024 12:18:51 UTC
Not After	04 Jun 2025 20:59:59 UTC
Validity period	182 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Certification Authority	GlobalSign nv-sa
Validation Type	Organization Validation (OV)
Authority Key Identifier	keyid:f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Parent Certificate	http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
CRL	http://crl.globalsign.com/gsrsaovsslca2018.crl
OCSP	http://ocsp.globalsign.com/gsrsaovsslca2018
Certificate Transparency
Signed Certificate Timestamps	05 Dec 2024 12:18:53 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Sectigo 'Mammoth2025h1' \| Qualified 05 Dec 2024 12:18:53 UTC \| Google 'Argon2025h1' log \| Qualified
Fingerprints
SHA1	fb9e1a6153b3e8c630e720dbc8a3aaa1b6fb865a
SHA256	3ee595585a21636de40d60520c5a72079cfdd5f29e5f446e0df35fd024af3743
SPKI SHA256	0900745e8e03cd143ea35f44c78964f724e15b8131a1e2eb6e3c10b880363799

Intermediate certificate

GlobalSign RSA OV SSL CA 2018 | b676ffa
Not After: 21 Nov 2028 00:00:00 UTC (expires in 3 years 7 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	f8ef7ff2cd7867a8de6f8f248d88f1870302b3eb
Serial	1ee5f221dfc623bd4333a8557
Not Before	21 Nov 2018 00:00:00 UTC
Not After	21 Nov 2028 00:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
Certification Authority	GlobalSign nv-sa
Validation Type	Not Applicable
Authority Key Identifier	keyid:8ff04b7fa82e4524ae4d50fa639a8bdee2dd1bbc
CRL	http://crl.globalsign.com/root-r3.crl
OCSP	http://ocsp2.globalsign.com/rootr3
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	dfe83023062b997682708b4eab8e819aff5d9775
SHA256	b676ffa3179e8812093a1b5eafee876ae7a6aaf231078dad1bfb21cd2893764a
SPKI SHA256	8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05

Intermediate certificate

GlobalSign | 445eec7
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3
Subject Key Identifier	8ff04b7fa82e4524ae4d50fa639a8bdee2dd1bbc
Serial	1ee5f169dff97352b6465d66a
Not Before	19 Sep 2018 00:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
CRL	http://crl.globalsign.com/root.crl
OCSP	http://ocsp.globalsign.com/rootr1
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	0bbfab97059595e8d1ec48e89eb8657c0e5aae71
SHA256	445eec78bc61215044a0379656aa2d5db5e42f76cb70b8d14c2077aa943d4ebb
SPKI SHA256	706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 2 years 9 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	40000000001154b5ac394
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	b1bc968bd4f49d622aa89a81f2150152a41d829c
SHA256	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

DANE (443)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Cookies

Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.

Test passed

Everything seems to be well configured. Well done.

HTTP Cookie: yandex_gid

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	87
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Mon Apr 28 12:27:51 UTC 2025 (29 days 23 hours)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: yp

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	1745843271.ygu.1
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Tue Mar 27 12:27:51 UTC 2035 (9 years 11 months)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: yuidss

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	4108382901743251271
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Tue Mar 27 12:27:51 UTC 2035 (9 years 11 months)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: is_gdpr

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	0
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Mon Mar 29 12:27:51 UTC 2027 (1 year 11 months)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: is_gdpr_b

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	CKKpXBDftwI=
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Mon Mar 29 12:27:51 UTC 2027 (1 year 11 months)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: _yasc

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	lO90Ro1NVzgt9cks91DPQGJiGy/X6T9opO1k/ljc5H2VKkhI58HQQ2H/rKEX9DRpnDY=
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Tue Mar 27 12:27:51 UTC 2035 (9 years 11 months)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: i

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	M1bxftpBr+UPb10FL5pt7b+Xk4dYLZjMImzi5q+PsfPMpYAjJ3UMJIRw7U4IYYWZqPfUOkI8AYKfczYz1eGZBU2Ru5Y=
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Mon Mar 29 12:27:51 UTC 2027 (1 year 11 months)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: yandexuid

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	4108382901743251271
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Mon Mar 29 12:27:51 UTC 2027 (1 year 11 months)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: yashr

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	7560396241743251271
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sun Mar 29 12:27:51 UTC 2026 (11 months 28 days)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: receive-cookie-deprecation

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	1
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sun Mar 29 12:27:51 UTC 2026 (11 months 28 days)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: bh

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	YMfOn78GaiPcytG2Abvxn6sE+taGzAi1zO7rA/y5r/8H3/3DkQnzgfb3Dg==
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	yandex.com
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sun May 03 12:27:51 UTC 2026 (1 year 1 month)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

Analysis

All cookies are secure

Great. All observed cookies are marked secure.

HTML Content

On virtually all web sites, HTML markup, images, style sheets, JavaScript, and other page resources arrive not only over multiple connections but possibly from multiple servers and sites spread across the entire Internet. For a page to be properly encrypted, it’s necessary that all the content is retrieved over HTTPS. In practice, that’s very often not the case, leading to mixed content security problems.

Test passed

Everything seems to be well configured. Well done.

Encryption of Embedded Resources

In this section we look at the transport security of all embedded resources. Mixed active content occurs when there are unprotected scripts or styles embedded in a page. This is typically not allowed by modern browsers. Mixed passive content (images, videos and such) are typically allowed, but shouldn't be present.

0 script(s)
0 out of 0 are secure

0 CSS file(s)
0 out of 0 are secure

0 media file(s)
0 out of 0 are secure

Encryption of Outbound Links

Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.

0 link(s)
0 out of 0 are encrypted

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) vastly improves security of the network encryption layer. With HSTS enabled, browsers no longer allow clicking through certificate warnings errors, which are typically trivial to exploit. Additionally, they will no longer submit insecure (plaintext) requests to the site in question, even if asked.

Test passed

Everything seems to be well configured. Well done.

HSTS Policy Main host

URL from which this policy was obtained.Location	https://yandex.com/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	31,536,000 seconds (about 1 year)
When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

Policy covers subdomains

When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.

Preloading not enabled

This policy doesn't give browsers permission to embed it and provide protection even to the first request to the web site. Sites that wish to use preloading can apply at hstspreload.org.

Port 80 closed

Good. Plaintext port 80 appears closed.

HTTP Public Key Pinning

HTTP Public Key Pinning (HPKP) enables site operators to restrict which certificates are considered valid for their domain names. With a valid HPKP configuration, sites can defeat man in the middle (MITM) attacks using fraudulent or misissued certificates. HPKP is an advanced feature, suitable for use by only high-profile web sites.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Content Security Policy

Content Security Policy (CSP) is a security mechanism that allows web sites control how browsers process their pages. In essence, sites can restrict what types of resources are loaded and from where. CSP policies can be used to defend against cross-site scripting, prevent mixed content issues, as well as report violations for investigation.

Test passed

Everything seems to be well configured. Well done.

Content-Security-Policy

img-src	.verify.yandex.ru .ya.ru .yandex.ru ya.ru yabs.yandex.by yabs.yandex.kz yabs.yandex.ru yabs.yandex.uz yandex.ru yandex.com 'self' yastatic.net data: mc.admetrica.ru mc.yandex.com .mc.yandex.ru adstat.yandex.ru mc.yandex.ru favicon.yandex.net avatars.mds.yandex.net
script-src	'nonce-ICpjzF4ERry4fgPmeh0lNQ==' mc.yandex.com yastatic.net yandex.com mc.yandex.ru *.mc.yandex.ru adstat.yandex.ru surveys.yandex.ru This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-eval'
child-src	.ya.ru .yandex.ru ya.ru yandex.ru mc.yandex.ru mc.yandex.md mc.yandex.com yandex.com
style-src	This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' yastatic.net
report-uri	https://csp.yandex.net/csp
media-src	yastatic.net
connect-src	.strm.yandex.net mc.yandex.com yandex.com yastatic.net yastat.net mc.yandex.ru .mc.yandex.ru adstat.yandex.ru mc.admetrica.ru surveys.yandex.ru *.yandex.net an.yandex.ru yandex.ru
default-src	'self' yastatic.net yastat.net
font-src	yastatic.net

Analysis

Inline styles are allowed

This policy allows inline styles. Although they are not as bad as inline scripts in terms of security, an injection bug in script area would allow the attacker to modify page appearance.

Dynamic code execution is allowed

By default, CSP doesn't allow dynamic script execution via eval and friends, but this policy overrides that behavior by specifyin 'unsafe-eval' in the 'script-src' directive. As a result, XSS defenses provided by CSP are significantly weakened.

Mixed content not blocked

This CSP policy doesn't use any of the directives designed to handle mixed content. Consider using the 'block-all-mixed-content' and 'upgrade-insecure-requests' directives as appropriate to ensure that no mixed content is allowed.

Form targets not restricted

The 'form-action' directive is not explicitly set. Because this directive doesn't fall back to default sources, this means that all targets are allowed.

Analysis

CSP policy detected

Header: Content-Security-Policy

Value: img-src *.verify.yandex.ru *.ya.ru *.yandex.ru ya.ru yabs.yandex.by yabs.yandex.kz yabs.yandex.ru yabs.yandex.uz yandex.ru yandex.com 'self' yastatic.net data: mc.admetrica.ru mc.yandex.com *.mc.yandex.ru adstat.yandex.ru mc.yandex.ru favicon.yandex.net avatars.mds.yandex.net;script-src 'nonce-ICpjzF4ERry4fgPmeh0lNQ==' mc.yandex.com yastatic.net yandex.com mc.yandex.ru *.mc.yandex.ru adstat.yandex.ru surveys.yandex.ru 'unsafe-eval';child-src *.ya.ru *.yandex.ru ya.ru yandex.ru mc.yandex.ru mc.yandex.md mc.yandex.com yandex.com *.ya.ru *.yandex.ru ya.ru yandex.ru;style-src 'unsafe-inline' yastatic.net;report-uri https://csp.yandex.net/csp?project=morda&from=morda.big.com&showid=1743251271746343-10805090992510838290-balancer-l7leveler-kubr-yp-vla-41-BAL&h=home-mordago-stable-web-backend-367.sas.yp-c.yandex.net&yandexuid=4108382901743251271&&version=2025-03-28-798&adb=0;media-src yastatic.net;connect-src *.strm.yandex.net mc.yandex.com yandex.com yastatic.net yastat.net mc.yandex.ru *.mc.yandex.ru adstat.yandex.ru mc.admetrica.ru surveys.yandex.ru *.yandex.net an.yandex.ru yandex.ru;default-src 'self' yastatic.net yastat.net;font-src yastatic.net

Location: https://yandex.com/

Subresource Integrity

Subresource Integrity (SRI) is a new standard that enables browsers to verify the integrity of embedded page resources (e.g., scripts and stylesheets) when they are loaded from third-party web sites. With SRI deployed, remote resources can be used safely, without fear of them being modified by malicious parties.

Test passed

Everything seems to be well configured. Well done.

No external scripts
SRI not needed

No external stylesheets
SRI not needed

Analysis

No remote resources

The homepage of this site doesn't contain any remote resources so SRI is not needed.

Expect CT

Expect-CT is a deprecated response HTTP header designed to enable web sites to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that supported this header will submit reports to the specified reporting endpoint. Chrome was the browser that introduced support for this response header, but later deprecated it and removed it in version 107.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

An Expect-CT policy enables web sites to monitor for any problems related to their Expect-CT compliance, detecting potentially serious issues quickly. When issues arise, compliant browsers will submit reports to the specified reporting endpoints. Before CT became required for all public certificates the Expect-CT was also used to require CT, but that use case no longer applies.

Frame Options

The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: DENY

Framing blocked

Good. Your site doesn't allow page framing from any other page.

XSS Protection

Some browsers ship with so-called XSS Auditors, built-in defenses against XSS. Although these defenses work against simple reflective XSS attacks, they can be abused by skillful attackers to add weaknesses to otherwise secure web sites. These dangers are present in both filtering and blocking modes. At this time, the Safari browser ships with its XSS defenses enabled by default. For this reason, the best approach is to explicitly disable this functionality.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Explicitly disable browser XSS protection

For best security, every web site should explicitly disable browser-based XSS protection. This is because this type of functionality can be used to introduce vulnerabilities into otherwise error-free web sites.

Content Type Options

Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Content-Type-Options

Value: nosniff

Valid configuration

Good. Your configuration is valid. This means that browsers won't try to guess file MIME type on this web site.

Public Report | yandex.com

yandex.com

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mx.yandex.ru (77.88.21.249)

Analysis

Email Certificates (SMTP)

Certificate #1

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

SMTP TLS Reporting

HTTP (80)

URL: http://yandex.com/

Analysis

URL: http://www.yandex.com/

Analysis

HTTP (443)

URL: https://yandex.com/

URL: https://www.yandex.com/

Analysis

WWW TLS

TLS Configuration: www.yandex.com (2a02:6b8:a:0:0:0:0:a)

Analysis

TLS Configuration: www.yandex.com (77.88.55.88)

Analysis

TLS Configuration: yandex.com (2a02:6b8:a:0:0:0:0:a)

Analysis

TLS Configuration: yandex.com (77.88.44.55)

Analysis

TLS Configuration: www.yandex.com (5.255.255.77)

Analysis

TLS Configuration: yandex.com (77.88.55.88)

Analysis

TLS Configuration: www.yandex.com (77.88.44.55)

Analysis

TLS Configuration: yandex.com (5.255.255.77)

Analysis

WWW Certificates

Certificate: yandex.com

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: www.yandex.com

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: yandex.com

Analysis