If you use this for something, please be sure to keep the data fresh! Especially now that new TLDs are being added at a steady clip. I once had an issue where

If you use this for something, please be sure to keep the data fresh! Especially now that new TLDs are being added at a steady clip. I once had an issue where a mobile user's browser would do a Google search every time they typed one of our domains into the URL bar. They weren't doing anything wrong - other domains worked fine. They were using some Android phone from 2013 which had been abandoned by the manufacturer, and it turned out the stock browser was using the public suffix list to decide if the input should be treated as a URL or as a search query. The list was as old as the browser, and since the domain ended in ".link" (added in 2014) it didn't think our domain was a domain. (The workaround was to type out http:// http:// or https:// https:// before the domain, but that's crappy UX.) If you use this in a server-side app, please use cron or something to keep it updated. If you embed it in a client app, make sure to update it as part of your build process. And if you know your app won't be updated very often, consider having it update separately from the app itself. (Does anyone know if this is hosted on some public CDN somewhere? I assume having a client app fetch directly from publicsuffix.org isn't kosher.) Edit: My mistake, on https://publicsuffix.org/list/ https://publicsuffix.org/list/ they do recommend having client apps pull directly from their site, and limiting updates to once per day.