How dlvr.it identifies itself and how to control feed access

This article is for site owners and server administrators who want to understand how dlvr.it accesses their content — and how to control it.

When dlvr.it's Feed Fetcher requests content from your site, it uses the following user agent string:

You can use this string to identify dlvr.it traffic in your server logs, set up firewall rules, or configure access controls. It's the most reliable way to identify dlvr.it — more reliable than IP address filtering, which can change over time (see below).

If dlvr.it is frequently timing out when trying to fetch your feed, your server may be blocking our requests. You'll typically see this as a timeout error in your feed log.

📸 [Screenshot: dlvr.it feed log showing a timeout error next to a feed entry]

One fix is to whitelist the dlvr.it IP address in your server's incoming request settings:

Important: This IP address is subject to change. We recommend using the user agent string (dlvr.it/1.0) rather than relying solely on IP address filtering — it's a more stable long-term identifier.

If you want to control which parts of your site dlvr.it can access, you can do this through your robots.txt file.

Why doesn't dlvr.it follow User-Agent: *? dlvr.it intentionally ignores the catch-all wildcard section of robots.txt. Unlike search engine crawlers, dlvr.it only fetches content when a user explicitly adds a feed — so we don't want general crawler-blocking rules to accidentally prevent your readers from using your feeds with dlvr.it. To control dlvr.it specifically, target the dlvr.it agent directly.

Still seeing access issues after updating your settings? Reach out to our support