Bot intelligence record

Sendcloud

Review first

Sendcloud is a service Client used for Sendcloud is used for Sendcloud may make automated HTTP requests for shipping, logistics, integration; it appears in server logs as `Sendcloud`.

Service Client Shipping Automation Documented Confidence: Medium Verified: No robots.txt: Unknown
Operator
Sendcloud
Family
Sendcloud
Source type
Documented
Last checked
2026-06-22

User-Agent Pattern

Sendcloud
Sendcloud
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: Sendcloud
Disallow: /

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

Handling Guidance

Depends

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

Sendcloud is used for Sendcloud may make automated HTTP requests for shipping, logistics, integration, and fulfillment workflows.

Record Details

Verified fields
Operator
Sendcloud
Family
Sendcloud
Type
Service Client
Purpose
Shipping Automation
Identity type
Documented
Confidence
Medium
Last verified
2026-06-22
Last checked
2026-06-22
Source type
Documented
Verification
Verify Sendcloud by matching `Sendcloud` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
Spoofing risk
Sendcloud has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.

Notes

  • Sendcloud is a service Client used for Sendcloud is used for Sendcloud may make automated HTTP requests for shipping, logistics, integration, and fulfillment workflows.
  • Its primary user-agent pattern is Sendcloud; related patterns include Sendcloud/1.0.0; Sendcloud integration client.
  • Sendcloud is not independently verified with Medium confidence. The identity type is Documented, and the evidence basis is documented crawler-pattern evidence.
  • Sendcloud does not have confirmed robots.txt behavior in the available public evidence.
  • Sendcloud should be reviewed against site policy, source evidence, crawl rate, and requested paths before a permanent allow or block rule is created.

Evidence and Source

  • Verify Sendcloud by matching `Sendcloud` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
  • Sendcloud traffic is primarily detected by the `Sendcloud` user-agent pattern; related patterns include `Sendcloud/1.0.0; Sendcloud integration client`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
  • Sendcloud is used for Sendcloud may make automated HTTP requests for shipping, logistics, integration, and fulfillment workflows.
  • Sendcloud has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.

Use This Signal In Edge

Botcrawl Edge

Use Edge to match live requests, detect related datacenter traffic, and apply allow, block, rate-limit, or log rules.

Open Edge Open in Edge BotDB