Can Browser Address-Bar Suggestions Bypass SearXNG's Autocomplete Setting?
Disabling SearXNG autocomplete does not control Chrome or Firefox address-bar suggestions. Trace which partial queries may still reach a search provider.
Yes. Turning off autocomplete inside SearXNG does not automatically stop Chrome or Firefox from sending text typed into the browser address bar to a search-suggestion provider. They are separate controls on separate input paths. SearXNG controls suggestions in its webpage; the browser controls its own address bar, default search engine, remote suggestions, and local history matches.
Watch The 30-Second Summary
That is not a software "bypass" in the exploit sense. It is a configuration gap. If you protect only the SearXNG search box but keep browser address-bar suggestions enabled, partial queries may still leave the device before you press Enter.
What Is Confirmed
Current official documentation establishes three important facts.
First, SearXNG has its own autocomplete setting. The official SearXNG search settings documentation lists supported autocomplete backends and says leaving autocomplete blank turns the feature off. The default configuration also defines autocomplete_min, which controls how many characters a person must type before the SearXNG autocompleter starts.
Second, Chrome has a separate address-bar suggestion system. Google's Chrome URL and search-data guidance says that when Improve search suggestions is enabled, Chrome sends address-bar text to the default search engine as the user types. The request also carries an IP address and available cookies. If the default engine is not Google, the other engine's privacy policy governs its handling.
Third, Firefox behaves similarly when its remote search suggestions are enabled. Mozilla's Search suggestions in Firefox page says typed keywords are sent to the default search engine from the address bar, optional Search bar, or New Tab search field. Mozilla separately explains that the address-bar list can mix remote suggestions with local matches from history, bookmarks, and open tabs.
These facts support a narrow answer: disabling the SearXNG webpage's autocomplete does not govern the browser's own suggestion request.
The Two Suggestion Systems People Confuse
The simplest way to understand the issue is to label the input field before changing a setting.
| Where you type | Who controls the suggestions | What disabling SearXNG autocomplete changes |
|---|---|---|
| Search box on a SearXNG webpage | SearXNG instance and user preferences | Stops that page from requesting configured SearXNG autocomplete results |
| Chrome address bar | Chrome settings and the configured default search engine | Nothing directly |
| Firefox address bar | Firefox search settings and the configured default search engine | Nothing directly |
| Local browser-history/bookmark list | Browser and local profile data | Nothing directly |
The two interfaces may eventually send the final search to the same SearXNG instance. That does not make their pre-submit behavior identical.
Imagine a user has this setup:
- SearXNG autocomplete is blank or disabled.
- Google remains the browser's default search engine.
- Chrome's Improve search suggestions setting remains enabled.
- The user types a sensitive phrase into Chrome's address bar.
SearXNG is not involved in the suggestion request at all. Chrome may send the growing prefix to Google because Google is still the default engine. Only after the user navigates to SearXNG and types in its webpage would the SearXNG autocomplete setting apply.
That is the clearest version of the configuration gap.
What Does SearXNG's Autocomplete Setting Actually Control?
SearXNG can ask a configured backend for suggested completions while a person types in the SearXNG page. Its current settings list includes providers such as Bing, Brave, DuckDuckGo, Google, Qwant, Startpage, Swisscows, and Wikipedia.
The documented configuration is conceptually simple:
search:
autocomplete: ""
autocomplete_min: 4
Leaving autocomplete blank turns SearXNG's autocomplete off. If a backend is selected, autocomplete_min determines how many characters are required before SearXNG begins requesting suggestions.
That control is meaningful. It can prevent the SearXNG webpage from forwarding each partial query to a third-party autocomplete backend.
It does not configure Chrome, Firefox, an installed extension, the operating system's launcher, a mobile keyboard, or another search box. Each is a separate potential input and network path.
The setting also does not stop a completed SearXNG search from reaching upstream search engines. SearXNG's Search API documentation says the submitted q string is passed to external search services. Autocomplete privacy and final-query privacy are different questions.
How Chrome Address-Bar Suggestions Can Send Partial Queries
Chrome combines web addresses and searches in the omnibox. When remote suggestions are enabled, Chrome can send what the user is typing to the default search engine before Enter is pressed.
Google's documentation says the sent data can include:
- the text typed so far;
- the user's IP address;
- search information stored in cookies;
- the current page URL in an additional Google-default configuration;
- information about a selected suggestion.
Chrome says it tries not to send certain text it recognizes as sensitive, including passwords, local filenames, or HTTPS URLs with paths. That is a protective heuristic, not a promise that every personal phrase, name, medical concern, client detail, or draft query will be recognized as sensitive.
The decisive setting is in Chrome, not SearXNG. Chrome's current help page directs desktop users to turn Improve search suggestions on or off under Google services.
Chrome also says that even when remote suggestions are off, it may still show suggestions based on local browsing and search history. This distinction matters during testing: seeing a dropdown does not prove that a network request occurred.
How Firefox Separates Remote And Local Suggestions
Firefox also mixes several result types in one address-bar list:
- suggestions from the default search engine;
- prior search-history entries;
- browsing-history pages;
- bookmarks;
- open tabs;
- synced tabs or other Firefox features, depending on configuration.
Mozilla states that enabling search suggestions sends typed keywords to the default search engine unless the text appears to be a URL or hostname. Firefox lets users disable remote search suggestions in Settings under Search.
Mozilla's documentation also says remote search suggestions are disabled by default in Private Browsing and must be explicitly enabled there. That is a useful default, but it should still be checked rather than assumed on a managed or previously configured profile.
As with Chrome, disabling remote suggestions does not make the address-bar dropdown disappear. Firefox can continue showing local history, bookmark, and tab matches. Mozilla's address-bar autocomplete guide explains how those local sources are displayed and controlled.
What Changes If SearXNG Is The Browser's Default Engine?
Making SearXNG the default engine can route completed address-bar searches through the chosen SearXNG instance. Chrome's custom search-engine instructions describe defining a search URL with %s as the query placeholder. Firefox likewise lets users add and choose search engines from its Search settings.
But "SearXNG is my default" still does not answer the suggestion question by itself.
The actual behavior depends on how the browser learned the engine and whether its search-engine definition includes a suggestion endpoint:
- A manually added engine may define only a completed-search URL.
- An OpenSearch description may advertise both search and suggestion endpoints.
- Browser settings may allow or block remote suggestions.
- Enterprise policy or an extension may alter the configuration.
- The SearXNG instance may have autocomplete disabled or configured to use another backend.
When SearXNG is both the default engine and the browser's suggestion provider, partial address-bar text may go to the SearXNG instance rather than directly to Google or another engine. The SearXNG instance may then return no remote suggestions when its autocomplete is disabled. That is materially different from leaving Google as the browser default.
The safe conclusion is configuration-specific: inspect the browser's default engine, its suggestion capability, and the SearXNG setting. Do not infer the whole path from one checkbox.
A Five-Point Address-Bar Privacy Audit
Use the FIELD audit before typing a sensitive search.
F - Field
Identify the exact box receiving the text. Is it the browser address bar, SearXNG webpage, New Tab search field, an AI app's search tool, or an operating-system launcher?
I - Initiator
Identify the software that reacts to each keystroke. For the address bar, that is the browser. For the SearXNG page, it is the page and instance.
E - Engine
Check the configured default search engine and any active shortcut. A SearXNG tab being open does not mean the browser address bar uses SearXNG.
L - Live Suggestions
Check whether remote search suggestions are enabled in the browser and whether SearXNG autocomplete is configured. These are two different toggles.
D - Destination
Determine where partial and completed queries go. The destinations may include a browser vendor, default search engine, SearXNG instance, SearXNG autocomplete backend, and upstream engines used for final results.
This audit is more reliable than asking whether the setup is simply "private." It forces each network boundary into view.
How To Test Without Sending A Real Sensitive Query
Use a synthetic canary that has never appeared in your history, such as:
ovtest-7429-lavender-comet
Do not use a real person's name, account number, diagnosis, client project, or confidential phrase.
Then test one input path at a time:
- Turn SearXNG autocomplete off.
- Confirm the browser's default engine.
- Type only the harmless canary in the SearXNG webpage and observe whether suggestions appear.
- Type a different canary in the browser address bar without pressing Enter.
- Repeat after disabling the browser's remote search suggestions.
- Clear local history or use a fresh test profile if local matches make the dropdown ambiguous.
The visible dropdown is not sufficient evidence because local and remote suggestions can look similar. Administrators who need stronger evidence can capture DNS or HTTPS destination metadata at a controlled network gateway, use a local debugging proxy on a test profile, or inspect server logs on their own SearXNG instance. Avoid decrypting or capturing other people's traffic.
The goal is not to prove that no browser request could ever occur. It is to verify the specific profile, policy, engine, and version that will handle sensitive searches.
What Is Still Unclear Without Inspecting The Configuration
No universal answer can identify the exact recipient of address-bar text without more evidence.
You still need to determine:
- which browser and version are in use;
- whether remote search suggestions are enabled;
- which engine is the default;
- whether the active engine definition includes a suggestion URL;
- whether an extension or enterprise policy changes address-bar behavior;
- whether SearXNG autocomplete is locked by the administrator or overridden by a user preference;
- which backend SearXNG uses when autocomplete is enabled;
- whether the displayed items came from the network or local profile data.
It is also important not to overstate what turning suggestions off accomplishes. The completed search still goes somewhere after Enter. If it goes through SearXNG, the instance receives the query and forwards it to configured upstream services. Browser suggestion settings do not turn a network search into local-only processing.
Practical Settings Checklist
For Chrome:
- Verify the default search engine under Search engine settings.
- Turn off Improve search suggestions if partial-query sharing is not acceptable.
- Review Make searches and browsing better if Google is the default engine.
- Remember that local history suggestions may remain visible.
For Firefox:
- Verify the default engine under Settings > Search.
- Turn off Show search suggestions when partial-query sharing is not acceptable.
- Check the separate Private Window option.
- Review which local address-bar sources remain enabled under Privacy & Security.
For SearXNG:
- Leave
search.autocompleteblank to disable its autocomplete backend. - Review
autocomplete_minif autocomplete is intentionally enabled. - Lock the autocomplete preference if an administrator needs a consistent multi-user policy.
- Document the final-query engines and the instance's logging, proxy, and retention configuration.
Finally, retest after browser updates, profile migrations, policy changes, extensions, or a new default search engine. Privacy-relevant defaults can drift even when the SearXNG server configuration has not changed.
Where OpenVeil Fits - And Where It Does Not
OpenVeil is a privacy-focused hosted AI workspace for adults. It offers private web search alongside chat, files, voice, image tools, video, and browser-local chat history without a normal server-side chat-history record.
If a user intends to run a search through OpenVeil, typing the request inside the OpenVeil app instead of the browser address bar avoids the browser's default search-suggestion path for that text. The active request still has to be processed by OpenVeil and necessary search, AI, routing, hosting, and security providers. OpenVeil is not fully offline, anonymous, zero-log, or a browser-configuration tool.
OpenVeil does not change Chrome, Firefox, or a separate SearXNG installation. It cannot stop an address-bar suggestion request that occurs before the user enters the OpenVeil workflow. The honest comparison is about choosing the correct input path, not claiming one privacy setting protects every search field.
For more context, read Does SearXNG Autocomplete Send Partial Queries To Another Provider? and Does Self-Hosting SearXNG Keep Every AI Search Query Private?.
Frequently Asked Questions
Does disabling SearXNG autocomplete disable Chrome suggestions?
No. SearXNG and Chrome have separate settings. Chrome's remote address-bar suggestions are controlled by Chrome and its configured default search engine.
Does disabling SearXNG autocomplete disable Firefox suggestions?
No. Firefox controls its own search suggestions. Disable them in Firefox's Search settings if you do not want typed address-bar keywords sent to the default engine.
If suggestions still appear, does that prove text was sent online?
No. Browsers can show local matches from history, bookmarks, open tabs, and prior searches. Use a harmless canary and inspect the configuration or controlled network evidence before drawing a conclusion.
Does making SearXNG the default engine solve the problem?
It changes the destination for completed address-bar searches and may change the suggestion path, but it is not sufficient evidence by itself. Check whether the engine definition supports suggestions and whether the browser enables them.
Does turning off browser suggestions keep the final search local?
No. It can stop pre-submit suggestion requests, but pressing Enter still sends the completed query to the configured engine. SearXNG then sends searches to its configured upstream services.
Is this a SearXNG security vulnerability?
No. The issue is a boundary between independent controls. "Bypass" describes the privacy expectation being missed, not code defeating SearXNG's setting.
Bottom Line
SearXNG's autocomplete setting protects the SearXNG webpage's suggestion path. It does not automatically protect the Chrome or Firefox address bar.
For sensitive searches, audit the exact field, browser setting, default engine, suggestion capability, SearXNG backend, and final-query destination. Turn off both remote-suggestion systems when needed, test with harmless canaries, and remember that the completed search still leaves the device unless the entire workflow is genuinely local.