# Certificate on headphone.com expired **URL:** \ **Category:** Site Feedback\ **Created:** [June 16, 2020, 8:21pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085 "2020-06-16T20:21:05Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Simonfish](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@Simonfish](https://forum.headphones.com/u/Simonfish)\ **Post date:** [June 16, 2020, 8:21pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085/1 "2020-06-16T20:21:05Z")
Hey folks, the SSL certificate for [headphone.com](http://headphone.com) has expired, and if you go there (or, say, click on the link to Ian’s review from the product page for the Phonitor X) you get a scary-looking “certificate expired” warning. The redirect works fine if you proceed, but you have to know how to do that. Once you’ve ignored the warning once, it seems to allow further navigation [headphone.com](http://headphone.com) with no warnings (at least on Chrome/Edge) ---
**Author:** ![duke.briscoe](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@duke.briscoe](https://forum.headphones.com/u/duke.briscoe)\ **Post date:** [June 16, 2020, 8:51pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085/2 "2020-06-16T20:51:33Z")
Maybe someone fixed it quickly, because I’m not seeing a problem using Safari on Mac. ---
**Author:** ![Simonfish](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@Simonfish](https://forum.headphones.com/u/Simonfish)\ **Post date:** [June 16, 2020, 8:58pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085/3 "2020-06-16T20:58:11Z")
I just it on Safari, Chrome and Firefox on my Mac, and none are showing the warning. FF on my Windows machine continues to show the warning (I haven’t navigated past it in FF). Edge and Chrome use the same Chromium engine, so it’s not surprising that they share the same “accept” list too. However, checking the cert using [sslshopper.com](http://sslshopper.com) reveals that the same expired cert is still in place. ---
**Author:** ![allegro](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.headphones.com/allegro/32/3846_2.png) [@allegro](https://forum.headphones.com/u/allegro)\ **Post date:** [June 16, 2020, 10:55pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085/4 "2020-06-16T22:55:29Z")
Odd I just used [sslshopper.com](http://sslshopper.com) on multiple browsers and all say the certificate for [www.headphones.com](http://www.headphones.com) still has 52 days before expiration. ---
**Author:** ![ProfFalkin](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.headphones.com/proffalkin/32/1399_2.png) [@ProfFalkin](https://forum.headphones.com/u/ProfFalkin)\ **Post date:** [June 16, 2020, 11:05pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085/5 "2020-06-16T23:05:10Z")
[Headphone.com](http://Headphone.com) and [headphones.com](http://headphones.com) are two different domains. I believe Taron or Andrew said [headphone.com](http://headphone.com) was being retired or something. What better time than when the cert expires. ---
**Author:** ![Simonfish](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@Simonfish](https://forum.headphones.com/u/Simonfish)\ **Post date:** [June 16, 2020, 11:21pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085/6 "2020-06-16T23:21:34Z")
They just need to make sure that any content which links to [headphone.com](http://headphone.com) has been fixed. No-one likes broken links 🙂 ---
**Author:** ![jhsmastering](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.headphones.com/jhsmastering/32/29947_2.png) [@jhsmastering](https://forum.headphones.com/u/jhsmastering)\ **Post date:** [July 3, 2021, 4:16pm UTC](https://forum.headphones.com/t/certificate-on-headphone-com-expired/7085/7 "2021-07-03T16:16:32Z")
Sorry for the resurrection, but I had a workaround/solution to share with y’all. Any of the old links will work if you click in the URL bar and add the “s” after “headphone” in the URL. Doing that will take you to the correct link.