Digital exposure report
vhcc.edu
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-22 15:02 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://vhcc.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://vhcc.edu/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- vhcc.edu
- Website request
- GET https://vhcc.edu/
- Scan time
- 2026-11-22 15:02:43 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 | 30/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 | 9/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.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowReferrer-Policy · Hardening gap+3
- 5.LowPermissions-Policy · Hardening gap+2
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. 5 of the 10 allowed DNS lookups.
v=spf1 include:spf.protection.outlook.com ip4:164.106.100.35 include:_spf.salesforce.com include:enotify.visioninternet.com include:_spf1.vhcc.edu ip4:204.73.44.226 ip4:204.73.44.228 ip4:198.21.2.183 ip4:35.167.98.129 ip4:216.17.93.137 ip4:198.21.1.32 include:_spf.psm.knowbe4.com -all
$ dig +short TXT vhcc.edu
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; rua=mailto:buryvooi@ag.dmarcian.com;
$ dig +short TXT _dmarc.vhcc.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=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCoUuR4vswmHH2EizUp8thyYhKUCvJa42iz…
$ dig +short TXT selector1._domainkey.vhcc.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 vhcc-edu.mail.protection.outlook.com
$ dig +short MX vhcc.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://vhcc.edu/ returned HTTP 200 (final URL: https://vhcc.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://vhcc.edu/
$ curl -sIL https://vhcc.edu/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://vhcc.edu/
HTTP 301 Location: https://vhcc.edu/
$ curl -sI http://vhcc.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-02-13 (83 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-15 Valid until: 2027-02-13 Names: vhcc.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect vhcc.edu:443 -servername vhcc.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://vhcc.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://vhcc.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://vhcc.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://vhcc.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://vhcc.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://vhcc.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://vhcc.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 vhcc.edu: NODATA
$ dig +short DS vhcc.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 vhcc.edu SOA delv vhcc.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: 0 issue "ssl.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "\226\128\156sectigo.com\226\128\157" | 0 issue "entrust.net"
0 issue "ssl.com" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issue "\226\128\156sectigo.com\226\128\157" 0 issue "entrust.net"
$ dig +short CAA vhcc.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.vccs.edu ns1.vccs.edu
$ dig +short NS vhcc.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.02 observed gaps
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baseline2 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 | vhcc.edu | 164.106.222.16 |
| AAAA | vhcc.edu | — |
| MX | vhcc.edu | 0 vhcc-edu.mail.protection.outlook.com |
| NS | vhcc.edu | ns2.vccs.edu | ns1.vccs.edu |
| TXT | vhcc.edu | MS=2900FEA245507E8AFEB0D0BEAEFE947A182B21A4 | sending_domain801893=315357a7ad070a4c3b6dc95e6958d9336d19749bc4b2b1dcf127b8c12a7ab7e3 | v=spf1 include:spf.protection.outlook.com ip4:164.106.100.35 include:_spf.salesforce.com include:enotify.visioninternet.com include:_spf1.vhcc.edu ip4:204.73.44.226 ip4:204.73.44.228 ip4:198.21.2.183 ip4:35.167.98.129 ip4:216.17.93.137 ip4:198.21.1.32 include:_spf.psm.knowbe4.com -all | g9innea90st5r71hnmn2esv0ai | 8LKsinZ1JvtS8MxEGC9QLaAt+4300mDg7eANiwtSEQUZYBKEy1ZTWBlpsWEiCqt1bVC7+C9uiKBgETCdNIZJgw== | pardot801893=18c027c82bb71839bb6dc22a5ffb9239f521e4872323c244de6dcd11d6bb3615 |
| TXT | _dmarc.vhcc.edu | v=DMARC1; p=reject; rua=mailto:buryvooi@ag.dmarcian.com; |
| CAA | vhcc.edu | 0 issue "ssl.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "\226\128\156sectigo.com\226\128\157" | 0 issue "entrust.net" |
| DS | vhcc.edu | — |