SSL Check WHOIS
Dashboard / Security Report

myzs.com

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

myzs.com: SSL/TLS grade A (HTTPS Monitor)myzs.comA
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
A

Robust Security

Overall Rating
198.62.93.72 · WHOIS ›
Assessed 2026-11-22 00:57 UTC

Grade Breakdown

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

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)
myzs.com301 → https://myzs.com/ → … → https://zsassociates.sharepoint.com/sites/Myzs → 403 Forbidden302 → https://zsassociates.sharepoint.com/sites/Myzs → 403 Forbidden
www.myzs.comDoes not resolveDoes not resolve
  • http://myzs.com redirects to HTTPS.
  • https://myzs.com forwards visitors to zsassociates.sharepoint.com, a different site, which answers 403 Forbidden. View its report ›
  • www.myzs.com does not resolve: visitors who type it reach nothing.

DNS Records

As a public resolver answered for myzs.com. Looked up 2026-11-22 00:57 UTC · today

TypeRecords
A
AAAA None
NS
ns-1138.awsdns-14.org ns-1774.awsdns-29.co.uk ns-305.awsdns-38.com ns-886.awsdns-46.net
MX None
SPF None

Certificate Identity

Common Namemyzs.com
Alt Names *.myzs.com myzs.com
IssuerCN=Amazon RSA 2048 M04, O=Amazon, C=US
Validity 2026-06-20 to 2027-01-03 (42 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0C277E08E83883B96EA5720E940C1EC3
SHA256 Fingerprint 7d2092d0fe55b474d29ef9affd394fc0f72d7cea11959437f607305a4c21e9a6
Pin SHA256w+cQjh0ridNlxyEmZsfnzgsKLixYBdGGYNQ0S2TSn54=

Certificate Properties

Type DV Domain Validated
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

Protocol Configuration

Supported Protocols

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

Negotiated Cipher

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN No
SNI Required Yes
Supported Named Groups secp256r1 (inferred)
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
HSTS Unknown (the HTTPS request to this IP failed)
HSTS Preloading N/A (HSTS not enabled)
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.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
macOS 14 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 14TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 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
CN=*.myzs.com (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 myzs.com, first seen 2026-08-26; current certificate since 2026-11-22.

Certificates served

Certificate (SHA-256)IssuerValidServed
7d2092d0fe55b474… current Amazon RSA 2048 M042026-06-20 → 2027-01-032026-11-22

Addresses

AddressCertificateSeen
198.62.93.72 7d2092d0fe55b474… 2026-11-22

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 00:57ATLS 1.2 7d2092d0fe55b474… 198.62.93.72