SSL Check WHOIS
Dashboard / Security Report

qlty.sh

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 3.165.136.33 IPv4 WHOIS › A+ 3.165.136.38 IPv4 WHOIS › A+ 3.165.136.5 IPv4 WHOIS › A+ 3.165.136.85 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-06 01:03 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

Protocol Configuration

Supported Protocols

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

Negotiated Cipher

TLS_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 SecP256r1MLKEM768 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Scan Coverage Incomplete no answer in time for: key exchange groups — shown as unknown, not as unsupported
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No
HSTS Yes 2 years · includeSubDomains · preload
HSTS Preloading Not preloadedSubmit →
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
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
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.

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)
qlty.sh301 → https://qlty.sh/ → 200 OK200 OK
www.qlty.shDoes not resolveDoes not resolve
  • http://qlty.sh redirects to HTTPS.
  • www.qlty.sh does not resolve: visitors who type it reach nothing.

DNS Records

As a public resolver answered for qlty.sh. Looked up 2026-11-06 01:03 UTC · 11 days ago

TypeRecords
A
AAAA None
NS
ns-1492.awsdns-58.org ns-1889.awsdns-44.co.uk ns-435.awsdns-54.com ns-515.awsdns-00.net
MX
10 smtp.google.com
SPF
v=spf1 include:_spf.google.com ~all

Certificate Identity

Common Nameqlty.sh
Alt Names qlty.sh *.qlty.sh
IssuerCN=Amazon RSA 2048 M04, O=Amazon, C=US
Validity 2026-09-06 to 2027-03-22 (125 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number022064F9461C8CF66A9ABAA4D8FCD6E0
SHA256 Fingerprint 4d10f493db666da873b0ef6be882a08f7d1216bf4b69b4ae0c33bdfb7778cc41
Pin SHA256GM6np1i7K4zEAsRXAu11O0PKUMgSq3/cmd56pI+aP2k=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m04.amazontrust.com CRL: http://crl.r2m04.amazontrust.com/r2m04.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=qlty.sh (Issuer: CN=Amazon RSA 2048 M04, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M04, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)

TLS History & Relations

Everything our scans have seen for qlty.sh, first seen 2026-11-06; current certificate since 2026-11-06.

Certificates served

Certificate (SHA-256)IssuerValidServed
4d10f493db666da8… current Amazon RSA 2048 M042026-09-06 → 2027-03-222026-11-06

Addresses

AddressCertificateSeen
3.165.136.5 4d10f493db666da8… 2026-11-06
3.165.136.33 4d10f493db666da8… 2026-11-06
3.165.136.38 4d10f493db666da8… 2026-11-06
3.165.136.85 4d10f493db666da8… 2026-11-06

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-06 01:03A+TLS 1.3 4d10f493db666da8… 3.165.136.5, 3.165.136.33, 3.165.136.38, 3.165.136.85

Other hosts seen on the same addresses