doordash.com blocks automated analysis, answering with HTTP 403 to an automated client instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.
This site blocks automated analysis.
It answered our request with HTTP 403 to an automated client rather than its
homepage, so nothing below is derived from its actual content — doing so would describe
the bot wall, not the site. The certificate and robots.txt data are still accurate,
because those are served to everyone.
How does doordash.com compare with other domains analysed here?
Measured against the 81 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 85% of them (median 491ms) |
|---|---|
| Domain age | Older than 36% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
Other analysed domains served from the same country:
When was doordash.com registered?
doordash.com was registered on 18 June 2013, which makes it about 13 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is MarkMonitor Inc..
Registration runs until 18 June 2031.
The domain carries 6 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 18 June 2013 |
|---|---|
| Expires | 18 June 2031 |
| Registrar | MarkMonitor Inc. |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
Where is doordash.com hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is doordash.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of doordash.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 403 over
HTTPS.
At 114ms to first byte this response is fast for a homepage measured from a single European location.
The HTML weighs 273KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 279,269 bytes |
| Declared language | not declared |
| Mobile viewport | not declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is doordash.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-01, which is 57 days from the date of this check. It covers
2 hostnames.
- doordash.com
- *.doordash.com
The certificate has 57 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
| Header | Set | Value |
|---|
How is DNS configured for doordash.com?
| IP addresses | 172.64.152.226, 104.18.35.30, 2606:4700:4402::ac40:98e2, 2a06:98c1:3107::6812:231e |
|---|---|
| Reverse DNS | 172.64.152.226, 104.18.35.30 |
| Name servers | ns2.doordash.com, ns1.doordash.com |
| Mail (MX) | aspmx2.googlemail.com (pri 10), aspmx3.googlemail.com (pri 10), alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1) |
| SPF | v=spf1 include:doordash.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all |
| TXT records | 59 |
doordash.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 5 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 172.64.152.226, 104.18.35.30, which usually names the hosting provider.
Can doordash.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
CAA records restrict certificate issuance to 6 named authorities (issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
Frequently asked questions
Does doordash.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own doordash.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →