hsbcadvance.com.tw
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+ 184.25.179.61 IPv4 WHOIS › A+ 184.31.10.62 IPv4 WHOIS › A+ 23.1.106.62 IPv4 WHOIS › A+ 23.1.35.61 IPv4 WHOIS › 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_256_GCM_SHA384
Protocol Details
| Connection | |
| ALPN | h2 http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | X25519MLKEM768 x25519 secp256r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768 |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (legacy TLS disabled) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | Yes |
| HSTS | Yes 1 year · includeSubDomains |
| HSTS Preloading | Not preloadedSubmit → |
| Security Checks | |
| BEAST attack | Mitigated |
| POODLE (SSLv3) | No (SSL 3 not supported) |
| POODLE (TLS) | No |
| RC4 | No |
| SSL/TLS Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 | |||||
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | 0xC02C | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 0xC02B | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA9 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_ECDSA_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.
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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| hsbcadvance.com.tw | 301 → http://www.hsbc.com.tw/ → … → https://www.hsbc.com.tw/ → 200 OK | 301 → https://www.hsbc.com.tw/ → 200 OK |
| www.hsbcadvance.com.tw | 301 → https://www.hsbcadvance.com.tw/ → … → https://www.hsbc.com.tw/advance/ → 200 OK | 301 → https://www.hsbc.com.tw/advance/ → 200 OK |
- http://hsbcadvance.com.tw redirects to HTTPS.
- https://hsbcadvance.com.tw forwards visitors to www.hsbc.com.tw, a different site. View its report ›
DNS Records
As a public resolver answered for hsbcadvance.com.tw. Looked up 2026-11-17 06:02 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns1.hsbc.com.sg ns11.hsbc.com.hk ns20.hsbc.net ns20.hsbc.uk ns21.hsbc.net ns21.hsbc.uk |
| MX | None |
| SPF | v=spf1 -all |
Certificate Identity
| Common Name | hsbcadvance.com.tw |
| Alt Names | hsbc.com.tw hsbcadvance.com.tw |
| Issuer | CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US |
| Validity | 2026-05-29 to 2026-12-13 (26 days remaining) |
| Key | ECDSA 256 bits (sha384ECDSA) |
| Serial Number | 08190AF3EC8F184CC5BF214486591810 |
| SHA256 Fingerprint | 112adb255afa72942b2ea04d25d51c69fafc5013dfa778c114f3850b3656a04d |
| Pin SHA256 | C/TzQCH5kqZjFBv+2kFLXZn1G+h+lhvoHqq6Yp3l21g= |
Certificate Properties
| Type | EV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.digicert.com CRL: http://crl3.digicert.com/DigiCertGlobalG3TLSECCSHA3842020CA1-2.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 199 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=hsbc.com.tw, O=HSBC Group Management Services Limited, L=London, C=GB, SERIALNUMBER=09231974, businessCategory=Private Organization, jurisdictionCountryName=GB (Issuer: CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US)
Intermediate CA
CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
TLS History & Relations
Everything our scans have seen for hsbcadvance.com.tw, first seen 2026-10-08; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 112adb255afa7294… current | DigiCert Global G3 TLS ECC SHA384 2020 CA1 | 2026-05-29 → 2026-12-13 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 23.1.35.61 | 112adb255afa7294… | 2026-11-17 |
| 23.1.106.62 | 112adb255afa7294… | 2026-11-17 |
| 184.25.179.61 | 112adb255afa7294… | 2026-11-17 |
| 184.31.10.62 | 112adb255afa7294… | 2026-11-17 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-17 06:02 | A+ | TLS 1.3 | 112adb255afa7294… | 23.1.35.61, 23.1.106.62, 184.25.179.61, 184.31.10.62 |
Other domains on the same certificate
- hsbc.com.tw 1 name