Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
doordash.com scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, TLS Configuration, HSTS Header 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 doordash.com compares
Grade distribution across 2378 companies we've scanned. doordash.com scores better than 81% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
doordash.com — Grade B+ (88/100)
2378 companies scanned
Security checks
Each check inspects a different part of doordash.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Known Breaches
1 breach(es) found (1 verified). Total accounts affected: 367,476. Breaches: DoorDash (2022-08-02, 367,476 accounts).
Certificate Hygiene
Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (ns1.doordash.com., ns2.doordash.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: CSP.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, k1, mandrill, zendesk1, zendesk2, smtpapi).
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.
Recommended actions
2 items
Steps to improve doordash.com's security grade, ranked by impact.
1
Review unverified breach disclosure
doordash.com appears in an unverified breach report. This may be a false positive or data aggregation error. Investigate to confirm or rule out exposure.
How to fix this
1
Review the breach details on haveibeenpwned.com
2
Cross-reference with internal incident records
3
If confirmed, follow breach response procedures
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review certificate configuration
Certificate issues found for doordash.com: 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.
How to fix this
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
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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, k1, mandrill, zendesk1, zendesk2, smtpapi).
SPF Record
Present
v=spf1 include:doordash.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
Security Headers
4/5 present
Missing: CSP
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (ns1.doordash.com., ns2.doordash.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.