# Connecting to the internet **URL:** \ **Category:** Uncategorized\ **Created:** [September 28, 2018, 1:26am UTC](https://forum.kee.pm/t/connecting-to-the-internet/1594 "2018-09-28T01:26:05Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![luckyrat](https://forum.kee.pm/user_avatar/forum.kee.pm/luckyrat/32/10_2.png) [@luckyrat](https://forum.kee.pm/u/luckyrat)\ **Post date:** [September 28, 2018, 10:20am UTC](https://forum.kee.pm/t/connecting-to-the-internet/1594/2 "2018-09-28T10:20:26Z")
Funnily enough I was just discussing this in a seemingly unrelated thread: > [@Kee shows a lot of wrong matches](https://forum.kee.pm/t/kee-shows-a-lot-of-wrong-matches/1563/9): > > I think that you could have your database configured to search for domain matches (which is the default) but on one system, KeePassRPC is unable to determine what the domain name for each website is. To do this, it needs to download the relevant data from the Public Suffix List service (and store it on disk for later use). If it can never connect to the internet to collect this data, it will have to fall back to hostname matching which in some cases (such as the [accounts.google.com](http://accounts.google.com) example) wil… Cloudfront is one of the largest CDNs on the internet so it’s not a surprise that the PSL service is hosted there, although there’s certainly no guarantee it will remain that way. Nor is there a guarantee that it is the PSL that your KeePass instance is trying to connect to - you’d have to dig into more details in a network and/or process monitoring tool to prove this or look through the source code to verify where the plugin connects to. Essentially, KeePassRPC will not work very well without access to the internet, but it will still function to a degree, and in a way that ensures the fallback behaviour is stricter so no security or privacy problems are introduced if it is unable to connect to the internet for any reason. --- _[View the full topic](https://forum.kee.pm/t/connecting-to-the-internet/1594)._