BotDB Record

ApacheBench

Review first

ApacheBench is an HTTP Client from Apache HTTP Server Project used for ApacheBench is used for Automated website access, content retrieval, or integration activity associated with the listed operator; it appears in server logs as `ApacheBench`.

Http Client Automated Http Requests Documented Confidence: Low Verified: Yes robots.txt: Unknown
Source type
Observed
Last checked
2026-06-22

User-Agent Signal

Apache HTTP Server Project
ApacheBench
Verification note

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 copy
User-agent: ApacheBench
Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Monitor

Use this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.

ApacheBench is used for Automated website access, content retrieval, or integration activity associated with the listed operator.

Intelligence Details

BotDB fields
Purpose
Automated Http Requests
Identity type
Documented
Confidence
Low
Last verified
2026-06-22
Last checked
2026-06-22
Source type
Observed
Verification
Verify ApacheBench by matching `ApacheBench` to Apache HTTP Server Project evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
Spoofing risk
ApacheBench has high spoofing risk because the pattern is low-confidence or observation-based; do not trust the user-agent by itself.

Notes

  • ApacheBench is an HTTP Client from Apache HTTP Server Project used for ApacheBench is used for Automated website access, content retrieval, or integration activity associated with the listed operator.
  • Its primary user-agent pattern is ApacheBench.
  • ApacheBench is verified with Low confidence. The identity type is Documented, and the evidence basis is observed traffic patterns and user-agent evidence.
  • ApacheBench does not have confirmed robots.txt behavior in the available public evidence.
  • ApacheBench should be monitored first, then rate-limited or blocked if the crawl rate, paths, or behavior are unwanted.

Evidence and Source

  • Verify ApacheBench by matching `ApacheBench` to Apache HTTP Server Project evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
  • ApacheBench traffic is primarily detected by the `ApacheBench` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Apache HTTP Server Project infrastructure before trusting the traffic.
  • ApacheBench is used for Automated website access, content retrieval, or integration activity associated with the listed operator.
  • ApacheBench has high spoofing risk because the pattern is low-confidence or observation-based; do not trust the user-agent by itself.

Use in Botcrawl Edge

Botcrawl Edge

Match this signal against live requests, related datacenter traffic, and rule actions in Edge.