Back to results

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.

A
94/100

What to do first

  1. 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 security27/30Spoofing email from this domain is hard.
Encryption & certificate7/7Traffic to the site is encrypted and the certificate is valid.
Browser protections—Nothing in this category could be verified from public data.
DNS infrastructure15/15The domain's infrastructure is well hardened.

Fix priorities

  1. 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/10

An authorized sender list is defined and mail from other servers is rejected.

Valid SPF record with -all. 1 of the 10 allowed DNS lookups.

Source data: DNS TXT washjeff.edu
v=spf1 include:_s00686267.autospf.email -all
$ dig +short TXT washjeff.edu
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Needs attention · Severity: Low · Hardening gap · 12/15

Forged 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.

Source data: DNS TXT _dmarc.washjeff.edu
v=DMARC1; p=quarantine
$ dig +short TXT _dmarc.washjeff.edu
Fix recommendation (effort: Easy)
  1. Keep your current p=quarantine enforcement and edit the existing record in place — do not replace it with p=none.
  2. Add rua=mailto:… to the existing record so you receive aggregate reports. Nothing else changes.
  3. 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.

Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A 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.

Source data: DNS TXT <selector>._domainkey.washjeff.edu
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
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail 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.

Source data: DNS MX washjeff.edu
0 washjeff-edu.mail.protection.outlook.com
$ dig +short MX washjeff.edu
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Unverified · Severity: OK · Not scored

HTTPS 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.

Source data: HTTPS GET https://washjeff.edu/
HTTP 526
$ curl -svI https://washjeff.edu/ 2>&1 | grep -E "SSL|HTTP|expire"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Passed · Severity: OK · 7/7

Visitors arriving at an unencrypted address are automatically sent to the secure version.

HTTP 301 → https://washjeff.edu/

Source data: HTTP GET http://washjeff.edu/ (redirects not followed)
HTTP 301
Location: https://washjeff.edu/
$ curl -sI http://washjeff.edu/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Unverified · Severity: OK · Not scored

The 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.

Source data: Certificate Transparency logs (certspotter) for washjeff.edu
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
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Unverified · Severity: OK · Not scored

Couldn'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.

Source data: Response headers from https://www.washjeff.edu/
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Unverified · Severity: OK · Not scored

Couldn'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.

Source data: Response headers from https://www.washjeff.edu/
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Unverified · Severity: OK · Not scored

Couldn'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.

Source data: Response headers from https://www.washjeff.edu/
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Unverified · Severity: OK · Not scored

Couldn'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.

Source data: Response headers from https://www.washjeff.edu/
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Unverified · Severity: OK · Not scored

Couldn'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.

Source data: Response headers from https://www.washjeff.edu/
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Unverified · Severity: OK · Not scored

Couldn'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.

Source data: Response headers from https://www.washjeff.edu/
No HTTPS response received
$ curl -sIL https://washjeff.edu/
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Passed · Severity: OK · 7/7

The domain's records are digitally signed and hard to forge.

An AD (Authenticated Data) flag was returned by a validating resolver.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = true
$ dig +dnssec washjeff.edu | grep -E "flags:.* ad"
Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Passed · Severity: OK · 5/5

Only 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"

Source data: DNS 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"
$ dig +short CAA washjeff.edu
Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

4 NS servers.

Source data: DNS NS washjeff.edu
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
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

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

Awashjeff.edu52.205.26.198
AAAAwashjeff.edu2620:37:c000:91:209:131:91:158
MXwashjeff.edu0 washjeff-edu.mail.protection.outlook.com
NSwashjeff.eduns1-33.azure-dns.com | ns2-33.azure-dns.net | ns3-33.azure-dns.org | ns4-33.azure-dns.info
TXTwashjeff.edu70v075r9lc78ob0h5tutu2ltk1 | 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.eduv=DMARC1; p=quarantine
CAAwashjeff.edu0 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"
DSwashjeff.edu61275 13 2 99ceea56583bf30142fdee2c75d6f53f1f59a9bf73f5795ddec9da89213136f8
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain