Port 4664Google Desktop Search
Port 4664 is primarily associated with Google Desktop Search, an application developed by Google to index and enable quick search functionality over a user's local files and emails. This port facilitates communication and management of search queries between the user interface and the local indexing service. Though Google Desktop was discontinued, references to this port can still be found in legacy environments or within archived software setups..
- transport
- tcp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 67,217
single transport
payload readable on path
used by convention
caution
rank 11 of 993 · top 1%
1 other service is registered on port 4664. compare all 2 →
Technical Details
what runs on :4664Google Desktop Search was a desktop search application developed by Google that allowed users to perform full-text search of emails, files, music, photos, chats, and web pages viewed. The application created an index of the contents on the host machine, enabling fast keyword searches. Port 4664 was utilized by the local HTTP server component embedded in Google Desktop Search to provide a web-based user interface accessible from the browser.
When active, the embedded web server on 127.0.0.1:4664 responded to queries by delivering indexed results via a familiar Google-style webpage. Communications primarily occurred over HTTP with no encryption, designed for local communication between services or from the web browser to the internal service.
Despite being deprecated, some residual installations or archival product copies might still use this port for search integration within the host operating system. Since it was not designed as a cloud service endpoint, network exposure of this port was neither necessary nor recommended.
Security Information
exposure of :4664risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
system averages 3.9 across 342 ports — this one sits 0.1 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
Common Vulnerabilities:
- Unauthorized local access if malicious software exploits the open local web service
- Potential information disclosure through indexed content if the port is inadvertently exposed externally
- Lack of encryption exposing sensitive search queries or response data
Common Mitigations:
- Ensure port 4664 is not accessible outside the local host interface (bind only to 127.0.0.1)
- Disable or fully uninstall Google Desktop Search, as it is deprecated
- Use host firewall rules to block external access
- Regularly update security configurations and remove legacy software with unpatched vulnerabilities
Related Ports
the 8 most looked-up other ports in system — 342 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8888 | Sun Answerbook & Alt HTTP | TCP | Web Services | caution | 123.9k |
| :8008 | IBM HTTP Server Admin | TCP | Web Services | caution | 58.3k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :9080 | WebSphere HTTP Transport (default) | TCP | Web Services | caution | 51.6k |
| :23 | Telnet | TCP | Remote Access | caution | 34.8k |
| :12489 | NSClient Monitoring Agent | TCP | Network Services | caution | 30.0k |
| :8011 | Symon Event Engine | TCP | Network Services | caution | 28.4k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted