Digital exposure report
uhhospitals.org
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-22 21:55 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS uhhospitals.org
- 2.
Limit what your site shares when visitors click links
This reduces how much page address detail is passed to other websites.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://uhhospitals.org/ | grep -i "Referrer-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- uhhospitals.org
- Website request
- GET https://uhhospitals.org/ → https://www.uhhospitals.org/
- Scan time
- 2026-11-22 21:55:34 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 | 30/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 22/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.LowReferrer-Policy · Hardening gap+3
- 3.LowPermissions-Policy · Hardening gap+2
- 4.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. 2 of the 10 allowed DNS lookups.
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:spf_oci.taleo.net -all$ dig +short TXT uhhospitals.org
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; adkim=r; aspf=r; fo=1; pct=100; rf=afrf; ri=3600; rua=mailto:r935346@dc.bmesrv.com,mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
$ dig +short TXT _dmarc.uhhospitals.org
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: k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxsEz1cxmld2dMQ9ifQavpn2xv/FJWtsM… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDe7/sVz3GjFkhJ1UPag0NV+JwbY78ak+SLZk4h…
$ dig +short TXT k1._domainkey.uhhospitals.org
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
4 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mxb-00158002.gslb.pphosted.com 10 mxa-00158002.gslb.pphosted.com 20 mx0a-00158002.pphosted.com 20 mx0b-00158002.pphosted.com
$ dig +short MX uhhospitals.org
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://uhhospitals.org/ returned HTTP 200 (final URL: https://www.uhhospitals.org/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.uhhospitals.org/
$ curl -sIL https://uhhospitals.org/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 307 → https://uhhospitals.org/
HTTP 307 Location: https://uhhospitals.org/
$ curl -sI http://uhhospitals.org/ | grep -iE "^(HTTP|location)"
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: GoDaddy, expiring 2027-05-14 (172 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: GoDaddy Valid from: 2026-10-28 Valid until: 2027-05-14 Names: *.uhhospitals.org, uhhospitals.org Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect uhhospitals.org:443 -servername uhhospitals.org 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
$ curl -sIL https://uhhospitals.org/ | grep -i "Strict-Transport-Security"
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', a broad source (* / https: / data:) — weakens XSS protection.
Content-Security-Policy: worker-src blob: *.uhhospitals.org; default-src 'self' *.uhhs.com data: 'unsafe-inline' 'unsafe-eval' *.uhhospitals.org http://uhlakforceapp04.uhhs.com:8070 *.typekit.net *.siteimproveanalytics.com siteimproveanalytics.com *.bing.com *.youtube.com *.invoca.net s.ytimg.com *.ytimg.com *.facebook.net *.invocacdn.com *.googletagmanager.com *.google-analytics.com *.googleapis.com *.google.com *.facebook.com *.siteimproveanalytics.io *.doubleclick.net *.gstatic.com *.w3.com *.podbean.com *.ads-twitter.com *.twitter.com *.t.co t.co *.alphonso.tv *.calculatestuff.com calculatestuff.com doubleclick.net *.selfcare.info selfcare.info *.digitalmedia.hhs.gov api.digitalmedia.hhs.gov *.appcatalyst.com appcatalyst.com *.staywellsolutionsonline.com staywellsolutionsonline.com *.hhs.gov *.livestream.com livestream.com *.issuu.com issuu.com *.isu.pub isu.pub *.w3.org w3.org *.quantserve.com quantserve.com *.boxcloud.com boxcloud.com *.box.com box.com *.bananatag.com bananatag.com *.alpixtrack.com alpixtrack.com *.adxcel-ec2.com *.data.adxcel-ec2.com data.adxcel-ec2.com adxcel-ec2.com *.cancer.gov cancer.gov *.kramesstaywell.com kramesstaywell.com *.nextdoor.com nextdoor.com *.youtube-nocookie.com youtube-nocookie.com *.licdn.com licdn.com *.stackadapt.com stackadapt.com *.hepdata.com hepdata.com *.jsdelivr.net cdn.jsdelivr.net *.pinimg.com s.pinimg.com *.pinterest.com ct.pinterest.com *.googleoptimize.com *.domo.com domo.com *.marketingcloudapis.com marketingcloudapis.com *.epic.com *.vfpnext.com *.adobedtm.com *.adobedc.net https://adobedc.demdex.net http://edge.adobedc.net https://atlas.microsoft.com *.visualstudio.com atlas.min.js cdnapisec.kaltura.com https://uhhospitals.cdn-v3.conductrics.com https://sqs.us-east-2.amazonaws.com https://uhhospitals.conductrics.com *.azurewebsites.net; frame-ancestors 'self' *.uhhospitals.org *.uhhs.com;
$ curl -sIL https://uhhospitals.org/ | 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' *.uhhospitals.org *.uhhs.com
X-Frame-Options: sameorigin CSP frame-ancestors: 'self' *.uhhospitals.org *.uhhs.com
$ curl -sIL https://uhhospitals.org/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://uhhospitals.org/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://uhhospitals.org/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
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://uhhospitals.org/ | 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://uhhospitals.org/ | 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 uhhospitals.org: NODATA
$ dig +short DS uhhospitals.org
- 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 uhhospitals.org SOA delv uhhospitals.org
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 "digicert.com" | 0 issue "godaddy.com" | 0 iodef "\"mailto:itinformationsecurity@uhhospitals.org\"" | 0 issue "amazon.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "amazonaws.com" | 0 issue "pki.goog"
0 issue "digicert.com" 0 issue "godaddy.com" 0 iodef "\"mailto:itinformationsecurity@uhhospitals.org\"" 0 issue "amazon.com" 0 issue "amazontrust.com" 0 issue "awstrust.com" 0 issue "amazonaws.com" 0 issue "pki.goog"
$ dig +short CAA uhhospitals.org
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
ns1-06.azure-dns.com ns2-06.azure-dns.net ns3-06.azure-dns.org ns4-06.azure-dns.info
$ dig +short NS uhhospitals.org
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 rulesNo gaps observed
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline1 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 | uhhospitals.org | 150.171.109.114 |
| AAAA | uhhospitals.org | — |
| MX | uhhospitals.org | 10 mxb-00158002.gslb.pphosted.com | 10 mxa-00158002.gslb.pphosted.com | 20 mx0a-00158002.pphosted.com | 20 mx0b-00158002.pphosted.com |
| NS | uhhospitals.org | ns1-06.azure-dns.com | ns2-06.azure-dns.net | ns3-06.azure-dns.org | ns4-06.azure-dns.info |
| TXT | uhhospitals.org | v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:spf_oci.taleo.net -all | twilio-domain-verification=2ac0555233fc96240f4d95edd1a04e82 | google-site-verification=riFP-o0ZyFCt4iePlB7J6o6zjDJ3bc5NqVkiQAiAQcM | google-site-verification=zInPOGJxxqieeM5_iFMkS7QGKZks5AQC2qnB6Lm2mO4 |
| TXT | _dmarc.uhhospitals.org | v=DMARC1; p=reject; adkim=r; aspf=r; fo=1; pct=100; rf=afrf; ri=3600; rua=mailto:r935346@dc.bmesrv.com,mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com |
| CAA | uhhospitals.org | 0 issue "digicert.com" | 0 issue "godaddy.com" | 0 iodef "\"mailto:itinformationsecurity@uhhospitals.org\"" | 0 issue "amazon.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "amazonaws.com" | 0 issue "pki.goog" |
| DS | uhhospitals.org | — |