Digital exposure report
umw.edu
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-20 07:34 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
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://umw.edu/ | grep -i "Strict-Transport-Security"
- 2.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://umw.edu/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- umw.edu
- Website request
- GET https://umw.edu/ → https://www.umw.edu/
- Scan time
- 2026-11-20 07:34:46 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 | 18/25 | Encryption is in place, but a gap could expose users. |
| Browser protections | 0/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.MediumClickjacking protection · Hardening gap+5
- 4.MediumDNSSEC — signed DNS records · Hardening gap+7
- 5.MediumCSP — protection from script injection · Hardening gap+8
- 6.LowX-Content-Type-Options · Hardening gap+4
- 7.LowReferrer-Policy · Hardening gap+3
- 8.LowPermissions-Policy · Hardening gap+2
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 mx ip4:199.111.84.0/24 ip4:199.111.138.184 include:spf.elluciancloud.com include:_spf.elasticemail.com include:_spf.salesforce.com include:spf.protection.outlook.com include:_spf.messagegears.net -all
$ dig +short TXT umw.edu
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;rua=mailto:dmarc@umw.edu;ruf=mailto:dmarc@umw.edu;fo=1;
$ dig +short TXT _dmarc.umw.edu
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, k1, s1, s2, dkim. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzo2btYAMgFezPquei79yM48NHt4343onw… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6MadGUA/kpBbAKtv7FEvNcPB5o/Ub0Df… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC94lVsoH+FSl28MKwfyiiLnJH+iXYlf9TYmygD… dkim._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAucT5I4itufYJ0CQvqFe/7brug9Zk…
$ dig +short TXT selector1._domainkey.umw.edu
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 mx2.hc3757-75.iphmx.com 10 mx1.hc3757-75.iphmx.com
$ dig +short MX umw.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://umw.edu/ returned HTTP 200 (final URL: https://www.umw.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.umw.edu/
$ curl -sIL https://umw.edu/
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://umw.edu/ returned HTTP 301 without redirecting to https:// (Location: http://www.umw.edu/).
HTTP 301 Location: http://www.umw.edu/
$ curl -sI http://umw.edu/ | 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 umw.edu www.umw.edu;
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: DigiCert, expiring 2027-03-20 (120 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: DigiCert Valid from: 2026-02-17 Valid until: 2027-03-20 Names: *.umw.edu, access.umw.edu, amg1.umw.edu, amg2.umw.edu, archive.umw.edu, at.umw.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect umw.edu:443 -servername umw.edu 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://umw.edu/ | 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
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://umw.edu/ | 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
Failed · Severity: Medium · Hardening gap · 0/5Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.
No valid X-Frame-Options and no frame-ancestors in the CSP.
X-Frame-Options: (missing)
$ curl -sIL https://umw.edu/ | grep -i "X-Frame-Options"
- Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
- Also set frame-ancestors in the CSP — the modern alternative.
/* X-Frame-Options: SAMEORIGIN
Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.
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://umw.edu/ | 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
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://umw.edu/ | 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://umw.edu/ | 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: WP Engine
$ curl -sIL https://umw.edu/ | 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 umw.edu: NODATA
$ dig +short DS umw.edu
- 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 umw.edu SOA delv umw.edu
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 "godaddy.com" | 0 issuewild "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "digicert.com" | 0 issue "amazon.com"
0 issue "godaddy.com" 0 issuewild "digicert.com" 0 issue "letsencrypt.org" 0 issue "digicert.com" 0 issue "amazon.com"
$ dig +short CAA umw.edu
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
5 NS servers.
ns1.dnsmadeeasy.com ns3.dnsmadeeasy.com ns2.dnsmadeeasy.com ns0.dnsmadeeasy.com ns4.dnsmadeeasy.com
$ dig +short NS umw.edu
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.04 observed gaps
- NIS2 / vendor due diligence2 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 | umw.edu | 141.193.213.10 | 141.193.213.11 |
| AAAA | umw.edu | — |
| MX | umw.edu | 10 mx2.hc3757-75.iphmx.com | 10 mx1.hc3757-75.iphmx.com |
| NS | umw.edu | ns1.dnsmadeeasy.com | ns3.dnsmadeeasy.com | ns2.dnsmadeeasy.com | ns0.dnsmadeeasy.com | ns4.dnsmadeeasy.com |
| TXT | umw.edu | ZOOM_verify_21VbxhkXHjikV8U8Z1rTPv | 4d0702a1afba4acdb8577a963e9e21a9 | MS=0F9DD86E72C6C8CFA9AE26FCE9A790525D4670F2 | google-site verification=BGz1sU2mb3P9DWJqgV4s5lcNE3KkvpEuIzPa3kLGNf | 7tm70u00kl36vev8e5e89mm6p1 | google-site-verification=mntU7qznfNCM9YqtozRFZtaPIYKe74MhnZhFLk1GEnc | atlassian-domain-verification=T6HIN9qGGliDKBjmp3e4h3Q0bxAQiYFgSguKyt1a51puu4xza/Y21KncMpcIhRv0 | apple-domain-verification=Y6T1cd23DaEl6Fl0 | ul147dvik283s61afqc4cvv0iv | _026gn7kzh8egonvak1k9fcrxakre5pl | MS=ms66746817 | j4670o3c106vi9qjddss3mh046 | uj9e3k3pjfaddprehasdnjeonb | _npkdnsbh0glz4mdx842quj9uam8spj4 | jamf-site-verification=s8mQ9Jlj2NVtUJrxvl0yGw | include:_spf.messagegears.net | 8hkdtdv43q39294tr5wwgzxrhst77nzm | atlassian-sending-domain-verification=2bc6293c-b594-4001-842d-13f3521627a0 | LSO/wakGntDLUF5D0BIjtCHB80uHFkXEgZGdj46lP98uCcIfoBvUspU0ku2f771t3Lk0rkZrvv7K8x7tZb/t2w== | v=spf1 mx ip4:199.111.84.0/24 ip4:199.111.138.184 include:spf.elluciancloud.com include:_spf.elasticemail.com include:_spf.salesforce.com include:spf.protection.outlook.com include:_spf.messagegears.net -all |
| TXT | _dmarc.umw.edu | v=DMARC1;p=reject;rua=mailto:dmarc@umw.edu;ruf=mailto:dmarc@umw.edu;fo=1; |
| CAA | umw.edu | 0 issue "godaddy.com" | 0 issuewild "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "digicert.com" | 0 issue "amazon.com" |
| DS | umw.edu | — |