ImagesiftBot
Hive (ImageSift) · Unconfirmed · robots.txt: Yes
Crawls the web for publicly available images, saving each with its page URL, page text and alt text, for Hive’s image-search and web intelligence products.
Block ImagesiftBot
User-agent: ImagesiftBot
Disallow: /
Unconfirmed by the operator Hive (ImageSift)'s documentation we checked does not say what blocking ImagesiftBot changes beyond the crawler itself.
Allow ImagesiftBot
User-agent: ImagesiftBot
Allow: /
An allow group only changes anything if a broader rule would block ImagesiftBot. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.
Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.
Already have a robots.txt? Paste it into the robots.txt checker to see whether it blocks ImagesiftBot on a given path, and which line decides.
Block or allow it at the server
robots.txt asks; a server rule refuses. Every rule here matches ImagesiftBot, spelled as in the User-Agent Hive (ImageSift) documents (“Mozilla/5.0 (compatible; ImagesiftBot; +imagesift.com)”), and matches it case-sensitively. The server answers 403.
What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user.
(Apache HTTP Server 2.4 documentation). A fake ImagesiftBot is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Hive (ImageSift)'s published addresses.
No “only the real one” rule: Hive (ImageSift) publishes no IP list file this site holds for ImagesiftBot.
The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.
Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.
Who blocks it
Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 50 block ImagesiftBot from the whole site by name, 36 block it through their User-agent: * group, and 2 name it with partial rules (some paths closed, the home page open). 0 more name it only to let it in.
50
block it by name 9.8%
36
block it through * 7.1%
2
name it, partial rules 0.4%
Percentages are of the 508 files we could read, not of all 1,000 sites.
Highest-ranked sites that block ImagesiftBot by name
- amazon.com rank 27
- yahoo.com rank 61
- msn.com rank 72
- vimeo.com rank 85
- amazonvideo.com rank 111
- snapchat.com rank 134
- tumblr.com rank 156
- nytimes.com rank 157
- cnn.com rank 205
- forbes.com rank 220
Each links to the site's live robots.txt, which may have changed since 2026-10-09.
robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.
Facts
- Operator
- Hive (ImageSift)
- Purpose
- Unconfirmed by the operator
Hive says it collects public images, with the page URL, page text and alt text, into an index its web intelligence products use for search and retrieval of similar images. It does not describe this as AI training, AI search or a user fetch.
- Obeys robots.txt
- Yes. Hive says robots.txt rules that target ImagesiftBot are respected and that it honours Crawl-delay. If no group names ImagesiftBot but one names Googlebot, it follows the Googlebot group — so a Googlebot rule can apply to it even though this site’s RFC 9309 checker reads only its own token and *.
- In your server logs
- The user-agent is "Mozilla/5.0 (compatible; ImagesiftBot; +imagesift.com)".
- How to verify it
- Unconfirmed by the operator Hive (ImageSift)'s documentation we checked gives no IP list or DNS check for this crawler, so a request claiming to be ImagesiftBot cannot be verified against the operator.
What Hive (ImageSift) says
Quoted word for word from the operator's documentation.
“ImageSiftBot is a web crawler that scrapes the internet for publicly available images to support our suite of web intelligence products”
“Once images and text are downloaded from a webpage, ImageSift analyzes this data from the page and stores the information in an index. Our web intelligence products use this index to enable search and retrieval of similar images.”
“Standard directives in robots.txt that target ImagesiftBot are respected.”
“ImagesiftBot also supports the crawl-delay directive in robots.txt files.”
“If there is no rule targeting ImagesiftBot, but there is a rule targeting Googlebot, then ImagesiftBot will follow the Googlebot directives.”
“Requests from ImageSiftBot set the User-Agent to: Mozilla/5.0 (compatible; ImagesiftBot; +imagesift.com)”
Sources
- Imagesift by Hive: ImageSift Bot — fetched and checked 2026-09-24