55
mckinsey.com
Findings
2
·
4
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
mckinsey.com scored 55/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.
Positive signals: Known Breaches, CVE Exposure all passed.
4 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 · 4 items
1
Strengthen email authentication configuration
Email authentication is partially configured for mckinsey.com but has gaps. Actions needed: configure DKIM. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance Impact
NIST CSFPR.AC-7
Email authentication is a required access control
Remediation Steps
1
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.mckinsey.com
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 4 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 mckinsey.com 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 .com TLD
4
Verify: dig +dnssec mckinsey.com
3
Upgrade to TLS 1.3
mckinsey.com negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
Remediation Steps
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect mckinsey.com:443 -tls1_3
4
Review certificate configuration
Certificate issues found for mckinsey.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
Scan Findings
DNS Configuration
Warning
DMARC / Email Security
Warning
TLS Configuration
Warning
Certificate Hygiene
Warning
HSTS Header
Error
Security Headers
Error
Known Breaches
Healthy
CVE Exposure
Healthy