Back to results

Digital exposure report

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

F
39/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.sckans.edu
  2. 2.

    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://sckans.edu/ | grep -i "Strict-Transport-Security"

A starting point, not a security guarantee.

What this grade means

Tested hostname
sckans.edu
Website request
GET https://sckans.edu/
Scan time
2026-11-17 23:03:14 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 security18/30Spoofing email in the company's name is possible in some cases.
Encryption & certificate18/25Encryption is in place, but a gap could expose users.
Browser protections0/30Several browser hardening headers are missing, which removes layers of protection against script injection and framing.
DNS infrastructure3/15The domain's infrastructure lacks basic protections.

Fix priorities

  1. 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
  2. 2.HighHTTP → HTTPS redirect · Hardening gap+7
  3. 3.MediumClickjacking protection · Hardening gap+5
  4. 4.MediumDMARC — anti-spoofing policy · Hardening gap+11
  5. 5.MediumDNSSEC — signed DNS records · Hardening gap+7
  6. 6.MediumCSP — protection from script injection · Hardening gap+8
  7. 7.LowCAA — who may issue certificates · Hardening gap+5
  8. 8.LowX-Content-Type-Options · Hardening gap+4
  9. 9.LowReferrer-Policy · Hardening gap+3
  10. 10.LowPermissions-Policy · Hardening gap+2

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 9/10

An authorized sender list is defined; mail from other servers is flagged as suspicious.

~all (softfail) — acceptable when combined with enforced DMARC. 7 of 10 DNS lookups.

Source data: DNS TXT sckans.edu
v=spf1 ip4:40.138.72.24 ip4:40.138.72.33 include:mh.blackboard.com include:spf.protection.outlook.com include:_spf.regroup.com include:_spf.salesforce.com include:cust-spf.cashnet.com include:amazonses.com include:secure.giftlegacy.com ~all
$ dig +short TXT sckans.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: Medium · Hardening gap · 4/15

DMARC is in monitoring mode only — forged email still reaches recipients.

Policy p=none. p=none collects reports but does not protect. No rua — no reports on spoofing attempts are received.

Source data: DNS TXT _dmarc.sckans.edu
v=DMARC1; p=none; adkim=r; aspf=r;
$ dig +short TXT _dmarc.sckans.edu
Fix recommendation (effort: Medium)
  1. Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
  2. Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
  3. Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.sckans.edu.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@sckans.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.

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: selector1, selector2, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.sckans.edu
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAy3tl/DS1jfgc49F2sj3i0ERK4JTs…
selector2._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0lluEY/XzS3SS/eF52hTXknm1jtg…
s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA61pkH27njAql2zE+T9cmOA6BnAEvwrQM…
s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw/bX2xvCjKjr/2T7BRGXEtuAQ0uE/7Mz…
$ dig +short TXT selector1._domainkey.sckans.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 sckans.edu
0 sckans-edu.mail.protection.outlook.com
$ dig +short MX sckans.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

Passed · Severity: OK · 10/10

The site loads over an encrypted connection.

https://sckans.edu/ returned HTTP 200 (final URL: https://sckans.edu/). Client-side certificate validation passed.

Source data: HTTPS GET https://sckans.edu/
HTTP 200
Final URL: https://sckans.edu/
$ curl -sIL https://sckans.edu/
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

Failed · Severity: High · Hardening gap · 0/7

The site is also reachable over an unencrypted connection, so data may travel in plain text on public networks.

http://sckans.edu/ returned HTTP 200 without redirecting to https://.

Source data: HTTP GET http://sckans.edu/ (redirects not followed)
HTTP 200
Location: (none)
$ curl -sI http://sckans.edu/ | grep -iE "^(HTTP|location)"
Fix recommendation (effort: Easy)
  1. Set up a permanent (301) redirect from every HTTP request to HTTPS on the server or CDN.
  2. Then add an HSTS header.
server {
  listen 80;
  server_name sckans.edu www.sckans.edu;
  return 301 https://$host$request_uri;
}

Safety: This change is made on your server. Make sure HTTPS works first, otherwise the site won't load.

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

