82
johnshopkins.edu
Findings
5
·
2
·
1
Checks
8 passive
Executive Summary
AI-GENERATED
johnshopkins.edu scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: Known Breaches, TLS Configuration, Security Headers all passed.
3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
Action Items
Ordered by priority · 3 items
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on johnshopkins.edu. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance Impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
Remediation Steps
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://johnshopkins.edu | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 3 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for johnshopkins.edu can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance Impact
NIST 800-53SC-20
Secure name/address resolution service
Remediation Steps
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .edu TLD
4
Verify: dig +dnssec johnshopkins.edu
3
Review certificate configuration
Certificate issues found for johnshopkins.edu: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
Scan Findings
HSTS Header
Critical
DNS Configuration
Warning
Certificate Hygiene
Warning
Known Breaches
Healthy
TLS Configuration
Healthy
Security Headers
Healthy
CVE Exposure
Healthy
DMARC / Email Security
Healthy