BotDB Record
LongURL API
Review firstLongURL API is a link preview bot from LongURL used for link unfurling, rich-card generation, social previews, messaging previews; it appears in server logs as `LongURL API`.
- Operator
- LongURL
- Family
- LongURL
- Type
- Link Preview Bot
- Source type
- Observed
- Last checked
- 2026-06-22
User-Agent Signal
LongURLLongURL API
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: LongURL API
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.
LongURL API is used for link unfurling, rich-card generation, social previews, messaging previews, and page metadata fetching.
Intelligence Details
BotDB fields- Operator
- LongURL
- Family
- LongURL
- Type
- Link Preview Bot
- Purpose
- Link Preview Fetching
- Identity type
- Documented
- Confidence
- Low
- Last verified
- 2026-06-22
- Last checked
- 2026-06-22
- Source type
- Observed
- Verification
- Verify LongURL API by matching `LongURL API` to LongURL evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- LongURL API has high spoofing risk because the pattern is low-confidence or observation-based; do not trust the user-agent by itself.
Notes
- LongURL API is a link preview bot from LongURL used for link unfurling, rich-card generation, social previews, messaging previews, and page metadata fetching.
- Its primary user-agent pattern is
LongURL API. - LongURL API is verified with Low confidence. The identity type is Documented, and the evidence basis is observed traffic patterns and user-agent evidence.
- LongURL API does not have confirmed robots.txt behavior in the available public evidence.
- LongURL API can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify LongURL API by matching `LongURL API` to LongURL evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- LongURL API traffic is primarily detected by the `LongURL API` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with LongURL infrastructure before trusting the traffic.
- LongURL API is used for link unfurling, rich-card generation, social previews, messaging previews, and page metadata fetching.
- LongURL API 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 EdgeMatch this signal against live requests, related datacenter traffic, and rule actions in Edge.