Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
chef.io scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, DMARC / Email Security, Known Breaches all passed.
2 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.
How chef.io compares
Grade distribution across 2599 companies we've scanned. chef.io scores better than 92% of them.
84
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
chef.io — Grade A- (92/100)
2599 companies scanned
Security checks
Each check inspects a different part of chef.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
DNS Configuration
Strengths: 4 nameservers configured (ns-92.awsdns-11.com., ns-1117.awsdns-11.org., ns-1993.awsdns-57.co.uk., ns-829.awsdns-39.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: selector1).
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. preload present.
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 83 days remaining; Issued by Google Trust Services.
Recommended actions
2 items
Steps to improve chef.io's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for chef.io 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
How to fix this
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 .io TLD
4
Verify: dig +dnssec chef.io
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (CSP, Permissions-Policy)
chef.io has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://chef.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: selector1).
SPF Record
Present
v=spf1 include:mktomail.com include:stspg-customer.com include:_spf.google.com include:sparkpostmail
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. preload present.
SSL Certificate
Valid
Strengths: Certificate valid, 83 days remaining; Issued by Google Trust Services.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-92.awsdns-11.com., ns-1117.awsdns-11.org., ns-1993.awsdns-57.co.uk., ns-829.awsdns-39.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.