Doordash.engineering valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | DoorDash Engineering Blog – The official blog of DoorDash Engineering team. |
| Description | The official blog of DoorDash Engineering team. |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 192.0.78.159 |
| Location | San Francisco, California, United States |
Related Websites
| Site | Rank |
| codemio.com | #2,363,710 |
More to Explore
| dorsetlep.co.uk |
| dortex.de |
| down-soft.com |
| downloadtyphoon.com |
| dr-theme.com |
| dramdl1.xyz |
| dreamworks.ae |
| drferas.com |
| driverforcanon.com |
| drmatematik.com |
| pmillc.com |
| pornazon.net |
Doordash.engineering Valuation
|
US$20,290
Last updated: Jan 29, 2020
Doordash.engineering has global traffic rank of 1,683,217. Doordash.engineering has an estimated worth of US$ 20,290, based on its estimated Ads revenue. Doordash.engineering receives approximately 1,853 unique visitors each day. Its web server is located in San Francisco, California, United States, with IP address 192.0.78.159. According to SiteAdvisor, doordash.engineering is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$20,290 |
| Daily Ads Revenue | US$11 |
| Monthly Ads Revenue | US$333 |
| Yearly Ads Revenue | US$4,058 |
| Daily Unique Visitors | 1,853 |
| Note: All traffic and earnings values are estimates. | |
Traffic Ranks
| Global Rank | 1,683,217 |
| Delta (90 Days) | 0 |
| Most Popular In Country | N/A |
| Country Rank | N/A |
DNS Records
| Host | Type | TTL | Data |
| doordash.engineering | A | 299 | IP: 192.0.78.252 |
| doordash.engineering | A | 299 | IP: 192.0.78.159 |
| doordash.engineering | MX | 14399 | Priority: 10 Target: eforward3.registrar-servers.com. |
| doordash.engineering | MX | 14399 | Priority: 20 Target: eforward5.registrar-servers.com. |
| doordash.engineering | MX | 14399 | Priority: 10 Target: eforward1.registrar-servers.com. |
| doordash.engineering | MX | 14399 | Priority: 15 Target: eforward4.registrar-servers.com. |
| doordash.engineering | MX | 14399 | Priority: 10 Target: eforward2.registrar-servers.com. |
| doordash.engineering | NS | 21599 | Target: ns1.wordpress.com. |
| doordash.engineering | NS | 21599 | Target: ns3.wordpress.com. |
| doordash.engineering | NS | 21599 | Target: ns2.wordpress.com. |
| doordash.engineering | TXT | 3599 | TXT: v=spf1 include:spf.efwd.registrar-servers.com ~all |
| doordash.engineering | SOA | 21599 | MNAME: ns1.wordpress.com. RNAME: hostmaster.wordpress.com. Serial: 2005071858 Refresh: 14400 Retry: 7200 Expire: 604800 Minimum TTL: 300 |
HTTP Headers
HTTP/1.1 301 Moved Permanently Server: nginx Date: Wed, 29 Jan 2020 23:51:09 GMT Content-Type: text/html Content-Length: 162 Connection: keep-alive Location: https://doordash.engineering/ X-ac: 3.ewr _atomic_dca HTTP/2 200 server: nginx date: Wed, 29 Jan 2020 23:51:09 GMT content-type: text/html; charset=UTF-8 strict-transport-security: max-age=86400 vary: Accept-Encoding vary: Cookie link: <https://doordash.engineering/wp-json/>; rel="https://api.w.org/" link: <https://wp.me/PauO29-d>; rel=shortlink last-modified: Wed, 29 Jan 2020 23:51:09 GMT cache-control: max-age=300, must-revalidate x-nananana: Batcache x-ac: 3.ewr _atomic_dca |
Doordash.engineering Whois Information
Domain Name: doordash.engineering Registry Domain ID: a8f6d2a7fed94939ac4fbe742aabc8ec-DONUTS Registrar WHOIS Server: whois.gandi.net Registrar URL: https://www.gandi.net Updated Date: 2019-12-13T17:20:40Z Creation Date: 2019-01-03T19:32:06Z Registry Expiry Date: 2021-01-03T19:32:06Z Registrar: Gandi SAS Registrar IANA ID: 81 Registrar Abuse Contact Email: abuse@support.gandi.net Registrar Abuse Contact Phone: +33.170377661 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Organization: DoorDash, Inc. Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: CA Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: US Registrant Phone: REDACTED FOR PRIVACY Registrant Phone Ext: REDACTED FOR PRIVACY Registrant Fax: REDACTED FOR PRIVACY Registrant Fax Ext: REDACTED FOR PRIVACY Registry Admin ID: REDACTED FOR PRIVACY Admin Name: REDACTED FOR PRIVACY Admin Organization: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin City: REDACTED FOR PRIVACY Admin State/Province: REDACTED FOR PRIVACY Admin Postal Code: REDACTED FOR PRIVACY Admin Country: REDACTED FOR PRIVACY Admin Phone: REDACTED FOR PRIVACY Admin Phone Ext: REDACTED FOR PRIVACY Admin Fax: REDACTED FOR PRIVACY Admin Fax Ext: REDACTED FOR PRIVACY Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Organization: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Phone Ext: REDACTED FOR PRIVACY Tech Fax: REDACTED FOR PRIVACY Tech Fax Ext: REDACTED FOR PRIVACY Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: ns2.wordpress.com Name Server: ns1.wordpress.com Name Server: ns3.wordpress.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ |