I'm using DuckDuckGo search engine to protect my privacy. Is it a safe bet to access netbanking site using DuckDuckGo?
closed as unclear what you're asking by Anders, forest, Xander, Tobi Nary, Conor Mancone Feb 1 at 19:49
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Definitely not, the duckduckgo is easy to fool with positioning phishing sites on top search results just like bing so when you search for your banking site it may point you to other website. Especially if it's some kind of small bank.
TL;DR: It is not safe.
First, I find it strange that you access your bank using a search engine in the first place. It is one of the main rules to protect against phishing attacks: never just follow a link to your bank (from mail, from another site) but always enter the known URL or use a bookmark you've setup yourself.
And, while I'm pretty sure that DuckDuckGo will not try to harm you explicitly, search engines in general (and this includes DuckDuckGo) are vulnerable against SEO (search engine optimization). And there is a kind of malicious SEO where the attacker tries to hijack phrases and place their own phishing page on top. Thus it might be possible that you'll be a victim of such malicious SEO attack if you access your bank using any search engine.
No. DuckDuckGo is just a search engine. Search engines can simply help you find your desired websites - in fact, Google is one. Some are more protected and anonymous though, some are less. But when accessing a website there are lots of other factors that can make your connection to the website unsecure:
- malware presence on your system - Keep your antivirus software updated
- MiTM attacks - Use encrypted VPNs to access the website, or use HTTPS protocols
- phishing attacks - Make sure your website address is correct
- server-side vulnerabilities (such as stored XSS) - No way around that from client side