SSL Check WHOIS
Dashboard / Security Report

youtube.kz

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
F

Critical: Insecure

Overall Rating
89.35.125.9 · WHOIS ›
Assessed 2026-11-17 14:46 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 0%
Certificate has expired. This domain's SSL/TLS certificate is no longer valid and browsers will show security warnings to visitors.
Certificate is expired.

Site Access: HTTP and HTTPS

What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.

Hosthttp:// (port 80)https:// (port 443)
youtube.kz200 OK (unencrypted)200 OK · certificate does not cover this name
www.youtube.kzDoes not resolveDoes not resolve
  • http://youtube.kz answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
  • www.youtube.kz does not resolve: visitors who type it reach nothing.

DNS Records

As a public resolver answered for youtube.kz. Looked up 2026-11-17 14:46 UTC · today

TypeRecords
A
AAAA None
NS
ns1.google.com ns2.google.com ns3.google.com ns4.google.com
MX None
SPF
v=spf1 -all

Certificate Identity

Common Nameyoutube.kz
Issuer[email protected], CN=Plesk, O=Plesk, L=Schaffhausen, C=CH
Validity 2019-09-09 to 2020-09-08 (2261 days ago — expired)
KeyRSA 2048 bits (sha256RSA)
Serial Number5D75E557
SHA256 Fingerprint 3af35464a8e0797a87e147319aed1728c7904dc78a1823acb15149f9e0ed46f4
Pin SHA256GV2p7ljk2SaeCevHp9hVqsjSVK6+UVFdvb+tgi3Q3fo=

Certificate Properties

Type OV
Cert Transparency No
OCSP Must Staple No
Revocation N/A (self-signed)
DNS CAA Yes (configured) 0 issue "pki.goog"
Trusted By Not verified
Name Match No — certificate does not cover this host
Validity Period 365 days
Policy Warnings
• Certificate does not cover youtube.kz (name mismatch): browsers will show an error.
Chain IssuesNone

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required No
Supported Named Groups x25519 secp256r1 x448 secp521r1 secp384r1 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Unknown (the HTTPS request to this IP failed)
HSTS Preloading Preloaded
Security Checks
BEAST attack Mitigated
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) No
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3 (server-preferred order)
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256 Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384 Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 4.0.4-- No
Android 4.1.1-- No
Baidu Jan 2015-- No
Java 6-- No

* Simulated based on server's supported protocols and cipher configuration.

Trust Chain Architecture

End-Entity Certificate
[email protected], CN=Plesk, O=Plesk, L=Schaffhausen, C=CH (Issuer: [email protected], CN=Plesk, O=Plesk, L=Schaffhausen, C=CH)

TLS History & Relations

Everything our scans have seen for youtube.kz, first seen 2026-10-09; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
3af35464a8e0797a… current Plesk2019-09-09 → 2020-09-082026-11-17

Addresses

AddressCertificateSeen
89.35.125.9 3af35464a8e0797a… 2026-11-17

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 14:46FTLS 1.3 3af35464a8e0797a… 89.35.125.9