Passed · Severity: OK · 8/8

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. Latest issuance in CT logs: GoDaddy, expiring 2027-01-22 (65 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.

Source data: Certificate Transparency logs (certspotter) for sckans.edu
Live TLS handshake: certificate accepted
CT logs (context only, not scored):
Issuer: GoDaddy
Valid from: 2026-07-08
Valid until: 2027-01-22
Names: *.sckans.edu, sckans.edu
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect sckans.edu:443 -servername sckans.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

Failed · Severity: High · Hardening gap · 0/8

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

Source data: Response headers from https://sckans.edu/
Strict-Transport-Security: (missing)
$ curl -sIL https://sckans.edu/ | grep -i "Strict-Transport-Security"
Fix recommendation (effort: Easy)
  1. Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
  2. Gradually raise it to 31536000 (one year) and add includeSubDomains.
  3. 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.

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

Failed · Severity: Medium · Hardening gap · 0/8

Missing Content-Security-Policy header: this removes one layer of protection against script injection.

No Content-Security-Policy header found.

Source data: Response headers from https://sckans.edu/
Content-Security-Policy: (missing)
$ curl -sIL https://sckans.edu/ | grep -i "Content-Security-Policy"
Fix recommendation (effort: Complex)
  1. First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
  2. Collect violations for a week or two and tune the policy to your legitimate sources.
  3. 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.

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

Failed · Severity: Medium · Hardening gap · 0/5

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

Source data: Response headers from https://sckans.edu/
X-Frame-Options: (missing)
$ curl -sIL https://sckans.edu/ | grep -i "X-Frame-Options"
Fix recommendation (effort: Easy)
  1. Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
  2. 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.

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

Failed · Severity: Low · Hardening gap · 0/4

The browser may interpret files as code unintentionally.

Missing X-Content-Type-Options: nosniff header (MIME sniffing).

Source data: Response headers from https://sckans.edu/
X-Content-Type-Options: (missing)
$ curl -sIL https://sckans.edu/ | grep -i "X-Content-Type-Options"
Fix recommendation (effort: Easy)
  1. 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.

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

Failed · Severity: Low · Hardening gap · 0/3

Internal URLs (including parameters) may leak to external sites.

Referrer-Policy is missing; the browser will use its default.

Source data: Response headers from https://sckans.edu/
Referrer-Policy: (missing)
$ curl -sIL https://sckans.edu/ | grep -i "Referrer-Policy"
Fix recommendation (effort: Easy)
  1. 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.

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

Needs attention · Severity: Low · Hardening gap · 0/2

Access to sensitive features like the camera and location isn't restricted.

Missing Permissions-Policy header.

Source data: Response headers from https://sckans.edu/
Permissions-Policy: (missing)
$ curl -sIL https://sckans.edu/ | grep -i "Permissions-Policy"
Fix recommendation (effort: Easy)
  1. 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.

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)

Software version disclosure

Passed · Severity: OK · unscored

The server doesn't disclose software versions.

No version numbers found in the Server / X-Powered-By headers.

Source data: Response headers from https://sckans.edu/
server: cloudflare
x-powered-by: (missing)
$ curl -sIL https://sckans.edu/ | grep -iE "^(server|x-powered-by)"
Documentation: OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

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

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS sckans.edu: NODATA
$ dig +short DS sckans.edu
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec sckans.edu SOA
delv sckans.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.

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

Needs attention · Severity: Low · Hardening gap · 0/5

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

Source data: DNS CAA sckans.edu
(no CAA records found)
$ dig +short CAA sckans.edu
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
sckans.edu.  CAA  0 issue "letsencrypt.org"
sckans.edu.  CAA  0 iodef "mailto:security@sckans.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.

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.

5 NS servers.

Source data: DNS NS sckans.edu
jinx.sckans.edu
mound.sckans.edu
ns102.digicertdns.com
ns100.digicertdns.com
ns101.digicertdns.com
$ dig +short NS sckans.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.04 observed gaps
  • NIS2 / vendor due diligence4 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

Asckans.edu40.138.72.25
AAAAsckans.edu—
MXsckans.edu0 sckans-edu.mail.protection.outlook.com
NSsckans.edujinx.sckans.edu | mound.sckans.edu | ns102.digicertdns.com | ns100.digicertdns.com | ns101.digicertdns.com
TXTsckans.eduihs824d5or6cq7ps93rk260077 | dba65qb8eljlksu6tb02ico66c | g5e852v14gbs11gqeldsq57c7i | v=spf1 ip4:40.138.72.24 ip4:40.138.72.33 include:mh.blackboard.com include:spf.protection.outlook.com include:_spf.regroup.com include:_spf.salesforce.com include:cust-spf.cashnet.com include:amazonses.com include:secure.giftlegacy.com ~all | facebook-domain-verification=1tf83pr4k04oevulk8n99qheny2dsb | 00DF00000005nZc=1TBRo00000009T7\010 | obr0tr3r0e81p9c953707cgcct | SFMC-emTPf1sKqYWnrtfduRdjKUwdgHaiLRwE-aUWfBNC | ZOOM_verify_VOUq-c-iQhOZQL9DPztB8g | 71ni4a2t4h3ens4fu7h8pddq8t
TXT_dmarc.sckans.eduv=DMARC1; p=none; adkim=r; aspf=r;
CAAsckans.edu—
DSsckans.edu—
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