This article is for site owners and server administrators who want to understand how dlvr.it accesses their content — and how to control it.
How dlvr.it identifies itself
When dlvr.it’s Feed Fetcher requests content from your site, it uses the following user-agent string:
dlvr.it/1.0 (+http://dlvr.it/)
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, since our IP can change over time (see below).
Allowlisting dlvr.it’s IP address
If dlvr.it is frequently timing out when it tries to fetch your feed, your server may be blocking our requests. You’ll typically see this as a timeout error in your feed log — see also My RSS feed works in a browser but times out in dlvr.it.
One fix is to allowlist the dlvr.it IP address in your server’s incoming-request settings:
54.213.123.74
This IP address can change
Identify dlvr.it by its user-agent string (dlvr.it/1.0) rather than relying on IP-address filtering — it’s a more stable long-term identifier.
Control access with robots.txt
To control which parts of your site dlvr.it can access, use 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 general crawler-blocking rules shouldn’t accidentally stop your readers from using your feeds with dlvr.it. To control dlvr.it specifically, target the dlvr.it agent directly.
Block a specific feed path
User-Agent: dlvr.it
Disallow: /path/to/your/feeds
Block all content on your site
User-Agent: dlvr.it
Disallow: /
Block most of your site but allow specific feeds
User-Agent: dlvr.it
Disallow: /
Allow: /path/to/some/feeds
Allow everything
A plain Disallow with no path means “allow all”:
User-Agent: dlvr.it
Disallow:
Still need help?
Still seeing access issues after updating your settings? Reach out to our support team — we’re happy to help.