SSL Check WHOIS
Dashboard / Security Report

www.tripadvisor.com

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+ 13.227.231.15 IPv4 WHOIS › A+ 13.227.231.58 IPv4 WHOIS › A+ 13.227.231.83 IPv4 WHOIS › A+ 13.227.231.97 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-17 17:16 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 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 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)
www.tripadvisor.com301 → https://www.tripadvisor.com/ → 403 Forbidden403 Forbidden
tripadvisor.com301 → https://tripadvisor.com/ → … → https://www.tripadvisor.com/ → 403 Forbidden301 → https://www.tripadvisor.com/ → 403 Forbidden
  • http://www.tripadvisor.com redirects to HTTPS.

DNS Records

As a public resolver answered for www.tripadvisor.com and its domain tripadvisor.com. Looked up 2026-11-17 17:16 UTC · today

TypeRecords
www.tripadvisor.com
A
AAAA None
MX None
SPF None
tripadvisor.com
A
AAAA None
NS
ns-1455.awsdns-53.org ns-1702.awsdns-20.co.uk ns-218.awsdns-27.com ns-584.awsdns-09.net
MX
10 smtp.google.com
SPF
v=spf1 include:_spf.tripadvisor.com include:mail.zendesk.com ~all

Certificate Identity

Common Namewww.tripadvisor.com
Alt Names *.tripadvisor.com tripadvisor.com
IssuerCN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE
Validity 2026-01-06 to 2027-02-07 (82 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0DBBEBF9E621BC9E941AD683
SHA256 Fingerprint dabbfe30debe2b2aa4f84e9b18b306c42d389241d49fa26f622f4bcaf33fe7ed
Pin SHA256qTW47YUDKKMyrjBN0ELHIYIJcEq2rWNvQ+ncsBCNwXQ=

Certificate Properties

Type OV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Unknown (OCSP-only certificate; not queried) OCSP: http://ocsp.globalsign.com/gsrsaovsslca2018
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 397 days (maximum 398 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)
• Chain contains certificates in the wrong order or unrelated certificates

Trust Chain Architecture

End-Entity Certificate
CN=*.tripadvisor.com, O=Tripadvisor LLC, L=Needham Heights, S=Massachusetts, C=US (Issuer: CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE)
Intermediate CA
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3)
Root Certificate
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3 (Issuer: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3)

TLS History & Relations

Everything our scans have seen for www.tripadvisor.com, first seen 2026-11-17; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
dabbfe30debe2b2a… current GlobalSign RSA OV SSL CA 20182026-01-06 → 2027-02-072026-11-17

Addresses

AddressCertificateSeen
13.227.231.15 dabbfe30debe2b2a… 2026-11-17
13.227.231.58 dabbfe30debe2b2a… 2026-11-17
13.227.231.83 dabbfe30debe2b2a… 2026-11-17
13.227.231.97 dabbfe30debe2b2a… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 17:16A+TLS 1.3 dabbfe30debe2b2a… 13.227.231.15, 13.227.231.58, 13.227.231.83, 13.227.231.97

Other hosts seen on the same addresses