mmhosp.com doesn't load. CMS has now sent two corrective action plan requests on the same open case.
Measured against Monrovia Memorial Hospital's own domain and CMS's enforcement record, retrieved Sep 18, 2026.
| Facility | Host domain | cms-hpt.txt | Filename | Schema | Last updated | HTTP last-mod | Type 2 NPI | Attester | Payers | Rows | Rows w/ rate |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Monrovia Memorial Hospital | mmhosp.com | NO | n/a | n/a | n/a | n/a | NO | n/a | 0 | 0 | 0 |
SHARE OF EACH FILE CARRYING A PAYER-SPECIFIC RATE
mmhosp.com fails a basic TLS handshake for every page on the domain, so neither the §180.50 file nor any consumer-facing display can be reached from outside the hospital's network right now.
The domain CMS has on file doesn't resolve to a working site
Requesting https://mmhosp.com/cms-hpt.txt returns a TLS handshake failure. The certificate currently being served on the domain is issued to *.ingress-comporellon.ewp.live, a hosting platform's wildcard certificate, not to mmhosp.com. Every page on the domain, not just the price transparency file, is affected the same way.
Is the hosting migration behind the certificate mismatch temporary, or has the domain been effectively abandoned?
A second CAP Request on the same case usually means the first plan wasn't accepted as sufficient. If the underlying reason is that the site itself isn't reachable, that's a straightforward, fixable cause CMS can be shown directly.
Is there a different domain or subdomain currently serving the hospital's actual website, separate from mmhosp.com?
If patients and CMS are both being pointed at a dead address, the fix might be as simple as updating the domain on file rather than rebuilding the underlying compliance work.
FLAGGED, NOT ASSERTED — COULD NOT BE VERIFIED FROM OUTSIDE THE ORGANIZATION