AboutUs hasn't finished checking this site yet — the live checks below are current; more details appear as we crawl it.
doordash.com
Verifying against the live site and live WHOIS/DNS…
Common questions
Is doordash.com legit or a scam?
doordash.com was registered Jun 18, 2013 (13 years old), per public registration records. AboutUs doesn't label sites "legit" or "a scam": this page lists the dated registration, DNS, HTTPS, mail-authentication and safety checks we could verify, each with its source, so you can decide for yourself.
Who owns doordash.com?
Nobody has completed AboutUs's owner verification for doordash.com. That's true of most sites here — it isn't itself a warning sign.
When was doordash.com registered?
doordash.com's registration dates to Jun 18, 2013 (13 years old), per public registration records. MarkMonitor Inc. is the registrar on record today.
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 13 years ago · on AboutUs since 2015 · 3 registrar changes since Nov 11, 2013 · 2 registrant changes since 2013 · last checked Nov 1, 2026.
Registration
RegisteredJun 18, 2013doordash.com was registered on Jun 18, 2013.Source: RDAP, fetched Oct 25, 2026
AboutUs record
AboutUs wiki pageFeb 21, 2015An AboutUs wiki page described doordash.com from Feb 21, 2015 to Feb 21, 2015 (1 edit).Source: AboutUs wiki archive, 2006–2023Current AboutUs recordJul 18, 2026 – Nov 1, 2026 (latest)Authority and Safety last refreshed Nov 1, 2026.
Registrar
ENOM, INC.ENOM, INC.Nov 11, 2013 – Dec 23, 2017Registrar ENOM, INC. (IANA 48) in the WHOIS and RDAP records held for doordash.com, from Nov 11, 2013 to Dec 23, 2017.Source: WHOIS / RDAP archive (who.is)NAMECHEAP INCFeb 13, 2018 – Nov 26, 2019
Registrant
Registrant recordsAug 14, 2013 – Jun 29, 2026Registration records for doordash.com are held from Aug 14, 2013 to Jun 29, 2026 (519 records). 2 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Zone file
Nameservers: dnsimple.comOct 18, 2013 – Jun 1, 2014dnsimple.com (ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com…) were the nameservers listed for doordash.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Jun 1, 2014 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Certificate
GeoTrustJun 18, 2013 – Jun 22, 2014GeoTrust issued 1 certificate for doordash.com from Jun 18, 2013, the latest valid until Jun 22, 2014.Source: Certificate Transparency logs (crt.sh)COMODO CA LimitedMar 10, 2014 – Mar 10, 2015COMODO CA Limited issued 3 certificates for doordash.com from Mar 10, 2014, the latest valid until Mar 10, 2015.
201520202025Jan ’26Oct ’26← last 12 months, drawn wider
Every dated fact on this lifeline (39)
Jun 18, 2013Registration: doordash.com was registered on Jun 18, 2013.Source: RDAP, fetched Oct 25, 2026
Jun 18, 2013 – Jun 22, 2014Certificate: GeoTrust issued 1 certificate for doordash.com from Jun 18, 2013, the latest valid until Jun 22, 2014.Source: Certificate Transparency logs (crt.sh)
Aug 14, 2013 – Jun 29, 2026Registrant: Registration records for doordash.com are held from Aug 14, 2013 to Jun 29, 2026 (519 records). 2 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Oct 18, 2013 – Jun 1, 2014Zone file: dnsimple.com (ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com…) were the nameservers listed for doordash.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Jun 1, 2014 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nov 11, 2013 – Dec 23, 2017Registrar: Registrar ENOM, INC. (IANA 48) in the WHOIS and RDAP records held for doordash.com, from Nov 11, 2013 to Dec 23, 2017.Source: WHOIS / RDAP archive (who.is)
Automated safety checks
DNS (passed)
AboutUs has not vetted this site. Everything below is what we could measure automatically. Anything you do on the site — paying, sharing personal details, downloading — is between you and the site, not AboutUs.
Current facts
Latest available measurements; dated entries retain their dates. These are measurements, not an endorsement of the site.
latest result
Domain registered Jun 18, 2013 — 13 years old.
latest result
Registrar on record: MarkMonitor Inc. — unchanged since AboutUs began tracking (Jul 23, 2026).
Authority 80/100— ahead of 80% of the August 2026 scored sample
Source: AboutUs checks
Registrar NAMECHEAP INC (IANA 1068) in the WHOIS and RDAP records held for doordash.com, from Feb 13, 2018 to Nov 26, 2019.
Source: WHOIS / RDAP archive (who.is)
Amazon Registrar, Inc.Amazon Registrar, Inc.Dec 3, 2019 – Sep 18, 2025Registrar Amazon Registrar, Inc. (IANA 468) in the WHOIS and RDAP records held for doordash.com, from Dec 3, 2019 to Sep 18, 2025.Source: WHOIS / RDAP archive (who.is)
MarkMonitor, Inc.Oct 22, 2025 – Jul 23, 2026 (latest)Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Oct 22, 2025 and most recently on Jul 23, 2026.Source: RDAP, fetched Oct 25, 2026
Registrant changeDec 3, 2019The registrant name or organization in the registration record changed; first recorded Dec 3, 2019. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Registrant changeOct 22, 2025The registrant name or organization in the registration record changed; first recorded Oct 22, 2025. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
2 registrant changes, 2013–2026
Nameservers: CloudflareJan 24, 2015 – Apr 1, 2016Cloudflare (adam.ns.cloudflare.com, vita.ns.cloudflare.com) were the nameservers listed for doordash.com at every ICANN zone-file snapshot AboutUs holds from Jan 24, 2015 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
DNS moved to CloudflareJan 24, 2015doordash.com's nameservers moved from dnsimple.com to Cloudflare at some point between Jun 1, 2014 and Jan 24, 2015. Last seen at dnsimple.com: Jun 1, 2014 (ICANN zone-file snapshot). First seen at Cloudflare: Jan 24, 2015 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 8 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)
Nameservers: CloudflareJul 13, 2016 – Dec 13, 2016Registration records listed Cloudflare nameservers (adam.ns.cloudflare.com, vita.ns.cloudflare.com) for doordash.com from Jul 13, 2016 to Dec 13, 2016.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: Amazon Route 53Feb 5, 2017 – Apr 2, 2018Registration records listed Amazon Route 53 nameservers (ns-1364.awsdns-42.org, ns-143.awsdns-17.com, ns-1956.awsdns-52.co.uk…) for doordash.com from Feb 5, 2017 to Apr 2, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to Amazon Route 53Feb 5, 2017doordash.com's nameservers moved from Cloudflare to Amazon Route 53 at some point between Dec 13, 2016 and Feb 5, 2017. Last seen at Cloudflare: Dec 13, 2016 (registration record). First seen at Amazon Route 53: Feb 5, 2017 (registration record). AboutUs holds no nameserver records for the 54 days in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Nameservers: Amazon Route 53Apr 3, 2018Amazon Route 53 (ns-1364.awsdns-42.org, ns-143.awsdns-17.com, ns-1956.awsdns-52.co.uk…) were the nameservers listed for doordash.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nameservers: Amazon Route 53Apr 4, 2018 – Feb 15, 2020Registration records listed Amazon Route 53 nameservers (ns-1364.awsdns-42.org, ns-143.awsdns-17.com, ns-1956.awsdns-52.co.uk…) for doordash.com from Apr 4, 2018 to Feb 15, 2020. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: doordash.comNameservers: doordash.comMar 23, 2020 – Jun 29, 2026Registration records listed doordash.com nameservers (ns1.doordash.com, ns2.doordash.com) for doordash.com from Mar 23, 2020 to Jun 29, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to doordash.comMar 23, 2020doordash.com's nameservers moved from Amazon Route 53 to doordash.com between Feb 15, 2020 and Mar 23, 2020. Last seen at Amazon Route 53: Feb 15, 2020 (registration record). First seen at doordash.com: Mar 23, 2020 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Seen in the .com zone fileSep 8, 2026 – Nov 1, 2026 (latest)First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 1, 2026. Nameservers on Nov 1, 2026: ns1.doordash.com, ns2.doordash.com. DNSSEC signed on Nov 1, 2026.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
Source: Certificate Transparency logs (crt.sh)
GlobalSign nv-saGlobalSign nv-saOct 8, 2014 – Oct 22, 2018GlobalSign nv-sa issued 47 certificates for doordash.com from Oct 8, 2014, the latest valid until Oct 22, 2018.Source: Certificate Transparency logs (crt.sh)
DigiCert IncDigiCert IncMar 7, 2015 – May 13, 2020DigiCert Inc issued 3 certificates for doordash.com from Mar 7, 2015, the latest valid until May 13, 2020.Source: Certificate Transparency logs (crt.sh)
COMODO CA LimitedCOMODO CA LimitedOct 25, 2015 – Dec 15, 2017COMODO CA Limited issued 6 certificates for doordash.com from Oct 25, 2015, the latest valid until Dec 15, 2017.Source: Certificate Transparency logs (crt.sh)
AmazonAmazonMay 31, 2018 – Nov 2, 2026Amazon issued 43 certificates for doordash.com from May 31, 2018, the latest valid until May 11, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
CloudFlareCloudFlareFeb 25, 2020 – Apr 28, 2024CloudFlare issued 10 certificates for doordash.com from Feb 25, 2020, the latest valid until Apr 28, 2024.Source: Certificate Transparency logs (crt.sh)
Google Trust Services LLCMay 29, 2022 – Apr 21, 2023Google Trust Services LLC issued 5 certificates for doordash.com from May 29, 2022, the latest valid until Apr 21, 2023.Source: Certificate Transparency logs (crt.sh)
DigiCertAug 9, 2023 – Aug 8, 2025DigiCert issued 2 certificates for doordash.com from Aug 9, 2023, the latest valid until Aug 8, 2025.Source: Certificate Transparency logs (crt.sh)
Google Trust Services LLCAug 28, 2023 – Aug 28, 2024Google Trust Services LLC issued 7 certificates for doordash.com from Aug 28, 2023, the latest valid until Aug 28, 2024.Source: Certificate Transparency logs (crt.sh)
Sectigo LimitedSectigo LimitedMar 29, 2024 – Jul 19, 2026Sectigo Limited issued 18 certificates for doordash.com from Mar 29, 2024, the latest valid until Jul 19, 2026.Source: Certificate Transparency logs (crt.sh)
Google Trust ServicesGoogle Trust ServicesJul 25, 2024 – Nov 2, 2026Google Trust Services issued 77 certificates for doordash.com from Jul 25, 2024, the latest valid until Jan 29, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
DigiCertDigiCertNov 17, 2025 – Nov 2, 2026DigiCert issued 1 certificate for doordash.com from Nov 17, 2025, the latest valid until Dec 13, 2026.Source: Certificate Transparency logs (crt.sh)
Let's EncryptJul 21, 2026 – Nov 2, 2026Let's Encrypt issued 78 certificates for doordash.com from Jul 21, 2026, the latest valid until Jan 21, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Sectigo LimitedSep 5, 2026 – Nov 2, 2026Sectigo Limited issued 3 certificates for doordash.com from Sep 5, 2026, the latest valid until Jan 4, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
SSL CorporationSep 27, 2026 – Nov 2, 2026SSL Corporation issued 8 certificates for doordash.com from Sep 27, 2026, the latest valid until Dec 29, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
DigiCert IncSep 29, 2026 – Nov 2, 2026DigiCert Inc issued 4 certificates for doordash.com from Sep 29, 2026, the latest valid until Apr 16, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
ZeroSSL GmbHOct 11, 2026 – Nov 2, 2026ZeroSSL GmbH issued 2 certificates for doordash.com from Oct 11, 2026, the latest valid until Jan 9, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Mar 10, 2014 – Mar 10, 2015
Certificate: COMODO CA Limited issued 3 certificates for doordash.com from Mar 10, 2014, the latest valid until Mar 10, 2015.Source: Certificate Transparency logs (crt.sh)
Oct 8, 2014 – Oct 22, 2018Certificate: GlobalSign nv-sa issued 47 certificates for doordash.com from Oct 8, 2014, the latest valid until Oct 22, 2018.Source: Certificate Transparency logs (crt.sh)
Jan 24, 2015 – Apr 1, 2016Zone file: Cloudflare (adam.ns.cloudflare.com, vita.ns.cloudflare.com) were the nameservers listed for doordash.com at every ICANN zone-file snapshot AboutUs holds from Jan 24, 2015 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Jan 24, 2015Zone file: doordash.com's nameservers moved from dnsimple.com to Cloudflare at some point between Jun 1, 2014 and Jan 24, 2015. Last seen at dnsimple.com: Jun 1, 2014 (ICANN zone-file snapshot). First seen at Cloudflare: Jan 24, 2015 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 8 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)
Feb 21, 2015AboutUs record: An AboutUs wiki page described doordash.com from Feb 21, 2015 to Feb 21, 2015 (1 edit).Source: AboutUs wiki archive, 2006–2023
Mar 7, 2015 – May 13, 2020Certificate: DigiCert Inc issued 3 certificates for doordash.com from Mar 7, 2015, the latest valid until May 13, 2020.Source: Certificate Transparency logs (crt.sh)
Oct 25, 2015 – Dec 15, 2017Certificate: COMODO CA Limited issued 6 certificates for doordash.com from Oct 25, 2015, the latest valid until Dec 15, 2017.Source: Certificate Transparency logs (crt.sh)
Jul 13, 2016 – Dec 13, 2016Zone file: Registration records listed Cloudflare nameservers (adam.ns.cloudflare.com, vita.ns.cloudflare.com) for doordash.com from Jul 13, 2016 to Dec 13, 2016.Source: From registration records (WHOIS / RDAP archive, who.is)
Feb 5, 2017 – Apr 2, 2018Zone file: Registration records listed Amazon Route 53 nameservers (ns-1364.awsdns-42.org, ns-143.awsdns-17.com, ns-1956.awsdns-52.co.uk…) for doordash.com from Feb 5, 2017 to Apr 2, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Feb 5, 2017Zone file: doordash.com's nameservers moved from Cloudflare to Amazon Route 53 at some point between Dec 13, 2016 and Feb 5, 2017. Last seen at Cloudflare: Dec 13, 2016 (registration record). First seen at Amazon Route 53: Feb 5, 2017 (registration record). AboutUs holds no nameserver records for the 54 days in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Feb 13, 2018 – Nov 26, 2019Registrar: Registrar NAMECHEAP INC (IANA 1068) in the WHOIS and RDAP records held for doordash.com, from Feb 13, 2018 to Nov 26, 2019.Source: WHOIS / RDAP archive (who.is)
Apr 3, 2018Zone file: Amazon Route 53 (ns-1364.awsdns-42.org, ns-143.awsdns-17.com, ns-1956.awsdns-52.co.uk…) were the nameservers listed for doordash.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Apr 4, 2018 – Feb 15, 2020Zone file: Registration records listed Amazon Route 53 nameservers (ns-1364.awsdns-42.org, ns-143.awsdns-17.com, ns-1956.awsdns-52.co.uk…) for doordash.com from Apr 4, 2018 to Feb 15, 2020. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
May 31, 2018 – Nov 2, 2026Certificate: Amazon issued 43 certificates for doordash.com from May 31, 2018, the latest valid until May 11, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Dec 3, 2019 – Sep 18, 2025Registrar: Registrar Amazon Registrar, Inc. (IANA 468) in the WHOIS and RDAP records held for doordash.com, from Dec 3, 2019 to Sep 18, 2025.Source: WHOIS / RDAP archive (who.is)
Dec 3, 2019Registrant: The registrant name or organization in the registration record changed; first recorded Dec 3, 2019. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Feb 25, 2020 – Apr 28, 2024Certificate: CloudFlare issued 10 certificates for doordash.com from Feb 25, 2020, the latest valid until Apr 28, 2024.Source: Certificate Transparency logs (crt.sh)
Mar 23, 2020 – Jun 29, 2026Zone file: Registration records listed doordash.com nameservers (ns1.doordash.com, ns2.doordash.com) for doordash.com from Mar 23, 2020 to Jun 29, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Mar 23, 2020Zone file: doordash.com's nameservers moved from Amazon Route 53 to doordash.com between Feb 15, 2020 and Mar 23, 2020. Last seen at Amazon Route 53: Feb 15, 2020 (registration record). First seen at doordash.com: Mar 23, 2020 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
May 29, 2022 – Apr 21, 2023Certificate: Google Trust Services LLC issued 5 certificates for doordash.com from May 29, 2022, the latest valid until Apr 21, 2023.Source: Certificate Transparency logs (crt.sh)
Aug 9, 2023 – Aug 8, 2025Certificate: DigiCert issued 2 certificates for doordash.com from Aug 9, 2023, the latest valid until Aug 8, 2025.Source: Certificate Transparency logs (crt.sh)
Aug 28, 2023 – Aug 28, 2024Certificate: Google Trust Services LLC issued 7 certificates for doordash.com from Aug 28, 2023, the latest valid until Aug 28, 2024.Source: Certificate Transparency logs (crt.sh)
Mar 29, 2024 – Jul 19, 2026Certificate: Sectigo Limited issued 18 certificates for doordash.com from Mar 29, 2024, the latest valid until Jul 19, 2026.Source: Certificate Transparency logs (crt.sh)
Jul 25, 2024 – Nov 2, 2026Certificate: Google Trust Services issued 77 certificates for doordash.com from Jul 25, 2024, the latest valid until Jan 29, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Oct 22, 2025 – Jul 23, 2026Registrar: Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Oct 22, 2025 and most recently on Jul 23, 2026.Source: RDAP, fetched Oct 25, 2026
Oct 22, 2025Registrant: The registrant name or organization in the registration record changed; first recorded Oct 22, 2025. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Nov 17, 2025 – Nov 2, 2026Certificate: DigiCert issued 1 certificate for doordash.com from Nov 17, 2025, the latest valid until Dec 13, 2026.Source: Certificate Transparency logs (crt.sh)
Jul 18, 2026 – Nov 1, 2026AboutUs record: Authority and Safety last refreshed Nov 1, 2026.Source: AboutUs checks
Jul 21, 2026 – Nov 2, 2026Certificate: Let's Encrypt issued 78 certificates for doordash.com from Jul 21, 2026, the latest valid until Jan 21, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Sep 5, 2026 – Nov 2, 2026Certificate: Sectigo Limited issued 3 certificates for doordash.com from Sep 5, 2026, the latest valid until Jan 4, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Sep 8, 2026 – Nov 1, 2026Zone file: First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 1, 2026. Nameservers on Nov 1, 2026: ns1.doordash.com, ns2.doordash.com. DNSSEC signed on Nov 1, 2026.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
Sep 27, 2026 – Nov 2, 2026Certificate: SSL Corporation issued 8 certificates for doordash.com from Sep 27, 2026, the latest valid until Dec 29, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Sep 29, 2026 – Nov 2, 2026Certificate: DigiCert Inc issued 4 certificates for doordash.com from Sep 29, 2026, the latest valid until Apr 16, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Oct 11, 2026 – Nov 2, 2026Certificate: ZeroSSL GmbH issued 2 certificates for doordash.com from Oct 11, 2026, the latest valid until Jan 9, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Clear
Why this authority score
80 is a percentile: higher than 80% of sites we score.
How it's calculated
Prominence (Tranco rank #2,326)+10
Verified continuity: 13.4 years (RDAP registration)+9
Security & email hygiene+5
Calibration adjustment (published map)+17
Model score: 41/99 — what these reason lines add up to.
Published Authority (percentile): 80/100 — this site's rank against the August 2026 scored sample. Public Authority is capped at 99.
Safety evidence
Retained threat-feed result (recorded about 1 days ago); name-similarity check available (recorded about 1 days ago); 3/3 transport and email checks available (oldest recorded about 1 days ago). This is evidence coverage, not a probability that a website is safe.
No caution flags in the available scoring observations; this is not a complete safety assessment
Site history
Dated record — historical facts always carry their date; self-description below is the 2015 record.
2013
Domain registered (Jun 18, 2013).
2015
First tracked by AboutUs (Feb 21, 2015).
2015
Self-description at the time:
“San Francisco Bay Area now delivers. Get”
2026
Checked today — The site's bot protection blocked AboutUs's HTTPS check; all 1 of the other checks passed (Nov 2, 2026).
✓ domain continuity 13 years registered– live check blocked the site's bot protection turned the check away Nov 2, 2026