Overview
Parse.ly is a monitoring bot used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Its primary user-agent pattern is parsely.com; a representative HTTP user-agent is Mozilla/5.0 (compatible; parse.ly scraper/0.16; +http://parsely.com).
Parse.ly is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is a public crawler reference or source-linked documentation.
Parse.ly is marked as respecting robots.txt directives for crawler access control.
Parse.ly can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
parsely.com - HTTP Agent Examples
-
Mozilla/5.0 (compatible; parse.ly scraper/0.16; +http://parsely.com) - Robots Token
- parsely.com
- Identity Type
- Verified bot
- Evidence Method
- Verify Parse.ly by matching `parsely.com` to a public crawler reference or source-linked documentation, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
Classification
- Type
- Monitoring
- Kind
- Monitor
- Family
- Parse.ly
- Purpose
- Monitoring
Behavior and handling
- Common Use
- Parse.ly is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Detection Notes
- Parse.ly traffic is primarily detected by the `parsely.com` user-agent pattern; a representative HTTP user-agent is `Mozilla/5.0 (compatible; parse.ly scraper/0.16; +http://parsely.com)`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Respects robots.txt
- Yes
- Spoofing Risk
- Parse.ly has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Safe
- Recommended Handling
- Do not block
Rules and controls
- Robots.txt Snippet
-
User-agent: parsely.com Disallow: /
Relationships
- Operator
- Parse.ly Checked 2026-06-23
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.