Digital exposure report
rush.edu
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-20 07:34 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
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://rush.edu/ | grep -i "Content-Security-Policy"
- 2.
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 rush.edu
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- rush.edu
- Website request
- GET https://rush.edu/ → https://www.rush.edu/
- Scan time
- 2026-11-20 07:34:31 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 | 27/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 | 16/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.MediumCSP — protection from script injection · Hardening gap+8
- 3.LowReferrer-Policy · Hardening gap+3
- 4.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 1 of 10 DNS lookups.
v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all$ dig +short TXT rush.edu
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1; p=quarantine; sp=quarantine; adkim=s; aspf=s; rua=mailto:dmarc_agg@vali.email; fo=1
$ dig +short TXT _dmarc.rush.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, selector2, k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0T6CmOoCaX62iDRucqnoqA9CPkt8… selector2._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoTXrOPV45+2a6YSb1ayefEvez4uN… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAy3RN/ylJCkzstZMk8dfVQWVj4x4pzUrp… s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1fB9CYsNX8WsR4yLlsHwfvt83jM3Hnwv…
$ dig +short TXT selector1._domainkey.rush.edu
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 rush-edu.mail.protection.outlook.com
$ dig +short MX rush.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://rush.edu/ returned HTTP 200 (final URL: https://www.rush.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.rush.edu/
$ curl -sIL https://rush.edu/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://www.rush.edu/
HTTP 301 Location: https://www.rush.edu/
$ curl -sI http://rush.edu/ | 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: DigiCert, expiring 2027-06-04 (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: DigiCert Valid from: 2026-11-18 Valid until: 2027-06-04 Names: rudv-expe-mra1.rush.edu, rudv-expe-mra3.rush.edu, rudv-expe-mra5.rush.edu, rupv-expe-mra2.rush.edu, rupv-expe-mra4.rush.edu, rupv-expe-mra6.rush.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect rush.edu:443 -servername rush.edu 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 7/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000
$ curl -sIL https://rush.edu/ | grep -i "Strict-Transport-Security"
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://rush.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
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://rush.edu/ | 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://rush.edu/ | 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://rush.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://rush.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: (missing)
$ curl -sIL https://rush.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 rush.edu: NODATA
$ dig +short DS rush.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 rush.edu SOA delv rush.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 issue "digicert.com"
0 issue "godaddy.com" 0 issue "digicert.com"
$ dig +short CAA rush.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.
3 NS servers.
ns3.rush.edu ns2.rush.edu ns1.rush.edu
$ dig +short NS rush.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.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 | rush.edu | 3.233.48.238 |
| AAAA | rush.edu | — |
| MX | rush.edu | 10 rush-edu.mail.protection.outlook.com |
| NS | rush.edu | ns3.rush.edu | ns2.rush.edu | ns1.rush.edu |
| TXT | rush.edu | 85ep78ajrolefpf3q47b7fqgb3 | cnnuuq798f19mbk54qodglo8t3 | smartsheet-site-validation=0oKA9ogxO3yVj91f9r6X-lpd5HyAPYuM | ms-domain-verification=6046947f-17be-45d8-b43e-3e89b6e606b8 | jamf-site-verification=47DFOMVJgIhkqOQ_QO5ZkA | m7k3q8rkkv8h8cat7vjrfkqn39 | dohv2hp6uujub0rem2tom39rcq | 4elveene03mfvubfuui3o3vh2c | 4e0ad44a79f83c8738192ed716f9211eec17f1f6c8f0cffb98f9c6fdd40e6de2 | 32b921d298d540d35691ff9e02607e3c72e790bc8f79536e76be5bffefd3907a | 607e9203ccc6ac2d5728cc40d1a91b5ce9d9405f9db07237e6ee96633bdeee93 | 64ktvg7pe5d05n4vhf4p60csjs | r2qt37fvo4ri3n50r9qpcv10aj | n6ej77obogdrqbj3pan784srk | m86gbe2uqpkrfpsneliusd3spg | MS=ms65548421 | google-site-verification=MeMQ3R0_dYCbTQ5mSFTZBrUb7qVe-mAEdgZqQ45xUmE | docusign=2b154078-a374-44b9-80eb-3ed4844f9996 | ciscodomainverification=6d08dd3819832b0ae877b9a61d4431a329c3b8ea57795aea465e2ecf50936726 | Dynatrace-site-verification=a4b674a5-958c-4915-b3ba-5b9b847d720f__j9omvducaea6bj09o92l8m61tj | dropbox-domain-verification=0jmvqs54cen0 | amazonses:r8H9k0A9i2XiHuRAaxhAUwHo4wTj2s9lkx5T7MQ1TF4= | PcBeZBbpEsya+hLtQy8qOrXGYF1pTPtj05ai8/v6Jq8jE4eyDLP+gTP2uM5E7FsDC5UF+3hwcDOEK4pNwBWZqg== | webexdomainverification.4C675B893785B136E053AB06FC0A3F65=0b8e7b63-dc14-4ea4-a8cf-e6cfbe9181ce | atlassian-domain-verification=ZFt4hJKcI0zGaQXKRyk8hS5U/BOUUizKOdO5GJEh0xgy24iemrdmgF0Ajwh/Xf7w | v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all | apple-domain-verification=IrTapCe7mquOjgSd | ms-domain-verification=f2031ab0-4b94-4b87-ad54-060ec084aea0 | duo_sso_verification=QuH8MTGXPH5x16hKlAaqbBdkeU42x7dFtafmUYAUqo0L8eggmGF1nhZwhqhncXtT | VURh8leuerwuQQenfZd0H5/35EJOqC4cqxuovhZ2eYluPcTVhBvokjuc7CzttxDlM5T+KQVZ7C7/BfZbknwd9w== | ms-domain-verification=9ac8e8dc-ce68-4fa7-b562-85b0acd998f3 | kkmcucbdrunfq0sqe4haeekk9k | e12kct51ehnvpd7vo4q28kd1ik | e55m09kgkvkb98j4oftb891j7f |
| TXT | _dmarc.rush.edu | v=DMARC1; p=quarantine; sp=quarantine; adkim=s; aspf=s; rua=mailto:dmarc_agg@vali.email; fo=1 |
| CAA | rush.edu | 0 issue "godaddy.com" | 0 issue "digicert.com" |
| DS | rush.edu | — |