Digital exposure report
texascollege.edu
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-17 21:04 UTC
Partial coverage: the score is based on 95% of applicable check weight. 1 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.texascollege.edu
- 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://texascollege.edu/ | grep -i "Strict-Transport-Security"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- texascollege.edu
- Website request
- GET https://texascollege.edu/
- Scan time
- 2026-11-17 21:04:58 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
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 | 10/25 | An attacker can send email that looks like it came from the company. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 0/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 3/15 | The domain's infrastructure lacks basic protections. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.HighDMARC — anti-spoofing policy · Hardening gap+16
- 3.MediumClickjacking protection · Hardening gap+5
- 4.MediumDNSSEC — signed DNS records · Hardening gap+7
- 5.MediumCSP — protection from script injection · Hardening gap+8
- 6.LowCAA — who may issue certificates · Hardening gap+5
- 7.LowX-Content-Type-Options · Hardening gap+4
- 8.LowReferrer-Policy · Hardening gap+3
- 9.LowPermissions-Policy · Hardening gap+2
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.
- DKIM — digital signature on email
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. 3 of the 10 allowed DNS lookups.
v=spf1 include:spf.protection.outlook.com ip4:66.76.24.135 ip4:198.17.44.211 a:mx1.texascollege.edu include:spf.groupm7.com -all
$ dig +short TXT texascollege.edu
DMARC — anti-spoofing policy
Failed · Severity: High · Hardening gap · 0/15No policy tells mail servers to block forged email in the company's name — a common opening for CEO fraud and phishing.
No TXT record at _dmarc.texascollege.edu. Without DMARC, mail failing SPF/DKIM may still reach the inbox.
(no DMARC record found)
$ dig +short TXT _dmarc.texascollege.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.texascollege.edu. TXT "v=DMARC1; p=none; rua=mailto:dmarc@texascollege.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
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.texascollege.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 texascollege-edu.mail.protection.outlook.com
$ dig +short MX texascollege.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://texascollege.edu/ returned HTTP 200 (final URL: https://texascollege.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://texascollege.edu/
$ curl -sIL https://texascollege.edu/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 302 → https://texascollege.edu/
HTTP 302 Location: https://texascollege.edu/
$ curl -sI http://texascollege.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-01-07 (50 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-10-09 Valid until: 2027-01-07 Names: *.texascollege.edu, texascollege.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect texascollege.edu:443 -servername texascollege.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://texascollege.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://texascollege.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
Failed · Severity: Medium · Hardening gap · 0/5Missing 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.
X-Frame-Options: (missing)
$ curl -sIL https://texascollege.edu/ | grep -i "X-Frame-Options"
- Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
- 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.
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://texascollege.edu/ | grep -i "X-Content-Type-Options"
- 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.
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://texascollege.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://texascollege.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://texascollege.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 texascollege.edu: NODATA
$ dig +short DS texascollege.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 texascollege.edu SOA delv texascollege.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
Needs attention · Severity: Low · Hardening gap · 0/5Any 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.
(no CAA records found)
$ dig +short CAA texascollege.edu
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
texascollege.edu. CAA 0 issue "letsencrypt.org" texascollege.edu. CAA 0 iodef "mailto:security@texascollege.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.
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.
anton.ns.cloudflare.com sharon.ns.cloudflare.com
$ dig +short NS texascollege.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 · 1 unverified
- PCI DSS v4.03 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
| A | texascollege.edu | 66.76.35.31 |
| AAAA | texascollege.edu | 2602:fcc9:777:1::31 |
| MX | texascollege.edu | 0 texascollege-edu.mail.protection.outlook.com |
| NS | texascollege.edu | anton.ns.cloudflare.com | sharon.ns.cloudflare.com |
| TXT | texascollege.edu | 4zixVD1pjGiO1mpBpbi1wB0NcraqEdhYmeGGRoGcs5K32xEq\010X/A3EyzucTKEOCiMxxoAFiAPUJKneIG4euV/KQ== | MS=9868EEE60223D2ABF3FD844FB63D95F48C814E1B | MS=ms69008921 | google-site-verification=UXfAXxtxInTuXNOgSu7EFt7\010jnjKP8WAlNNa3acXx7C8 | google-site-verification=UXfAXxtxInTuXNOgSu7EFt7jnjKP8WAlNNa3acXx7C8 | v=DMARC1; p=quarantine | v=spf1 include:spf.protection.outlook.com ip4:66.76.24.135 ip4:198.17.44.211 a:mx1.texascollege.edu include:spf.groupm7.com -all |
| TXT | _dmarc.texascollege.edu | — |
| CAA | texascollege.edu | — |
| DS | texascollege.edu | — |