DuckDuckGo help and reporting
Use the help topic for Search, the browser or the privacy feature involved.
Live Domain Check
Run a live reachability check for duckduckgo.com. Compare the regional responses with the problem you see in DuckDuckGo.
Find DuckDuckGo help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
DuckDuckGo search, its browser and subscription/privacy features are different products.
The checker above requests duckduckgo.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual DuckDuckGo action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Use the help topic for Search, the browser or the privacy feature involved.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.
Use the help topic for Search, the browser or the privacy feature involved.
Open DuckDuckGo help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Product, URL/query with private details removed, browser/OS, privacy-feature context and error time.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to DuckDuckGo.
These are troubleshooting comparisons, not claims that DuckDuckGo is currently experiencing a particular incident.
Compare a simple web search with the failing browser or privacy feature.
Use the matching official help section and record whether a website fails only in the DuckDuckGo browser.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when DuckDuckGo seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open duckduckgo.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader DuckDuckGo issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting DuckDuckGo support.
Run the duckduckgo.com check and compare its original timestamps and responses with your actual error. DuckDuckGo search, its browser and subscription/privacy features are different products.
Use the official help/reporting resource linked above. Use the help topic for Search, the browser or the privacy feature involved.
Compare a simple web search with the failing browser or privacy feature. Use the matching official help section and record whether a website fails only in the DuckDuckGo browser.
Product, URL/query with private details removed, browser/OS, privacy-feature context and error time.