Digital exposure report
hmhospitales.com
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-19 02:56 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.hmhospitales.com
- 2.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://hmhospitales.com/ | grep -i "Strict-Transport-Security"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- hmhospitales.com
- Website request
- GET https://hmhospitales.com/
- Scan time
- 2026-11-19 02:56:01 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 20/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 18/25 | Encryption is in place, but a gap could expose users. |
| Browser protections | 13/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.HighHTTP → HTTPS redirect · Hardening gap+7
- 3.MediumDMARC — anti-spoofing policy · Hardening gap+10
- 4.MediumDNSSEC — signed DNS records · Hardening gap+7
- 5.LowX-Content-Type-Options · Hardening gap+4
- 6.LowPermissions-Policy · Hardening gap+2
- 7.LowCSP — protection from script injection · Hardening gap+3
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 6 of the 10 allowed DNS lookups.
v=spf1 include:spf.protection.outlook.com ip4:185.132.183.52 ip4:212.4.96.83 ip4:185.183.30.110 ip4:91.215.64.147 ip4:212.4.98.26 ip4:212.4.111.188 ip4:54.240.49.120 ip4:54.240.49.121 ip4:212.4.107.191 ip4:212.4.107.20 ip4:212.4.108.179 ip4:212.4.122.120 ip4:212.4.99.138 a:listahm.hmhospitales.com a:listaformacion.hmhospitales.com include:servers.mcsv.net a:servweb01.gnet.es include:_spf.stampymail.com -all
$ dig +short TXT hmhospitales.com
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 5/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect.
v=DMARC1; p=none; pct=100; rua=mailto:b8699467e2c34f419bca0ae85e2d167c@dmarc-reports.cloudflare.net,mailto:admin@hmhospitales.com;
$ dig +short TXT _dmarc.hmhospitales.com
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.hmhospitales.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@hmhospitales.com; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: selector1, selector2, k1, s1, s2, mail. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC6H+Wvas+U8bHoy4UTUjvjoTmp/KMCRHRK… selector2._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArZgoeoWZpUaKwUcWmBxSrkZZPpS4… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2nSFym0PzrVaIdShRsz5EIdHsvonXSiW… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDT1y94XM69BEhpAcSWi+RTJEDpbXVUmW3Kva+R… mail._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDmMd2Tj9Y2GhxAvm98t2rps7iCv8SUoHjX…
$ dig +short TXT selector1._domainkey.hmhospitales.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mxa-004e2c01.gslb.pphosted.com 10 mxb-004e2c01.gslb.pphosted.com
$ dig +short MX hmhospitales.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://hmhospitales.com/ returned HTTP 403 (final URL: https://hmhospitales.com/). Client-side certificate validation passed.
HTTP 403 Final URL: https://hmhospitales.com/
$ curl -sIL https://hmhospitales.com/
HTTP → HTTPS redirect
Failed · Severity: High · Hardening gap · 0/7The site is also reachable over an unencrypted connection, so data may travel in plain text on public networks.
http://hmhospitales.com/ returned HTTP 403 without redirecting to https://.
HTTP 403 Location: (none)
$ curl -sI http://hmhospitales.com/ | grep -iE "^(HTTP|location)"
- Set up a permanent (301) redirect from every HTTP request to HTTPS on the server or CDN.
- Then add an HSTS header.
server {
listen 80;
server_name hmhospitales.com www.hmhospitales.com;
return 301 https://$host$request_uri;
}Safety: This change is made on your server. Make sure HTTPS works first, otherwise the site won't load.
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: SSL.com, expiring 2027-06-03 (196 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: SSL.com Valid from: 2026-11-17 Valid until: 2027-06-03 Names: *.hmhospitales.com, hmhospitales.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect hmhospitales.com:443 -servername hmhospitales.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Failed · Severity: High · Hardening gap · 0/8Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.
No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.
Strict-Transport-Security: (missing)
$ curl -sIL https://hmhospitales.com/ | grep -i "Strict-Transport-Security"
- Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
- Gradually raise it to 31536000 (one year) and add includeSubDomains.
- Consider preload only once the policy is stable — removal from the preload list is slow.
/* Strict-Transport-Security: max-age=31536000; includeSubDomains
Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: 'unsafe-inline', 'unsafe-eval' — weakens XSS protection.
Content-Security-Policy: base-uri 'none'; default-src 'self'; frame-ancestors 'self'; object-src 'none'; upgrade-insecure-requests; form-action 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' challenges.cloudflare.com *.google-analytics.com region1.google-analytics.com *.googletagmanager.com *.googleapis.com *.google.com *.gstatic.com *.azureedge.net unpkg.com *.cookiebot.com *.cloudflare.com cloudflareinsights.com *.cloudflareinsights.com *.amazonaws.com *.cloudfront.net hmhospitales.com *.hmhospitales.com *.talentclue.com *.youtube.com *.youtube-nocookie.com script.hotjar.com static.hotjar.com t.contentsquare.net app.contentsquare.com *.contentsquare.net www.googleadservices.com *.googleadservices.com *.doubleclick.net *.googlesyndication.com connect.facebook.net facebook.com www.facebook.com *.facebook.net cdn.jsdelivr.net tags.srv.stackadapt.com app.konverting.io *.sealmetrics.com; script-src-elem 'self' 'unsafe-inline' 'unsafe-eval' challenges.cloudflare.com *.google-analytics.com region1.google-analytics.com *.googletagmanager.com *.googleapis.com *.google.com *.gstatic.com *.azureedge.net unpkg.com *.cookiebot.com *.cloudflare.com cloudflareinsights.com *.cloudflareinsights.com *.amazonaws.com *.cloudfront.net hmhospitales.com *.hmhospitales.com *.talentclue.com *.youtube.com *.youtube-nocookie.com script.hotjar.com static.hotjar.com t.contentsquare.net app.contentsquare.com *.contentsquare.net www.googleadservices.com *.googleadservices.com *.doubleclick.net *.googlesyndication.com connect.facebook.net facebook.com www.facebook.com *.facebook.net cdn.jsdelivr.net tags.srv.stackadapt.com app.konverting.io *.sealmetrics.com; connect-src 'self' hmhospitales.com www.hmhospitales.com *.hmhospitales.com cloudflareinsights.com *.cloudflareinsights.com *.google-analytics.com region1.google-analytics.com *.googletagmanager.com *.googleapis.com *.google.com google.es www.google.es www.googleadservices.com *.googleadservices.com *.analytics.google.com *.doubleclick.net *.googlesyndication.com *.cookiebot.com *.azureedge.net *.amazonaws.com *.cloudfront.net *.openstreetmap.org overpass-api.de *.svc.dynamics.com *.mkt.dynamics.com *.sentry.io *.youtube.com *.youtube-nocookie.com *.talentclue.com script.hotjar.com static.hotjar.com *.hotjar.com *.hotjar.io *.contentsquare.net wss://*.hotjar.com wss://*.contentsquare.net connect.facebook.net facebook.com www.facebook.com *.facebook.net *.srv.stackadapt.com app.konverting.io *.sealmetrics.com; img-src 'self' data: blob: hmhospitales.com *.hmhospitales.com *.google.com google.es www.google.es *.googletagmanager.com *.google-analytics.com *.analytics.google.com *.doubleclick.net *.googlesyndication.com *.openstreetmap.org *.ytimg.com *.cookiebot.com *.amazonaws.com *.cloudfront.net *.azureedge.net *.talentclue.com unpkg.com *.hotjar.com *.hotjar.io *.contentsquare.net connect.facebook.net facebook.com www.facebook.com *.facebook.net *.srv.stackadapt.com www.googleadservices.com googleadservices.com *.googleadservices.com *.imgix.net s.w.org; media-src 'self' data: blob: hmhospitales.com *.hmhospitales.com *.amazonaws.com *.cloudfront.net; font-src 'self' data: *.gstatic.com *.azureedge.net *.cloudfront.net hmhospitales.com *.hmhospitales.com *.talentclue.com; style-src 'self' 'unsafe-inline' *.googleapis.com *.cookiebot.com unpkg.com hmhospitales.com *.hmhospitales.com *.talentclue.com www.googletagmanager.com cdn.jsdelivr.net cdn.srv.stackadapt.com tags.srv.stackadapt.com *.cloudfront.net; frame-src 'self' blob: *.cloudflare.com *.cookiebot.com www.googletagmanager.com www.google.com *.youtube.com *.youtube-nocookie.com hmhospitales.com *.hmhospitales.com *.talentclue.com *.hotjar.com *.contentsquare.net *.mkt.dynamics.com *.svc.dynamics.com *.doubleclick.net; worker-src 'self' blob:;
$ curl -sIL https://hmhospitales.com/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN frame-ancestors 'self'
X-Frame-Options: SAMEORIGIN CSP frame-ancestors: 'self'
$ curl -sIL https://hmhospitales.com/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://hmhospitales.com/ | grep -i "X-Content-Type-Options"
- Add X-Content-Type-Options: nosniff to every response.
/* X-Content-Type-Options: nosniff
Safety: This change is made in your server/CDN settings. Test on staging before production.
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: same-origin
Referrer-Policy: same-origin
$ curl -sIL https://hmhospitales.com/ | grep -i "Referrer-Policy"
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://hmhospitales.com/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://hmhospitales.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS hmhospitales.com: NODATA
$ dig +short DS hmhospitales.com
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec hmhospitales.com SOA delv hmhospitales.com
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "comodoca.com" | 0 issue "digicert.com; cansignhttpexchanges=yes" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "sectigo.com" | 0 issue "ssl.com" | 0 issuewild "amazon.com" | 0 issuewild "amazonaws.com" | 0 issuewild "amazontrust.com" | 0 issuewild "awstrust.com" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com; cansignhttpexchanges=yes" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "sectigo.com" | 0 issuewild "ssl.com"
0 issue "amazon.com" 0 issue "amazonaws.com" 0 issue "amazontrust.com" 0 issue "awstrust.com" 0 issue "comodoca.com" 0 issue "digicert.com; cansignhttpexchanges=yes" 0 issue "letsencrypt.org" 0 issue "pki.goog; cansignhttpexchanges=yes" 0 issue "sectigo.com" 0 issue "ssl.com" 0 issuewild "amazon.com" 0 issuewild "amazonaws.com" 0 issuewild "amazontrust.com" 0 issuewild "awstrust.com" 0 issuewild "comodoca.com" 0 issuewild "digicert.com; cansignhttpexchanges=yes" 0 issuewild "letsencrypt.org" 0 issuewild "pki.goog; cansignhttpexchanges=yes" 0 issuewild "sectigo.com" 0 issuewild "ssl.com"
$ dig +short CAA hmhospitales.com
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
ada.ns.cloudflare.com rex.ns.cloudflare.com
$ dig +short NS hmhospitales.com
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rules1 observed gaps
- PCI DSS v4.03 observed gaps
- NIS2 / vendor due diligence3 observed gaps
- SOC 2 / ISO 27001 baseline4 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | hmhospitales.com | 104.18.4.210 | 104.18.5.210 |
| AAAA | hmhospitales.com | 2606:4700::6812:4d2 | 2606:4700::6812:5d2 |
| MX | hmhospitales.com | 10 mxa-004e2c01.gslb.pphosted.com | 10 mxb-004e2c01.gslb.pphosted.com |
| NS | hmhospitales.com | ada.ns.cloudflare.com | rex.ns.cloudflare.com |
| TXT | hmhospitales.com | Dynatrace-site-verification=e020620c-e35b-40ba-bb3a-185e77d5ce5d__8g9k72v5hiast063qcajb5nj5t | MS=ms56869484 | MS=ms62375315 | MS=ms84544719 | d365mktkey=1egqixy6ipehr4rahlu039txn | d365mktkey=34x1gnoxmifv57x3ew4uz2hrl | google-gws-recovery-domain-verification=60556628 | google-site-verification=CUEuHsbn0_u4_8R-1If1fRNaGCIn7IdSO0N-kjybSwE | have-i-been-pwned-verification=d6c3b80c1fe23d45354016fdbec9a38b | msfpkey=63lrrge8sro2yp5siel9vsrkc | one-time-verification=8a04b866-add7-430e-bbe0-1bbc044a712e | openai-domain-verification=dv-1tOOIQB9oBRRCrbGXvQjTJdu | v=spf1 include:spf.protection.outlook.com ip4:185.132.183.52 ip4:212.4.96.83 ip4:185.183.30.110 ip4:91.215.64.147 ip4:212.4.98.26 ip4:212.4.111.188 ip4:54.240.49.120 ip4:54.240.49.121 ip4:212.4.107.191 ip4:212.4.107.20 ip4:212.4.108.179 ip4:212.4.122.120 ip4:212.4.99.138 a:listahm.hmhospitales.com a:listaformacion.hmhospitales.com include:servers.mcsv.net a:servweb01.gnet.es include:_spf.stampymail.com -all |
| TXT | _dmarc.hmhospitales.com | v=DMARC1; p=none; pct=100; rua=mailto:b8699467e2c34f419bca0ae85e2d167c@dmarc-reports.cloudflare.net,mailto:admin@hmhospitales.com; |
| CAA | hmhospitales.com | 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "comodoca.com" | 0 issue "digicert.com; cansignhttpexchanges=yes" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "sectigo.com" | 0 issue "ssl.com" | 0 issuewild "amazon.com" | 0 issuewild "amazonaws.com" | 0 issuewild "amazontrust.com" | 0 issuewild "awstrust.com" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com; cansignhttpexchanges=yes" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "sectigo.com" | 0 issuewild "ssl.com" |
| DS | hmhospitales.com | — |