Congratulations, your browser supports the upcoming PriceHubble certificate!
If you can read this page without warnings, your client successfully validated the TLS certificate and trust chain that will be used for pricehubble.com and *.pricehubble.com. This hostname is published ahead of the production cutover so teams can confirm browsers, APIs, and integrations trust the new certificate authority.
For a minimal check from scripts or load balancers, call
/ping — it returns plain text ok.
Why is the certificate changing?
We are changing the provider of our certificates to better support upcoming frequent renewal requirements and improve the availability of our services with stronger automation.
Why is the trust chain changing?
Today, production presents a GoDaddy chain: leaf *.pricehubble.com issued by GoDaddy TLS Intermediate CA DV – R1v1, then GoDaddy TLS Root CA – R1, anchoring at Go Daddy Root Certificate Authority – G2.
The upcoming leaf is still *.pricehubble.com, but it is issued by WR3 (Google Trust Services). The presented chain continues to GTS Root R1, which is cross-signed by GlobalSign Root CA. Hostname coverage (*.pricehubble.com, pricehubble.com) is unchanged. Google-managed certificates renew about every 90 days; only the leaf changes on renewal, not the Google Trust Services / GlobalSign roots.
Am I impacted?
If you connect to PriceHubble as a client — browser, mobile app, SDK, script, or API integration — and use the operating system or runtime default trust store, you are unlikely to be impacted. That is what this preview site confirms.
You may be impacted if your integration does any of the following:
- Leaf pinning — you fingerprint the current *.pricehubble.com GoDaddy certificate.
- Intermediate pinning — you require GoDaddy TLS Intermediate CA DV – R1v1 (or an older GoDaddy G2 intermediate) instead of WR3.
- Root CA pinning — you trust only Go Daddy Root Certificate Authority – G2 (or GoDaddy TLS Root CA – R1) and reject GTS Root R1 / GlobalSign Root CA.
- Custom trust stores — you ship or maintain your own CA bundle and it does not include Google Trust Services.
If any of these apply, update your pinning or trust configuration before the
production cutover, and use this page (or /ping) to verify your client
accepts the upcoming chain.
Is this a security incident?
No. This is a planned migration from a manually rotated GoDaddy certificate to
Google-managed certificates. There is no indication of compromise. Seeing this page
(or a successful /ping response) means your client already trusts the
upcoming chain.
Current production
Upcoming certificate