HTTPS Support:  Healthcare

UtahWatch.org evaluates and rates the HTTPS support of over 300 Utah websites and over 130 subdomains of Utah.gov.

See the About page to learn about the rating criteria and this project.

Click the Plus icon next to a name to see the reasons for that website's rating.

Companies, Services

4/3/0
Alpine Home Medical (www.alpinehomemedical.com) Mediocre
  • A verified TLS connection can be established. (SSL Labs report)
  • A page can be successfully fetched over HTTPS.
  • HTTP Strict-Transport-Security header is set but the max-age is less than 30 days.
  • HTTP site redirects to HTTPS.
Tell Alpine Home Medical they should improve their HTTPS support: Tweet @alpinehme
CareSource Home Health & Hospice (www.caresourcehealthcare.com) Bad
  • Nothing is listening on port 443.
EMI Health (www.emihealth.com) Mediocre
  • A verified TLS connection can be established. (SSL Labs report)
  • A page can be successfully fetched over HTTPS.
  • HTTP Strict-Transport-Security header is not set. (About HSTS)
  • HTTP site doesn't redirect to HTTPS.
Tell EMI Health they should improve their HTTPS support: Tweet @emihealth
Merit Medical Systems (www.merit.com) Mediocre
  • A verified TLS connection can be established. (SSL Labs report)
  • A page can be successfully fetched over HTTPS.
  • HTTP Strict-Transport-Security header is not set. (About HSTS)
  • HTTP site redirects to HTTPS.
Mission Health Services (www.missionhealthservices.org) Bad
  • Nothing is listening on port 443.
SouthWest Vision (www.southwestvision.org) Bad
  • Certificate hostname verification fails.
Tell SouthWest Vision they should improve their HTTPS support: Tweet @southwestvision
Utah Telehealth Network (www.utn.org) Bad
  • connect() to port 443 times out.
Tell Utah Telehealth Network they should improve their HTTPS support: Tweet @utahtelehealth

Crisis Services, Shelters

9/1/0
A.C.E.S. (www.acestreatment.org) Bad
  • Nothing is listening on port 443.
Dove Center (www.dovecenter.org) Bad
  • A verified TLS connection can be established. (SSL Labs report)
  • The HTML page loaded over HTTPS has mixed content.
  • HTTP Strict-Transport-Security header is not set. (About HSTS)
  • HTTP site doesn't redirect to HTTPS.
Tell Dove Center they should improve their HTTPS support: Tweet @tweet_dove
New Horizons Crisis Center (www.centralutahcrisisintervention.org) Bad
  • Certificate hostname verification fails.
Odyssey House (www.odysseyhouse.org) Bad
  • Certificate hostname verification fails.
Tell Odyssey House they should improve their HTTPS support: Tweet @odysseyhouseut
Rescue Mission of Salt Lake (www.rescuesaltlake.org) Bad
  • Certificate hostname verification fails.
Tell Rescue Mission of Salt Lake they should improve their HTTPS support: Tweet @rescuesaltlake
Safe Harbor Crisis Center (www.safeharborhope.org) Bad
  • Certificate not trusted by Mozilla cert store.
Tell Safe Harbor Crisis Center they should improve their HTTPS support: Tweet @safeharborut
Seekhaven (www.seekhaven.org) Bad
  • connect() returns with error WSAECONNRESET.
Tell Seekhaven they should improve their HTTPS support: Tweet @seekhaven
South Valley Services (www.svsutah.org) Bad
  • Certificate not trusted by Mozilla cert store.
Tell South Valley Services they should improve their HTTPS support: Tweet @svsutah
The Road Home (www.theroadhome.org) Mediocre
  • A verified TLS connection can be established. (SSL Labs report)
  • A page can be successfully fetched over HTTPS.
  • HTTP Strict-Transport-Security header is not set. (About HSTS)
  • HTTP site redirects to HTTPS.
Tell The Road Home they should improve their HTTPS support: Tweet @theroadhomeut
Utah Domestic Violence Coalition (www.udvc.org) Bad
  • A verified TLS connection can be established. (SSL Labs report)
  • The HTML page loaded over HTTPS has mixed content.
  • HTTP Strict-Transport-Security header is not set. (About HSTS)
  • HTTP site doesn't redirect to HTTPS.

Hospitals, Clinics

9/1/0
Brigham City Community Hospital (www.brighamcityhospital.com) Bad
  • Certificate hostname verification fails.
Tell Brigham City Community Hospital they should improve their HTTPS support: Tweet @brighamcityhosp
Intermountain Healthcare (www.intermountainhealthcare.org) Bad
  • connect() to port 443 times out.
Tell Intermountain Healthcare they should improve their HTTPS support: Tweet @intermountain
Jordan Valley Medical Center (www.jordanvalleymc.com) Bad
  • Certificate not trusted by Mozilla cert store.
Tell Jordan Valley Medical Center they should improve their HTTPS support: Tweet @jordanvalleymed
Lakeview Hospital (www.lakeviewhospital.com) Bad
  • Certificate hostname verification fails.
Tell Lakeview Hospital they should improve their HTTPS support: Tweet @lakeviewhosp
Mountain View Hospital (www.mvhpayson.com) Bad
  • Certificate hostname verification fails.
Tell Mountain View Hospital they should improve their HTTPS support: Tweet @mvhpayson
Ogden Clinic (www.ogdenclinic.com) Mediocre
  • A verified TLS connection can be established. (SSL Labs report)
  • A page can be successfully fetched over HTTPS.
  • HTTP Strict-Transport-Security header is not set. (About HSTS)
  • HTTP site doesn't redirect to HTTPS.
Tell Ogden Clinic they should improve their HTTPS support: Tweet @ogdenclinic
Ogden Regional Medical Center (www.ogdenregional.com) Bad
  • Certificate hostname verification fails.
Tell Ogden Regional Medical Center they should improve their HTTPS support: Tweet @ogdenregional
Promise Hospital of Salt Lake (www.promise-saltlake.com) Bad
  • Certificate hostname verification fails.
St. Mark's Hospital (www.stmarkshospital.com) Bad
  • Certificate hostname verification fails.
Tell St. Mark's Hospital they should improve their HTTPS support: Tweet @stmarkshosp
Timpanogos Regional Hospital (www.timpanogosregionalhospital.com) Bad
  • Certificate hostname verification fails.
Tell Timpanogos Regional Hospital they should improve their HTTPS support: Tweet @timpanogoshosp

Back to the top