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.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
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.
Looking for another service? Browse infrastructure checks.
Use the help topic for Search, the browser or the privacy feature involved.
Open the website in your browser and compare it with the result above.
Open DuckDuckGo help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
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 Forbidden or 429 Too Many Requests 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.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
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 community buttons on this page to share whether the service works for you. For help from DuckDuckGo, 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.