Digital exposure report
washjeff.edu
Low exposure. The domain is well protected in most areas checked.
Scanned: 2026-11-22 15:02 UTC
Partial coverage: the score is based on 52% of applicable check weight. 8 unverified check(s) are excluded, not counted as failures.
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.washjeff.edu
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- washjeff.edu
- Website request
- GET https://washjeff.edu/ → https://www.washjeff.edu/
- Scan time
- 2026-11-22 15:02:46 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- HTTPS available · Unverified
- SSL/TLS certificate validity · Unverified
- HSTS — enforce encryption in the browser · Unverified
- CSP — protection from script injection · Unverified
- Clickjacking protection · Unverified
- X-Content-Type-Options · Unverified
- Referrer-Policy · Unverified
- Permissions-Policy · Unverified
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 | 7/7 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | — | Nothing in this category could be verified from public data. |
| DNS infrastructure | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.LowDMARC — anti-spoofing policy · Hardening gap+6
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- HTTPS available
- SSL/TLS certificate validity
- CSP — protection from script injection
- HSTS — enforce encryption in the browser
- Clickjacking protection
- X-Content-Type-Options
- Referrer-Policy
- Permissions-Policy
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. 1 of the 10 allowed DNS lookups.
v=spf1 include:_s00686267.autospf.email -all
$ dig +short TXT washjeff.edu
DMARC — anti-spoofing policy
Needs attention · Severity: Low · Hardening gap · 12/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject. No rua — no reports on spoofing attempts are received.
v=DMARC1; p=quarantine
$ dig +short TXT _dmarc.washjeff.edu
- Keep your current p=quarantine enforcement and edit the existing record in place — do not replace it with p=none.
- Add rua=mailto:… to the existing record so you receive aggregate reports. Nothing else changes.
- Optional: once reports show all legitimate senders pass, move from p=quarantine to p=reject.
_dmarc.washjeff.edu. TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@washjeff.edu"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Your domain already enforces DMARC. Edit the record in place; never roll back to p=none.
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: selector2, s1, s2, dkim. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector2._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJKhmKwP0sdfd9c9wgj7lS1eNo9KDDkRA3… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1CJ6+q+N264DhEGxi92ISXCkZT+f06yc… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDTUzQVpQ1SATUnikEo0S3AEJl3+2Q5ygaEhH44… dkim._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDfFCs0/3chQvfHLJLO609FtJtvc/CtMrTNbFY+oZaN5…
$ dig +short TXT selector2._domainkey.washjeff.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 washjeff-edu.mail.protection.outlook.com
$ dig +short MX washjeff.edu
HTTPS available
Unverified · Severity: OK · Not scoredHTTPS couldn't be confirmed: the request timed out or the connection failed. This isn't treated as a security failure.
Requesting https://washjeff.edu/ didn't complete (HTTP 526). Timeouts and transport errors may be transient; the check is excluded from the score.
HTTP 526
$ curl -svI https://washjeff.edu/ 2>&1 | grep -E "SSL|HTTP|expire"
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://washjeff.edu/
HTTP 301 Location: https://washjeff.edu/
$ curl -sI http://washjeff.edu/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Unverified · Severity: OK · Not scoredThe certificate couldn't be checked live because the HTTPS connection didn't complete. CT log data alone isn't used to score validity or expiry.
No live TLS evidence was obtained. CT entries are shown as context only. Not scored.
CT logs (context only, not scored): Issuer: Sectigo Valid from: 2026-09-06 Valid until: 2027-03-23 Names: *.washjeff.edu, washjeff.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect washjeff.edu:443 -servername washjeff.edu 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://washjeff.edu/
CSP — protection from script injection
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Clickjacking protection
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://washjeff.edu/
X-Content-Type-Options
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Referrer-Policy
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Permissions-Policy
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://washjeff.edu/
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec washjeff.edu | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "digicert.com" | 0 issue "entrust.net" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "microsoft.com" | 0 issue "sectigo.com" | 0 issue "ssl.com" | 0 issue "ssladmin.microsoft.com" | 0 issuewild "sectigo.com" | 0 issuewild "ssl.com"
0 issue "amazon.com" 0 issue "amazonaws.com" 0 issue "amazontrust.com" 0 issue "awstrust.com" 0 issue "digicert.com" 0 issue "entrust.net" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issue "microsoft.com" 0 issue "sectigo.com" 0 issue "ssl.com" 0 issue "ssladmin.microsoft.com" 0 issuewild "sectigo.com" 0 issuewild "ssl.com"
$ dig +short CAA washjeff.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.
4 NS servers.
ns1-33.azure-dns.com ns2-33.azure-dns.net ns3-33.azure-dns.org ns4-33.azure-dns.info
$ dig +short NS washjeff.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.05 unverified
- NIS2 / vendor due diligence1 observed gaps · 3 unverified
- SOC 2 / ISO 27001 baseline1 observed gaps · 6 unverified
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 | washjeff.edu | 52.205.26.198 |
| AAAA | washjeff.edu | 2620:37:c000:91:209:131:91:158 |
| MX | washjeff.edu | 0 washjeff-edu.mail.protection.outlook.com |
| NS | washjeff.edu | ns1-33.azure-dns.com | ns2-33.azure-dns.net | ns3-33.azure-dns.org | ns4-33.azure-dns.info |
| TXT | washjeff.edu | 70v075r9lc78ob0h5tutu2ltk1 | ZOOM_verify_smT4l4qdQ-qmvD2t7ihSig | ca3-f60f306e423c437ca787fc8f7e42f01b | apple-domain-verification=bz08ITOFBgj3PVTq | v=spf1 include:_s00686267.autospf.email -all | jamf-site-verification=kjhPH-Np7LtpqCONa37krg | 1password-site-verification=JNCBUT7IJZDWZGJRKRYCSANT4Y | adobe-idp-site-verification=045007c8-dc20-477d-8a63-ec02aed7d1d3 | google-site-verification=3PJGHAzVC2_pmlFh7mar_x0GKslFNUNAcTFY-cx3GQA | duo_sso_verification=CLpMVFJNHT3HcaKHpKVshlshLenJCjBFbPbTFVeQx9wdrwXD1cpQ3VN6d6nRD5En | 6rDC0B89LFyTR9n6fo2OBvmwn+/rKy/tdiKZbvm+HUQ0t5rrI6J2W+swTwoan5ftiBp9G0WTDXMZ/SmpVQUMRQ== | MFdPxVCEEyiRswar2WO5EOhISXLBkPv+qumhtsUgXN/jxqbPoAG3qkJFzzIPbW3k/VYFV40lSJ41grxHvurF1w== |
| TXT | _dmarc.washjeff.edu | v=DMARC1; p=quarantine |
| CAA | washjeff.edu | 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "digicert.com" | 0 issue "entrust.net" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "microsoft.com" | 0 issue "sectigo.com" | 0 issue "ssl.com" | 0 issue "ssladmin.microsoft.com" | 0 issuewild "sectigo.com" | 0 issuewild "ssl.com" |
| DS | washjeff.edu | 61275 13 2 99ceea56583bf30142fdee2c75d6f53f1f59a9bf73f5795ddec9da89213136f8 |