| 1. General Results, most used to calculate the result |
| A | name "yandex.ru" is domain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 3331 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: www.yandex.ru has 4 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: yandex.ru has 4 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.yandex.ru has 3 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: yandex.ru has 3 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://dzen.ru/?yredirect=true
| https://sso.passport.yandex.ru/push?uuid=fec0b7cf-fc77-4e16-b060-b70ddd54ca12&retpath=https%3A%2F%2Fdzen.ru%2F%3Fyredirect%3Dtrue%26is_autologin_ya%3Dtrue
| Correct redirect https to https
|
| A | https://yandex.ru/ 5.255.255.77
| https://dzen.ru/?yredirect=true
| Correct redirect https to https
|
| A | https://yandex.ru/ 77.88.44.55
| https://dzen.ru/?yredirect=true
| Correct redirect https to https
|
| A | https://yandex.ru/ 77.88.55.88
| https://dzen.ru/?yredirect=true
| Correct redirect https to https
|
| A | https://yandex.ru/ 2a02:6b8:a::a
| https://dzen.ru/?yredirect=true
| Correct redirect https to https
|
| A | https://www.yandex.ru/ 5.255.255.77
| https://www.yandex.ru/showcaptcha?cc=1&form-fb-hint=8.46&mt=B950532A8D391DE0166BDE97A11CEBCAA940A07064ABC0C4EE81DB1A33AF6EE0E66204D0F12696E0B11D5A475B281A9FE979DE9248BFF35F0A7C1A14C825520DC79D4C463B6004E52C310431E665E40ECC40E902DC05A470B52B957A4A0521CBAB722E1A502541B25792BF063785AB15015FD068975C7F99E7E65D44329DDD7BE9A95FB6C038FCDF8766F345E8AA73D8025F26CA57402C72189949E53E6659074D923BDFD46D765B189AE0A36DBE95D6A87E8DC18C533B9FBEDADF887D92D7BB89B5A7D2887741301A145FBD3AD818C214C9DC465505F7142F88BAE6&retpath=aHR0cHM6Ly93d3cueWFuZGV4LnJ1Lz8%2C_6545baedc2dc834110e0aab79318e3f1&t=2%252F1771111961%252F8ad1caa526ce4972d2515ab96789b315&u=8176847343436318685&s=6da2a2349a891265763b93ffe49a2fb0
| Correct redirect https to https
|
| A | Good: destination is https
|
| HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
|
| https://www.yandex.ru/showcaptcha?cc=1&form-fb-hint=8.46&mt=B950532A8D391DE0166BDE97A11CEBCAA940A07064ABC0C4EE81DB1A33AF6EE0E66204D0F12696E0B11D5A475B281A9FE979DE9248BFF35F0A7C1A14C825520DC79D4C463B6004E52C310431E665E40ECC40E902DC05A470B52B957A4A0521CBAB722E1A502541B25792BF063785AB15015FD068975C7F99E7E65D44329DDD7BE9A95FB6C038FCDF8766F345E8AA73D8025F26CA57402C72189949E53E6659074D923BDFD46D765B189AE0A36DBE95D6A87E8DC18C533B9FBEDADF887D92D7BB89B5A7D2887741301A145FBD3AD818C214C9DC465505F7142F88BAE6&retpath=aHR0cHM6Ly93d3cueWFuZGV4LnJ1Lz8%2C_6545baedc2dc834110e0aab79318e3f1&t=2%252F1771111961%252F8ad1caa526ce4972d2515ab96789b315&u=8176847343436318685&s=6da2a2349a891265763b93ffe49a2fb0
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://dzen.ru/?yredirect=true
|
| Missing HSTS-Header
|
| B | https://yandex.ru/ 5.255.255.77
|
| Missing HSTS-Header
|
| B | https://yandex.ru/ 77.88.44.55
|
| Missing HSTS-Header
|
| B | https://yandex.ru/ 77.88.55.88
|
| Missing HSTS-Header
|
| B | https://yandex.ru/ 2a02:6b8:a::a
|
| Missing HSTS-Header
|
| B | https://www.yandex.ru/ 5.255.255.77
|
| Missing HSTS-Header
|
| B | https://www.yandex.ru/ 77.88.44.55
|
| Missing HSTS-Header
|
| B | https://www.yandex.ru/ 77.88.55.88
|
| Missing HSTS-Header
|
| B | https://www.yandex.ru/ 2a02:6b8:a::a
|
| Missing HSTS-Header
|
| B | https://www.yandex.ru/showcaptcha?cc=1&form-fb-hint=8.46&mt=B950532A8D391DE0166BDE97A11CEBCAA940A07064ABC0C4EE81DB1A33AF6EE0E66204D0F12696E0B11D5A475B281A9FE979DE9248BFF35F0A7C1A14C825520DC79D4C463B6004E52C310431E665E40ECC40E902DC05A470B52B957A4A0521CBAB722E1A502541B25792BF063785AB15015FD068975C7F99E7E65D44329DDD7BE9A95FB6C038FCDF8766F345E8AA73D8025F26CA57402C72189949E53E6659074D923BDFD46D765B189AE0A36DBE95D6A87E8DC18C533B9FBEDADF887D92D7BB89B5A7D2887741301A145FBD3AD818C214C9DC465505F7142F88BAE6&retpath=aHR0cHM6Ly93d3cueWFuZGV4LnJ1Lz8%2C_6545baedc2dc834110e0aab79318e3f1&t=2%252F1771111961%252F8ad1caa526ce4972d2515ab96789b315&u=8176847343436318685&s=6da2a2349a891265763b93ffe49a2fb0
|
| Missing HSTS-Header
|
| B | https://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| http://yandex.ru/ 5.255.255.77
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 5.255.255.77
| is_gdpr_b=CMzOaRCa9AIYASgB; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 5.255.255.77
| _yasc=BCJTAzkFuUCUbZpnw548usez/8ZtjVkzdtnIXzvNm52/WkZu8+IdF1fC/T8YriCG; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 5.255.255.77
| bh=YJmMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.44.55
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.44.55
| is_gdpr_b=CMzOaRCa9AIYASgB; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.44.55
| _yasc=v2q9eTdrk8HgybUt20WOeD/HMKbh0scnwVrUUeQJhsi9CICfyiJ56u7WzUfP/sMe2A==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.44.55
| bh=YJmMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.55.88
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.55.88
| is_gdpr_b=CMzOaRCa9AIYASgB; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.55.88
| _yasc=KVewt0TR1wK7hrWHVQpRU1t05I/RF7Xh0WBTkO7W5CE+nZc9t1hXIfIM/Kot/oiQ; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 77.88.55.88
| bh=YJmMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 2a02:6b8:a::a
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 2a02:6b8:a::a
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 2a02:6b8:a::a
| _yasc=IjsVkW4GGe+XsT15rPFnOvGzke502bn7L2Zk2UdcgGFCYSbn6dFvggvp/3JkFPrh; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/ 2a02:6b8:a::a
| bh=YJmMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 5.255.255.77
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:40 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 5.255.255.77
| is_gdpr_b=CMzOaRCa9AIYASgB; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:40 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 5.255.255.77
| _yasc=7+RAaVfJmYyOkBEPG3sn0DzvIUb8dWXZngL4dbTxgU0Lm5nUxI00lz911Emc30c=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:40 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 5.255.255.77
| bh=YJiMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:40 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.44.55
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:40 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.44.55
| is_gdpr_b=CMzOaRCa9AIYASgB; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:40 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.44.55
| _yasc=H8VSOv75fqCye4g2+6fm4lU82gv/xGA04OeWV/vVsepygtt3fBFEPSGJievZ9cM=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:40 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.44.55
| bh=YJiMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:40 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.55.88
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.55.88
| is_gdpr_b=CMzOaRCa9AIYASgB; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.55.88
| _yasc=EVLYvqd/M9cSf/Iq+mhBOzxPzzJelwn2DbyjPvX9RqVKBXtagv7OuERiRSDS4w==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 77.88.55.88
| bh=YJmMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 2a02:6b8:a::a
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 2a02:6b8:a::a
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 2a02:6b8:a::a
| _yasc=Cj2wPe7IiUX3AlM6PvGwliN7DH7VjEogT9WLsOncDO5qLkPKKnt7475iwH75cw==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/ 2a02:6b8:a::a
| bh=YJmMxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:32:41 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| _yasc=PvteAWhvkeoP63m/z1RKS3SyETVInvBGYYTQvaElOZNQvymR4akwwz8jiRZbMQ==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| bh=YL+MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| _yasc=rpkSvFDMYlM2s4TyVEtkkl+4sNy51b0Vw7dbJfprX7KDiulPVjliKK7WMroHCg==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| bh=YL+MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| _yasc=5JSIOM5SiAFivSoImuKnL5b94jwq0UAWPJxK4I1mbMHGI0stNlyfPgCIXy2FZw==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| bh=YL+MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| _yasc=okvea+Szf9URwNzS8UcJnRJrHSe+3Rmap9Na1EtANGSfsZ2lOxEazzudyZrGcy8=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| bh=YL+MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:18 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:18 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| _yasc=rD227GTuYNAEfPsVgwSEpEKtZYN0TrHHWwaOOCH3eXLswQTs0DPvwcf6t/MsGAE=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:18 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| bh=YL6MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:18 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:18 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:18 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| _yasc=hwsaM6A2reMfFlXPpkhGeaO3q/+r3WE3XeA96eGh7RW2XT4/mktyAl6eJEVu3w==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:18 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| bh=YL6MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:18 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| _yasc=sudDiqpicRU6n/9cbk77w8rLLRmeISf/SgE3r9D0jQJ+SCHipd1fl+49d0ft3Q==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| bh=YL+MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| is_gdpr=1; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| is_gdpr_b=CMzOaRCa9AIYAQ==; Path=/; Domain=.yandex.ru; Expires=Mon, 14 Feb 2028 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| _yasc=gORByPkBYXeVOzeakcKGOI7X/eH+WFT1a7goisPVlQTIw9O1RSvAk0iq8ZDTGaI=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| bh=YL+MxMwGahfcyuH/CJLYobEDn8/14Qz0uPCOA9GMAQ==; Path=/; Domain=.yandex.ru; Expires=Sun, 21 Mar 2027 23:33:19 GMT; SameSite=None; Secure
| Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
|
| B | https://www.yandex.ru/ 5.255.255.77
| spravka=dD0xNzM5NTc1OTYxO2k9ODUuMjE1LjIuMjI3O0Q9M0RFNDhBQTg3NjY4M0JBRTk2NkE2MUJGMTU3M0IwREYwMDA1RTVGQUY1NjhCNTE1Qzg5N0YxQzhCNUREQTlGQTU3MzlEMEM1QzAzNjUxREM7dT0xNzM5NTc1OTYxOTg3NjUzNjc0O2g9MGIxMjY1ZTE3ZTcxNDIxZmUwMmJkY2RhY2FlN2ZjMzM=; domain=.yandex.ru; path=/; expires=Mon, 16 Mar 2026 23:32:41 GMT
| Cookie sent via https, but not marked as secure
|
| B | http://yandex.ru/ 5.255.255.77
| _yasc=BCJTAzkFuUCUbZpnw548usez/8ZtjVkzdtnIXzvNm52/WkZu8+IdF1fC/T8YriCG; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://yandex.ru/ 77.88.44.55
| _yasc=v2q9eTdrk8HgybUt20WOeD/HMKbh0scnwVrUUeQJhsi9CICfyiJ56u7WzUfP/sMe2A==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://yandex.ru/ 77.88.55.88
| _yasc=KVewt0TR1wK7hrWHVQpRU1t05I/RF7Xh0WBTkO7W5CE+nZc9t1hXIfIM/Kot/oiQ; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://yandex.ru/ 2a02:6b8:a::a
| _yasc=IjsVkW4GGe+XsT15rPFnOvGzke502bn7L2Zk2UdcgGFCYSbn6dFvggvp/3JkFPrh; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/ 5.255.255.77
| _yasc=7+RAaVfJmYyOkBEPG3sn0DzvIUb8dWXZngL4dbTxgU0Lm5nUxI00lz911Emc30c=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:40 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/ 77.88.44.55
| _yasc=H8VSOv75fqCye4g2+6fm4lU82gv/xGA04OeWV/vVsepygtt3fBFEPSGJievZ9cM=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:40 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/ 77.88.55.88
| _yasc=EVLYvqd/M9cSf/Iq+mhBOzxPzzJelwn2DbyjPvX9RqVKBXtagv7OuERiRSDS4w==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/ 2a02:6b8:a::a
| _yasc=Cj2wPe7IiUX3AlM6PvGwliN7DH7VjEogT9WLsOncDO5qLkPKKnt7475iwH75cw==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://dzen.ru/?yredirect=true
| zencookie=1859445681771112023; Path=/; Domain=.dzen.ru; Expires=Tue, 12-Feb-2036 23:33:43 GMT; Max-Age=315360000; Secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://dzen.ru/?yredirect=true
| zen_sso_checked=1; Path=/; Domain=.dzen.ru; Expires=Sun, 15-Feb-2026 11:33:43 GMT; Max-Age=43200; Secure; HttpOnly
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://dzen.ru/?yredirect=true
| zen_vk_sso_checked=0; Path=/; Domain=.dzen.ru; Expires=Sun, 15-Feb-2026 11:33:43 GMT; Max-Age=43200; Secure; HttpOnly
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://yandex.ru/ 5.255.255.77
| _yasc=bSPN6QU3SwKS8R3rfQhbAJ1GchnSQCptbZZx0hHlzcEGIb21sTLMDTQlIpWr/knS; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:00 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://yandex.ru/ 77.88.44.55
| _yasc=HYuHyXfjf16Nrd2RsGEU42TefK9pJVox2AQw7jtyTjjpH9fUF6hbymPjvVxYbr0s; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:05 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://yandex.ru/ 77.88.55.88
| _yasc=QwlXr7Dm01Ol2/J6tS0Hr/9giB2J7fwLNpe/+x50c6udOlWOMQpYMJdzdte2f5MP; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:10 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://yandex.ru/ 2a02:6b8:a::a
| _yasc=aey2Wk2iZSLYRW5iYd1Jli6Swi85TryPhoVvCDf2b/wnBHgMx/tOYGTEK0MX+36gfA==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:14 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://sso.passport.yandex.ru/push?uuid=fec0b7cf-fc77-4e16-b060-b70ddd54ca12&retpath=https%3A%2F%2Fdzen.ru%2F%3Fyredirect%3Dtrue%26is_autologin_ya%3Dtrue
| mda2_domains=dzen.ru; Domain=.passport.yandex.ru; Expires=Tue, 19 Jan 2038 03:14:07 GMT; Secure; Path=/
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://www.yandex.ru/ 5.255.255.77
| spravka=dD0xNzM5NTc1OTYxO2k9ODUuMjE1LjIuMjI3O0Q9M0RFNDhBQTg3NjY4M0JBRTk2NkE2MUJGMTU3M0IwREYwMDA1RTVGQUY1NjhCNTE1Qzg5N0YxQzhCNUREQTlGQTU3MzlEMEM1QzAzNjUxREM7dT0xNzM5NTc1OTYxOTg3NjUzNjc0O2g9MGIxMjY1ZTE3ZTcxNDIxZmUwMmJkY2RhY2FlN2ZjMzM=; domain=.yandex.ru; path=/; expires=Mon, 16 Mar 2026 23:32:41 GMT
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://www.yandex.ru/ 5.255.255.77
| _yasc=GOpRMKkgpk7yIqb4tbZU1xjvl7OySs86kC9+w2w5QvqUTeu/VTeh3aY4Ctx4rDA=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:41 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://www.yandex.ru/ 77.88.44.55
| _yasc=gT5uPvW5u6MrEtIiymM6AhkPC5kcFyBbtiPsfVNyU4GvMQkuC0NCoyzof0GaFg==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:47 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://www.yandex.ru/ 77.88.55.88
| _yasc=L/nmvVRfceDdLgB8MU7NEQ+7KvFclGncHyVitSos5ZMA80XVr4PpQJN78YP1ZNU=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:52 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://www.yandex.ru/ 2a02:6b8:a::a
| _yasc=Lr9StopOS3x0VJx7v1jxN5X3BEZygrQ9pYCkNP+fEggVxsywXfq+R5Ik1cg+76k=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:32:56 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://www.yandex.ru/showcaptcha?cc=1&form-fb-hint=8.46&mt=B950532A8D391DE0166BDE97A11CEBCAA940A07064ABC0C4EE81DB1A33AF6EE0E66204D0F12696E0B11D5A475B281A9FE979DE9248BFF35F0A7C1A14C825520DC79D4C463B6004E52C310431E665E40ECC40E902DC05A470B52B957A4A0521CBAB722E1A502541B25792BF063785AB15015FD068975C7F99E7E65D44329DDD7BE9A95FB6C038FCDF8766F345E8AA73D8025F26CA57402C72189949E53E6659074D923BDFD46D765B189AE0A36DBE95D6A87E8DC18C533B9FBEDADF887D92D7BB89B5A7D2887741301A145FBD3AD818C214C9DC465505F7142F88BAE6&retpath=aHR0cHM6Ly93d3cueWFuZGV4LnJ1Lz8%2C_6545baedc2dc834110e0aab79318e3f1&t=2%252F1771111961%252F8ad1caa526ce4972d2515ab96789b315&u=8176847343436318685&s=6da2a2349a891265763b93ffe49a2fb0
| _yasc=KpueP75p581vlZgzP/ByVlyuDc5Nkvokvk53zt1bZ6ZYvvxLb8g21b85/UewxTYo; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:38 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| _yasc=PvteAWhvkeoP63m/z1RKS3SyETVInvBGYYTQvaElOZNQvymR4akwwz8jiRZbMQ==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| _yasc=rpkSvFDMYlM2s4TyVEtkkl+4sNy51b0Vw7dbJfprX7KDiulPVjliKK7WMroHCg==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| _yasc=5JSIOM5SiAFivSoImuKnL5b94jwq0UAWPJxK4I1mbMHGI0stNlyfPgCIXy2FZw==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| _yasc=okvea+Szf9URwNzS8UcJnRJrHSe+3Rmap9Na1EtANGSfsZ2lOxEazzudyZrGcy8=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.255.255.77
| _yasc=rD227GTuYNAEfPsVgwSEpEKtZYN0TrHHWwaOOCH3eXLswQTs0DPvwcf6t/MsGAE=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:18 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.44.55
| _yasc=hwsaM6A2reMfFlXPpkhGeaO3q/+r3WE3XeA96eGh7RW2XT4/mktyAl6eJEVu3w==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:18 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.88.55.88
| _yasc=sudDiqpicRU6n/9cbk77w8rLLRmeISf/SgE3r9D0jQJ+SCHipd1fl+49d0ft3Q==; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | http://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:6b8:a::a
| _yasc=gORByPkBYXeVOzeakcKGOI7X/eH+WFT1a7goisPVlQTIw9O1RSvAk0iq8ZDTGaI=; domain=.yandex.ru; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://5.255.255.77/ 5.255.255.77
| _yasc=NfAL9YOdMbiOWawXrhV1STC9hnFffgDwhqu+1OYUb+P4uaKPYuAbE3ztR128G6g=; domain=.255.77; path=/; expires=Tue, 12 Feb 2036 23:33:19 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://77.88.44.55/ 77.88.44.55
| _yasc=yeQ0uLNNru7qBiyyLrdEilLWzw8U6Z4WPJvU7RQwAYdLjE+/xgkPgfrIAoSkfA==; domain=.44.55; path=/; expires=Tue, 12 Feb 2036 23:33:24 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://77.88.55.88/ 77.88.55.88
| _yasc=GcXdAGzMuBffhk6ySAHbG5+2ayb/jwTE4b4kX2VSf5Cxca++GhiUC1ZpnW8Q1Z8=; domain=.55.88; path=/; expires=Tue, 12 Feb 2036 23:33:29 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://[2a02:06b8:000a:0000:0000:0000:0000:000a]/ 2a02:6b8:a::a
| _yasc=o+y9zPV6uP5haPqNK9gE9UyTneD1oM0XLwijRU4b1K/uhVFd6wRlXyBZYVEzOQ==; domain=.[2a02; path=/; expires=Tue, 12 Feb 2036 23:33:34 GMT; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| K | https://www.yandex.ru/ 5.255.255.77, Status 302
| https://www.yandex.ru/ 77.88.44.55, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://www.yandex.ru/ 5.255.255.77, Status 302
| https://www.yandex.ru/ 77.88.55.88, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://www.yandex.ru/ 5.255.255.77, Status 302
| https://www.yandex.ru/ 2a02:6b8:a::a, Status 301
| Configuration problem - different ip addresses with different status
|
| M | https://5.255.255.77/ 5.255.255.77
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://77.88.44.55/ 77.88.44.55
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://77.88.55.88/ 77.88.55.88
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a02:06b8:000a:0000:0000:0000:0000:000a]/ 2a02:6b8:a::a
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://5.255.255.77/ 5.255.255.77
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://77.88.44.55/ 77.88.44.55
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://77.88.55.88/ 77.88.55.88
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a02:06b8:000a:0000:0000:0000:0000:000a]/ 2a02:6b8:a::a
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.yandex.ru, 4 ip addresses.
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain yandex.ru, 4 ip addresses.
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.yandex.ru, 4 ip addresses, 1 different http results.
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain yandex.ru, 4 ip addresses, 1 different http results.
|
| B | No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.yandex.ru
|
| 2. Header-Checks |
| A | www.yandex.ru
| report-to
| Ok: Header without syntax errors found: { "group": "network-errors", "max_age": 100, "endpoints": [{"url": "https://dr.yandex.net/nel", "priority": 1}, {"url": "https://dr2.yandex.net/nel", "priority": 2}]}
|
| A |
|
| Ok: Header without syntax errors found: { "group": "network-errors", "max_age": 100, "endpoints": [{"url": "https://dr.yandex.net/nel", "priority": 1}, {"url": "https://dr2.yandex.net/nel", "priority": 2}]}
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A | sso.passport.yandex.ru
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'none'; frame-ancestors https://*.dzen.ru https://dzen.ru; connect-src 'self'; script-src 'nonce-5e109f5facdcaadaa17313fea7b69eaf' 'self'; img-src 'self'
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: No object-src found, but the default-src used as fallback is defined and restricted.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
|
| Ok: Nonce found.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: origin
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| F | www.yandex.ru
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.yandex.ru
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.yandex.ru
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.yandex.ru
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.yandex.ru
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.yandex.ru
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | sso.passport.yandex.ru
| Permissions-Policy
| Critical: Missing Header:
|
| B | sso.passport.yandex.ru
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | sso.passport.yandex.ru
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | sso.passport.yandex.ru
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.yandex.ru (213.180.193.1, 2a02:6b8::1), ns2.yandex.ru (2a02:6b8:0:1::1, 93.158.134.1)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.yandex.ru, ns2.yandex.ru, 2 Name Servers included in Delegation: ns1.yandex.RU, ns2.yandex.RU, 2 Name Servers included in 1 Zone definitions: ns1.yandex.ru, ns2.yandex.ru, 1 Name Servers listed in SOA.Primary: ns1.yandex.ru.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.yandex.ru.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.yandex.ru.
|
| A | Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.yandex.ru, ns2.yandex.ru
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
|
| A | Good: All Name Server ip addresses are public.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
|
| Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: ru
|
| Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: yandex.ru
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: RU
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 213., 93., 2 different subnets (first two Bytes): 213.180., 93.158., 2 different subnets (first three Bytes): 213.180.193., 93.158.134.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a02:, 1 different subnets (first two blocks): 2a02:06b8:, 1 different subnets (first three blocks): 2a02:06b8:0000:, 2 different subnets (first four blocks): 2a02:06b8:0000:0000:, 2a02:06b8:0000:0001:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create wildcard-certificates
|
| 4. Content- and Performance-critical Checks |
| A | Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://sso.passport.yandex.ru/push?uuid=fec0b7cf-fc77-4e16-b060-b70ddd54ca12&retpath=https%3A%2F%2Fdzen.ru%2F%3Fyredirect%3Dtrue%26is_autologin_ya%3Dtrue
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://www.yandex.ru/showcaptcha?cc=1&form-fb-hint=8.46&mt=B950532A8D391DE0166BDE97A11CEBCAA940A07064ABC0C4EE81DB1A33AF6EE0E66204D0F12696E0B11D5A475B281A9FE979DE9248BFF35F0A7C1A14C825520DC79D4C463B6004E52C310431E665E40ECC40E902DC05A470B52B957A4A0521CBAB722E1A502541B25792BF063785AB15015FD068975C7F99E7E65D44329DDD7BE9A95FB6C038FCDF8766F345E8AA73D8025F26CA57402C72189949E53E6659074D923BDFD46D765B189AE0A36DBE95D6A87E8DC18C533B9FBEDADF887D92D7BB89B5A7D2887741301A145FBD3AD818C214C9DC465505F7142F88BAE6&retpath=aHR0cHM6Ly93d3cueWFuZGV4LnJ1Lz8%2C_6545baedc2dc834110e0aab79318e3f1&t=2%252F1771111961%252F8ad1caa526ce4972d2515ab96789b315&u=8176847343436318685&s=6da2a2349a891265763b93ffe49a2fb0
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://sso.passport.yandex.ru/push?uuid=fec0b7cf-fc77-4e16-b060-b70ddd54ca12&retpath=https%3A%2F%2Fdzen.ru%2F%3Fyredirect%3Dtrue%26is_autologin_ya%3Dtrue
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| https://www.yandex.ru/showcaptcha?cc=1&form-fb-hint=8.46&mt=B950532A8D391DE0166BDE97A11CEBCAA940A07064ABC0C4EE81DB1A33AF6EE0E66204D0F12696E0B11D5A475B281A9FE979DE9248BFF35F0A7C1A14C825520DC79D4C463B6004E52C310431E665E40ECC40E902DC05A470B52B957A4A0521CBAB722E1A502541B25792BF063785AB15015FD068975C7F99E7E65D44329DDD7BE9A95FB6C038FCDF8766F345E8AA73D8025F26CA57402C72189949E53E6659074D923BDFD46D765B189AE0A36DBE95D6A87E8DC18C533B9FBEDADF887D92D7BB89B5A7D2887741301A145FBD3AD818C214C9DC465505F7142F88BAE6&retpath=aHR0cHM6Ly93d3cueWFuZGV4LnJ1Lz8%2C_6545baedc2dc834110e0aab79318e3f1&t=2%252F1771111961%252F8ad1caa526ce4972d2515ab96789b315&u=8176847343436318685&s=6da2a2349a891265763b93ffe49a2fb0
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| https://sso.passport.yandex.ru/push?uuid=fec0b7cf-fc77-4e16-b060-b70ddd54ca12&retpath=https%3A%2F%2Fdzen.ru%2F%3Fyredirect%3Dtrue%26is_autologin_ya%3Dtrue
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| A | Info: No img element found, no alt attribute checked
|
| A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
| https://yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.927 seconds
| Warning: 404 needs more then one second
|
| https://www.yandex.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.650 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 135743 milliseconds, 135.743 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)