Bot intelligence record
FeedBurner
Review firstFeedBurner is a feed fetcher from Google FeedBurner used for RSS or Atom feed polling, syndication refresh, subscription delivery; it appears in server logs as `FeedBurner`.
- Operator
- Google FeedBurner
- Family
- Google FeedBurner
- Type
- Feed Fetcher
- Source type
- Official
- Last checked
- 2026-06-23
User-Agent Pattern
Google FeedBurnerFeedBurner
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: FeedBurner
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
AllowUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
FeedBurner is used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
Record Details
Structured data- Operator
- Google FeedBurner
- Family
- Google FeedBurner
- Type
- Feed Fetcher
- Purpose
- Feed Fetching
- Identity type
- Documented
- Confidence
- High
- Last verified
- 2026-06-23
- Last checked
- 2026-06-23
- Source type
- Official
- Verification
- Verify FeedBurner by matching `FeedBurner` to Google FeedBurner evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- FeedBurner has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
Notes
- FeedBurner is a feed fetcher from Google FeedBurner used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
- Its primary user-agent pattern is
FeedBurner. - FeedBurner is verified with High confidence. The identity type is Documented, and the evidence basis is official operator documentation.
- FeedBurner is marked as respecting robots.txt directives for crawler access control.
- FeedBurner can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify FeedBurner by matching `FeedBurner` to Google FeedBurner evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- FeedBurner traffic is primarily detected by the `FeedBurner` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Google FeedBurner infrastructure before trusting the traffic.
- FeedBurner is used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
- FeedBurner has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.