Does LCC respect robots.txt?

Not documented. No operator statement says whether LCC reads robots.txt, so add the rule but verify in your logs that the requests actually stop.

Add the LCC token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.

IPScanner

Data scrapers and resellers

LCC

Q: How do I verify a request really came from LCC?

You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.

LCC is a bot that crawls pages into a dataset that is then reused or sold, and its operator has not been publicly identified. The token has been seen in server logs, but no operator has published documentation for it. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.

No operator has published documentation for this token. Everything below is what can be established from the string itself and from how the traffic behaves. We would rather say that than fill the gap with a guess.

LCC at a glance

Reference data for the LCC crawler
User agent	`LCC` Token only. The operator has not published a full user-agent string, so match on the substring rather than an exact header.
Operator	Not publicly identified
Purpose	Data scrapers and resellers
Respects robots.txt	Not documented
Verification method	None published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof.
Crawl pattern	Not published
Robots.txt tokens	`LCC`
Operator documentation	None published

robots.txt

Allow or block LCC

Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.

Block LCC

User-agent: LCC
Disallow: /

Blocks every path for this crawler only.

Allow LCC

User-agent: LCC
Allow: /

Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.

Allow, except the pages you never want quoted

User-agent: LCC
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /search

Edit the Disallow paths to match your own account, checkout and search URLs.

What blocking actually costs you

Blocking LCC stops your content being packaged and resold to third parties. Whoever bought earlier crawls still has them.

Block every crawler in the directory at once

Verification

Is that really LCC?

A user-agent header is a string the client chooses. Scrapers copy LCC precisely because site owners allow it. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof.

Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.

Datacenter IP detectionNearly every real AI crawler egresses from cloud ranges. A residential IP claiming to be one is the first thing to check.IP reputation checkSee whether the address behind a fake crawler hit has a history of abuse elsewhere.Residential proxy detectionScrapers that get blocked by user agent often come back through residential proxy pools.

Related crawlers

YandexAdditionalYandex · Data scrapers and resellers AgentTimesThe Agent Times · Data scrapers and resellers aiHitBotaiHit · Data scrapers and resellers AIWebIndexOperator unknown · Data scrapers and resellers ApifyBotOperator unknown · Data scrapers and resellers

Agentscan

Identify crawlers automatically instead of by hand

Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.

How Agentscan works API reference Pricing What is my IP

FAQ

LCC