LinkDapper
Try a URL

About the LinkDapper crawler

LinkDapper fetches public web pages to build link previews. Fetches happen only when a site owner asks us to — inspecting a brand, verifying ownership, checking an installation, or refreshing a page. We do not crawl the web.

Identifying our requests

Every fetch we make carries this exact User-Agent:

LinkDapper/1.0 (+https://dapper.chicko.digital/bot)

Requests go out over HTTPS from Cloudflare Workers, which use shared egress addresses. There is no fixed IP range to allowlist — match on the User-Agent, or on the per-site crawler key below.

What we fetch, and the limits we respect

  • Site root HTML for brand inspection and ownership verification.
  • Individual page HTML for installation checks and refreshes.
  • Bounded reads: single-digit-second timeouts, megabyte-scale body caps, a small redirect budget, same-origin redirect enforcement, and HTML-only content types.

Allowing LinkDapper through bot protection

If Cloudflare Bot Fight Mode or a managed challenge blocks our fetches, add a WAF custom rule scoped to our User-Agent that skips only the challenge components. Keep rate limiting and managed rules in force.

A User-Agent alone is easy to imitate, so treat it as an identifier, not a secret. For proof that a request really is ours during brand inspection, issue a per-site crawler key in your website dashboard: LinkDapper sends it as an X-LinkDapper-Crawler-Key header with brand-inspection fetches, and your rule can match on the header value instead of — or in addition to — the User-Agent. The key is not currently sent for ownership verification, installation checks, refreshes, or automatic image generation. A rule like this skips the challenge only for brand-inspection requests carrying your key:

(http.request.headers["x-linkdapper-crawler-key"][0] eq "PASTE-YOUR-KEY")

Do not use a User-Agent-only skip while you are under an active layer-7 attack; anyone can set a User-Agent string. The header key does not have that weakness.

Blocking us

To stop our fetches entirely, add a WAF rule that blocks requests carrying our User-Agent, or write to us and we will exclude your sites. Owner-initiated features for a blocked site will report the site as unreachable.

Contact

Questions about our crawler: support@chicko.digital.