🤖 Overview

Drip is a legitimate web crawler operated by Drip.com (now part of Leadpages), an email marketing and CRM platform launched in 2012. Its primary purpose is to verify the validity and safety of hyperlinks embedded within Drip email campaigns, ensuring that links are not broken or pointing to malicious content before emails are sent. The crawler also scans customer-submitted websites to generate link previews and content snapshots for email personalization features. Documentation on Drip’s official help center confirms this verification role.

🌐 Technical Behavior

The Drip crawler originates from a fixed set of IP addresses documented in Drip’s support article “What IP addresses does Drip use?” — primarily within the range 52.33.236.0/22 and 52.33.240.0/22 (AWS EC2 us-west-2). It makes a moderate number of requests per crawl session, typically fetching only the specific pages that contain tracked links or embedded content, rather than performing deep site-wide scans. The crawler uses standard HTTP/1.1 over port 80 and 443, and follows redirects up to a limit of 5 hops. Request frequency is capped at approximately 10–15 requests per minute per website to avoid excessive load, as stated in Drip’s infrastructure documentation. The bot does not execute JavaScript and only retrieves static HTML responses.

📋 robots.txt Compliance

Drip’s crawler fully respects robots.txt directives, as confirmed by official support documentation that advises customers to use Disallow rules if they wish to block the bot. It reads the robots.txt file at the beginning of each crawl session and adheres to both User-agent and Disallow instructions, with no known instances of ignoring exclusions.

🔍 Detection Indicators

The primary User-Agent string is Drip/1.0 (e.g., “Drip/1.0 (http://drip.com)”) along with an alternate variant “DripBot/1.0”. The bot also sends a X-Drip-Crawler: true header in requests, a behavioral fingerprint unique to this crawler. Absence of a Referer header and a consistent request interval of ~4–6 seconds between pages further aid identification.

📊 Data Usage

Collected data — primarily link status codes (200, 404, etc.) and basic HTML content — is used exclusively for link validation and email campaign integrity within Drip’s platform. No content is stored for AI training or search indexing; data is discarded after verification unless needed for analytics dashboards showing link click-through rates. Drip’s privacy policy explicitly states that scraping data is not shared with third parties.

⚙️ Rate Limiting Policy

The Drip crawler is rate-limited on the application side because its verification runs can spike to tens of thousands of simultaneous requests across a customer base, and threshold-based blocking prevents downstream site overload or disruption of normal traffic, as recommended by Drip’s own support guidelines for integration partners.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.