SSL Check WHOIS
Dashboard / Security Report

yangsanlang.com.tw

Overall grade based on: IPv4: 2 of 2 complete · IPv6: 0 of 2 complete, 2 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2606:4700:3033::6815:15a9 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2606:4700:3035::ac43:c7a3 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).

The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.

All 2 endpoints share identical configuration Select an IP for owner, ASN & location
B 104.21.21.169 IPv4 WHOIS › B 172.67.199.163 IPv4 WHOIS ›
B

Adequate Protection

Overall Rating
Assessed 2026-11-19 03:28 UTC

Grade Breakdown

Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.

Security Vulnerabilities Detected

  • •Obsolete TLS versions (1.0/1.1) supported.
  • •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).

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 Yes
Supported Named Groups X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
HTTP/3 (QUIC) Yes (advertised)
Encrypted Client Hello Yes(ECH config in HTTPS DNS record)
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (TLS_FALLBACK_SCSV)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 1 year
HSTS Preloading Not preloadedSubmit →
Security Checks
BEAST attack Not mitigated server-side (TLS 1.0 + CBC)
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) Possible (CBC + legacy TLS present)
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_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak

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_ECDSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.0.4TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess
Android 4.1.1TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess
Baidu Jan 2015TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess
Java 6TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHASuccess

* 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)
yangsanlang.com.tw301 → https://yangsanlang.com.tw/ → 200 OK200 OK
www.yangsanlang.com.tw301 → https://www.yangsanlang.com.tw/ → … → https://yangsanlang.com.tw/ → 200 OK301 → https://yangsanlang.com.tw/ → 200 OK
  • http://yangsanlang.com.tw redirects to HTTPS.

DNS Records

As a public resolver answered for yangsanlang.com.tw. Looked up 2026-11-19 03:28 UTC · today

TypeRecords
A
AAAA
NS
kyree.ns.cloudflare.com ligia.ns.cloudflare.com
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 dc-4af145a5a9de.yangsanlang.com.tw 20 dc-f1db52101538.yangsanlang.com.tw
SPF
v=spf1 include:amazonses.com include:yangsanlang.com.tw include:_spf.wpcloud.com ~all

Certificate Identity

Common Nameyangsanlang.com.tw
Alt Names yangsanlang.com.tw *.yangsanlang.com.tw
IssuerCN=WE1, O=Google Trust Services, C=US
Validity 2026-10-10 to 2027-01-08 (49 days remaining)
KeyECDSA 256 bits (sha256ECDSA)
Serial Number0DC53D96D868290B0EEB0EB3148D034B
SHA256 Fingerprint e544843aa96e8340365645653925c7685691a138cb3825334dec9cd345389d5f
Pin SHA256y44gx3urem4X4w8JyHirznTLvyxirzrQDrjeQib0qqk=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://c.pki.goog/we1/QX7MXtcapCY.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 90 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=yangsanlang.com.tw (Issuer: CN=WE1, O=Google Trust Services, C=US)
Intermediate CA
CN=WE1, O=Google Trust Services, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)
Root Certificate
CN=GTS Root R4, O=Google Trust Services LLC, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)

TLS History & Relations

Everything our scans have seen for yangsanlang.com.tw, first seen 2026-11-19; current certificate since 2026-11-19.

Certificates served

Certificate (SHA-256)IssuerValidServed
e544843aa96e8340… current WE12026-10-10 → 2027-01-082026-11-19

Addresses

AddressCertificateSeen
104.21.21.169 e544843aa96e8340… 2026-11-19
172.67.199.163 e544843aa96e8340… 2026-11-19

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-19 03:28BTLS 1.3 e544843aa96e8340… 104.21.21.169, 172.67.199.163

Other hosts seen on the same addresses