Digital exposure report
saic.edu
High exposure. Significant weaknesses put the brand, customers and email at risk.
Scanned: 2026-11-17 23:03 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.saic.edu
- 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://saic.edu/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- saic.edu
- Website request
- GET https://saic.edu/ → https://www.saic.edu/
- Scan time
- 2026-11-17 23:03:12 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 | 19/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| 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.MediumHSTS — enforce encryption in the browser · Hardening gap+4
- 2.MediumDMARC — anti-spoofing policy · Hardening gap+10
- 3.MediumDNSSEC — signed DNS records · Hardening gap+7
- 4.MediumCSP — protection from script injection · Hardening gap+8
- 5.LowReferrer-Policy · Hardening gap+3
- 6.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. 2 of 10 DNS lookups.
v=spf1 include:_spf.google.com include:mktomail.com ip4:54.219.145.149 ip4:34.194.230.233 ip4:34.230.107.215 ip4:184.106.13.89 ip4:198.40.30.0/23 ip4:198.40.24.0/22 ~all
$ dig +short TXT saic.edu
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; rua=mailto:e3kth4aw@ag.us.dmarcian.com; ruf=mailto:e3kth4aw@fr.us.dmarcian.com; fo=1
$ dig +short TXT _dmarc.saic.edu
- 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.saic.edu. TXT "v=DMARC1; p=none; rua=mailto:dmarc@saic.edu; 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: google. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAjyu3IBwqzfYolzcmFuLvJSsw1NLU…
$ dig +short TXT google._domainkey.saic.edu
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
$ dig +short MX saic.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://saic.edu/ returned HTTP 200 (final URL: https://www.saic.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.saic.edu/
$ curl -sIL https://saic.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.saic.edu/
HTTP 301 Location: https://www.saic.edu/
$ curl -sI http://saic.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: Let's Encrypt, expiring 2027-01-31 (74 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: Let's Encrypt Valid from: 2026-11-02 Valid until: 2027-01-31 Names: *.saic.edu, saic.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect saic.edu:443 -servername saic.edu 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Needs attention · Severity: Medium · Hardening gap · 4/8Encryption enforcement is set for too short a time.
max-age=300 (0 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=300
$ curl -sIL https://saic.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://saic.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://saic.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://saic.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://saic.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://saic.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://saic.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 saic.edu: NODATA
$ dig +short DS saic.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 saic.edu SOA delv saic.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: 128 issue "trustwave.com" | 128 issue "Digicert.com" | 128 issue "awstrust.com" | 128 issue "godaddy.com" | 0 iodef "mailto:networkservices@artic.edu" | 128 issue "letsencrypt.org" | 128 issuewild "letsencrypt.org"
128 issue "trustwave.com" 128 issue "Digicert.com" 128 issue "awstrust.com" 128 issue "godaddy.com" 0 iodef "mailto:networkservices@artic.edu" 128 issue "letsencrypt.org" 128 issuewild "letsencrypt.org"
$ dig +short CAA saic.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.
2 NS servers.
ns2.artic.edu ns1.artic.edu
$ dig +short NS saic.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 rules1 observed gaps
- PCI DSS v4.02 observed gaps
- NIS2 / vendor due diligence3 observed gaps
- SOC 2 / ISO 27001 baseline3 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 | saic.edu | 198.40.30.252 |
| AAAA | saic.edu | — |
| MX | saic.edu | 1 aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 5 alt2.aspmx.l.google.com | 10 alt3.aspmx.l.google.com | 10 alt4.aspmx.l.google.com |
| NS | saic.edu | ns2.artic.edu | ns1.artic.edu |
| TXT | saic.edu | docusign=293fa742-7036-4f7b-bfaa-76a362b8e7d9 | docusign=e0ec11cb-c6e9-4042-b2ab-c4c6dda0d13f | 5ee7c892-cc92-4cf5-9206-f8744ca85baf | google-site-verification=xMcUDmJIoDLmJQ47nibPDbE8OM5N_ENeloFTeNbzXq4 | logmein-verification-code=9a8f022b-d164-4735-8a58-c0b914a60d09 | airtable-verification=ef78f98e8d4fdff2de2c65048193b7b5 | SFMC-nBxS3aNN0QOnARnw7dBR0ib_62-uf4nSdLabFol- | SFMC-_Tph2QUf89Ze0cgwYu0hZ8uPpAY6czxKtkABSxxC | asv=ab3c4901e489d69169de1f00e86a42a7 | v=spf1 include:_spf.google.com include:mktomail.com ip4:54.219.145.149 ip4:34.194.230.233 ip4:34.230.107.215 ip4:184.106.13.89 ip4:198.40.30.0/23 ip4:198.40.24.0/22 ~all | MS=ms30397306 | adobe-idp-site-verification=a08447d9-f7df-43e1-a4ed-29adc0e806f6 |
| TXT | _dmarc.saic.edu | v=DMARC1; p=none; rua=mailto:e3kth4aw@ag.us.dmarcian.com; ruf=mailto:e3kth4aw@fr.us.dmarcian.com; fo=1 |
| CAA | saic.edu | 128 issue "trustwave.com" | 128 issue "Digicert.com" | 128 issue "awstrust.com" | 128 issue "godaddy.com" | 0 iodef "mailto:networkservices@artic.edu" | 128 issue "letsencrypt.org" | 128 issuewild "letsencrypt.org" |
| DS | saic.edu | — |