DoorDash
Food · United States · Q20714323
- Verdict
- Couldn't CheckWe couldn't read this company's robots.txt. doordash.com refused our checker (HTTP 403), which usually means bot protection is on. We try again every day, and we never work around a refusal.
- Company statement
- None found
- robots.txt signals
- Couldn't check. Site refused our checker (HTTP 403).
- Last checked
- Fee
- Unknown
- x402
- Unknown
- Notes
- Auto-discovered (Tranco + Wikidata); consumer classification not yet reviewed.
- Human verified
- Not yet
By agent
| Agent | Result | Basis |
|---|---|---|
| ChatGPT | No data | No data |
| Claude | No data | No data |
| Perplexity | No data | No data |
| Gemini | No data | Google documents Google-Agent for agents hosted on its infrastructure but does not name Gemini; the mapping is unconfirmed. |
| Meta AI | No data | Meta's assistant. Meta documents this token for user-requested fetches but does not name Meta AI; the mapping is unconfirmed. |
| Meta Muse | No data | Reported to send a generic Chromium-on-Linux user agent, so it cannot be targeted or detected via robots.txt; only company statements can speak to it. |
Consumer surfaces
- DoorDash (primary) doordash.com · Access: Unknown
Evidence
| Source type | Agents | Result | Evidence level | Observed | Source |
|---|---|---|---|---|---|
| No evidence recorded yet. | |||||
robots.txt checks
| Host | Result | Last checked | Unchanged since | Content-Signal |
|---|---|---|---|---|
| doordash.com | Refused (403) | 2026-11-07 23:00 UTC | 2026-11-02 | None |
A robots.txt with no agent-specific rules produces no result, and silence is not the same as allowed. A refused or unreachable check says nothing about the site's rules.
Evidence levels: Our Check is a direct read of the site's robots.txt, Company Document is confirmed by a quote, News Report is reported by a reputable outlet, and Unverified Lead never sets a verdict. Methodology v2. View as JSON