curl -s https://www.pathwren.workers.dev/crawler/duckduckbot.json   # this page, as JSON

DuckDuckBot

DuckDuckGo · Search engines · json

User-agent: DuckDuckBot
Disallow: /

What it is

DuckDuckGo's own crawler. Note that the bulk of DuckDuckGo's web results come from Bing, so blocking bingbot removes you from DuckDuckGo whether or not you allow this one.

What blocking it costs you

Limited on its own; the real DuckDuckGo lever is bingbot.

Full user-agent string

DuckDuckBot/1.1; (+http://duckduckgo.com/duckduckbot.html)

Allow it instead

User-agent: DuckDuckBot
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=duckduckbot&s=client-dossiers'

• /tools/verification-methods?crawler=duckduckbot
  How do I prove a request really is DuckDuckBot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.
• /tools/verify-crawler?ip=104.43.54.127&ua=DuckDuckBot
  Is 104.43.54.127 really DuckDuckBot? That address checked against every prefix this host mirrors. 104.43.54.127 is the first address of 104.43.54.127/32, one of the ranges listed on this page — so the link is a worked example that returns a match. Swap in an address from your own log.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://duckduckgo.com/duckduckgo-help-pages/results/duckduckbot/
Machine copies: json · markdown
Policies that name this crawler: allow-all · allow-ai-search-only · maximum-ai-visibility