Digital exposure report
siu.edu
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-17 23:03 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://siu.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://siu.edu/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- siu.edu
- Website request
- GET https://siu.edu/
- Scan time
- 2026-11-17 23:03:13 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 | 0/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 3/15 | The domain's infrastructure lacks basic protections. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.MediumClickjacking protection · Hardening gap+5
- 3.MediumDNSSEC — signed DNS records · Hardening gap+7
- 4.MediumCSP — protection from script injection · Hardening gap+8
- 5.LowCAA — who may issue certificates · Hardening gap+5
- 6.LowX-Content-Type-Options · Hardening gap+4
- 7.LowReferrer-Policy · Hardening gap+3
- 8.LowPermissions-Policy · Hardening gap+2
- 9.LowSoftware version disclosure · Hardening gap
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. 5 of 10 DNS lookups.
v=spf1 a mx ip4:131.230.0.0/16 include:spf.protection.outlook.com include:sendgrid.net include:a._spf.brightspace.com ~all
$ dig +short TXT siu.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; fo=1; rua=mailto:dmarc-rua@siu.edu,mailto:dmarc_agg@vali.email; ruf=mailto:dmarc-ruf@siu.edu
$ dig +short TXT _dmarc.siu.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. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyA+TbnNsw9TcSLj7Mm2TiyZ6akwz…
$ dig +short TXT selector1._domainkey.siu.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.
0 siu-edu.mail.protection.outlook.com
$ dig +short MX siu.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://siu.edu/ returned HTTP 200 (final URL: https://siu.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://siu.edu/
$ curl -sIL https://siu.edu/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 302 → https://siu.edu/
HTTP 302 Location: https://siu.edu/
$ curl -sI http://siu.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: Sectigo, expiring 2027-05-20 (184 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: Sectigo Valid from: 2026-11-03 Valid until: 2027-05-20 Names: *.business.siu.edu, *.siu.edu, portal.siu.edu, siu.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect siu.edu:443 -servername siu.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://siu.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://siu.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://siu.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://siu.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://siu.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://siu.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
Needs attention · Severity: Low · Hardening gap · unscoredThe server discloses its software version, making it easier for attackers to find known vulnerabilities.
Headers with a version number: x-powered-by: PHP/8.3.36, PleskLin. Informational finding, does not affect the score.
server: cloudflare x-powered-by: PHP/8.3.36, PleskLin
$ curl -sIL https://siu.edu/ | grep -iE "^(server|x-powered-by)"
- Hide version numbers in the server settings.
server_tokens off;
Safety: This change is made in your server/CDN settings. Test on staging before production.
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 siu.edu: NODATA
$ dig +short DS siu.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 siu.edu SOA delv siu.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
Needs attention · Severity: Low · Hardening gap · 0/5Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.
No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.
(no CAA records found)
$ dig +short CAA siu.edu
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
siu.edu. CAA 0 issue "letsencrypt.org" siu.edu. CAA 0 iodef "mailto:security@siu.edu"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.
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.
ns5.siu.edu ns4.siu.edu ns1.siu.edu ns3.siu.edu
$ dig +short NS siu.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.03 observed gaps
- NIS2 / vendor due diligence3 observed gaps
- SOC 2 / ISO 27001 baseline5 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 | siu.edu | 131.230.21.130 |
| AAAA | siu.edu | — |
| MX | siu.edu | 0 siu-edu.mail.protection.outlook.com |
| NS | siu.edu | ns5.siu.edu | ns4.siu.edu | ns1.siu.edu | ns3.siu.edu |
| TXT | siu.edu | adobe-idp-site-verification=8e699fe7391a61d469bd007a3295c397905fb566b98db27d355d3483eac0a86e | e2ma-verification=19bbb | MS=ms20230666 | apple-domain-verification=UWcwBIUNhBK-htVraea_MSmuyduELwRhhWx2MFJw2OE | e2ma-verification=702eb | apple-domain-verification=wLe0m12b2Z4EunYa | HoxTnhzvBYZ82oYiTjotA/8BUKC/NJEHjQL5Yvtwo15uaVyH+vsDHa5xmjKxnwtDtJloUn2AHIlLstIoCDWMLg== | v=spf1 a mx ip4:131.230.0.0/16 include:spf.protection.outlook.com include:sendgrid.net include:a._spf.brightspace.com ~all |
| TXT | _dmarc.siu.edu | v=DMARC1; p=quarantine; fo=1; rua=mailto:dmarc-rua@siu.edu,mailto:dmarc_agg@vali.email; ruf=mailto:dmarc-ruf@siu.edu |
| CAA | siu.edu | — |
| DS | siu.edu | — |