Kinya (勤哉)

Crawler identity

KinyaBot

We operate KinyaBot, the Kinya web crawler. It visits a site for one of two reasons: a customer owns the site or has asked us to analyse it, or we are testing the crawler itself against real public pages that the site’s robots rules leave open to crawlers.

At a glance

User-Agent
KinyaBot/1.0 (+https://www.kinya.ai/bot)
robots.txt token
KinyaBot
Dedicated egress
2.28.52.200/32
Operated by
Kinya
Legal name
Rhino Rank LTD
Company number
10849738
Registered address
5 Knights Court Archers Way, Battlefield Enterprise Park, Shrewsbury, Shropshire, England, SY1 3GA
Jurisdiction
United Kingdom
Contact
[email protected]
Machine-readable
/bot/identity.json
Full documentation for providers and operatorshttps://app.kinya.ai/bot

Why it visits

Two reasons KinyaBot requests a page

  • Analysis for a Kinya customer

    A customer owns the site, or has authorized us to analyse it. KinyaBot collects the page source and technical SEO evidence we need to set that site up, then revisits it so the analysis stays current as the site changes.

  • Testing the crawler itself

    We also run the crawler against real public pages to check its own quality: that it reads real-world markup correctly, works across different server setups, and keeps its request rate reasonable. These runs are bounded, and limited to public paths that the site’s applicable robots.txt rules do not block for KinyaBot or for crawlers generally.

Either way it reads the same things: it requests pages over HTTP and reads the source your server returns, together with the response status and headers. It reads your robots.txt first and applies it to the crawling those rules cover.

How it behaves

What KinyaBot commits to on every crawl

  • It reads robots.txt first

    KinyaBot fetches your robots.txt before it crawls, matches rules against the product token KinyaBot, and follows the rules that apply to it.

  • It keeps requests bounded

    A crawl runs to a bounded number of requests. KinyaBot does not take as much of your server as it can get.

  • It backs off when your server says so

    A 429 or 503 response, a Retry-After header, a challenge page, or a sign that the origin is under strain makes KinyaBot slow down or stop.

  • It never works around a block

    KinyaBot does not attempt to evade blocks or challenges. If you shut it out, it stays out.

Control it

Control KinyaBot from your robots.txt

Add one of these groups to the robots.txt at the root of your domain. KinyaBot matches the token KinyaBot, case-insensitively, and the token never changes between versions.

  • Allow KinyaBot everywhere

    # Allow KinyaBot everywhere
User-agent: KinyaBot
Allow: /

  • Block KinyaBot entirely

    # Block KinyaBot entirely
User-agent: KinyaBot
Disallow: /

  • Keep KinyaBot out of one area

    # Allow KinyaBot, except these paths
User-agent: KinyaBot
Disallow: /cart/
Disallow: /search
Allow: /
  • If your robots.txt has no KinyaBot group, KinyaBot applies the rules under User-agent: *. Site owners often assume the opposite.
  • A change applies from the next time KinyaBot reads your robots.txt.
  • robots.txt is a crawl control, not a grant of permission, and the two uses above draw their authority from different places. Analysis for a customer is authorized by the customer who owns the site or asked us to analyse it. Our own crawler testing has no customer behind it: it uses public paths that the applicable robots rules do not block for KinyaBot or for crawlers generally.
  • In both cases KinyaBot obeys every disallowed path, backs off on signals that an origin is under strain, and never evades a block or a challenge.

Dedicated egress

This is KinyaBot’s complete current dedicated egress list

Production KinyaBot traffic leaves from exactly one address, published here as 2.28.52.200/32. That host is used solely by KinyaBot. Customers and providers may match that exact /32 in addition to the exact User-Agent.

  • The User-Agent alone remains spoofable. Anything can send KinyaBot/1.0 (+https://www.kinya.ai/bot). Matching the published address is how you verify origin by network address.
  • Address publication is not authorization. Publishing the address proves the request came from KinyaBot’s dedicated host. It does not grant us permission to crawl a site.
  • Robots, rate bounds, and customer authorization remain controlling. A matching address does not override robots.txt, does not raise a rate ceiling, and does not replace the customer authorization that analysis crawls require.
  • Address changes are published before new production traffic uses them. This page and /bot/identity.json are updated first.

Verification

How to confirm a request is KinyaBot’s

Match the exact User-Agent together with the dedicated egress address published above. The User-Agent alone is spoofable; the address is the network-level proof. Nothing beyond these two exists today:

  • No reverse-DNS name or public signing key. KinyaBot has no crawler DNS suffix, no PTR record and no request-signing key, so neither a reverse-DNS lookup nor a signature check can confirm a request. Privately configured Shopify merchant headers apply only to that exact storefront.
  • No verified-bot listing. KinyaBot is not registered with any CDN, host or security-vendor verified-bot programme.
  • No pause control inside our product. The controls are your robots.txt and the mailbox below.

Contact us about a crawl

Email us at [email protected] to ask for KinyaBot to be allowed, blocked, or kept out of part of a site you run — or to report a crawl that caused a problem.

What to include

  • The hostname affected.
  • Roughly when the requests arrived, and the time zone.
  • A request ID, or the matching log lines, if you have them.
  • What you want to happen: KinyaBot allowed, blocked, or limited to part of the site.

Please do not send credentials, private content, or raw logs containing personal data. The matching lines are enough.

Email [email protected]

Published 21 August 2026. This page is the address inside KinyaBot’s User-Agent header, so it will not move.