Alibaba
Qwen-User
Qwen fetching a page to answer someone's question.
When you see it: Someone asked Alibaba's assistant something and it opened your page.
How we check it is really Alibaba
- 01
The user agent has to contain Qwen-User.
Alibaba publishes neither IP ranges nor a reverse DNS record, so this is the honest ceiling: the visit is recorded as a claim. We would rather show you an unverified row than a tick we cannot back.
What each result means
- verified
- The address matched Alibaba's own published records. This really was them.
- unverified
- We could not confirm it, and that is all it means. The operator may publish nothing to check against, a published list may be behind the addresses actually in use, or DNS may simply have been slow. It is not an accusation.
- spoofed
- The address belongs to somebody else — its own reverse DNS record resolves to a different owner. That is positive evidence of a forgery rather than a failure to find evidence, which is why it is reported as its own result and never folded into the row above.
The distinction costs nothing to make and is the reason these numbers can be shown to someone who will ask where they came from. A report that cannot separate “we do not know” from “this was faked” invites exactly one question it cannot answer.
No list to check against
Alibaba publishes neither an address file nor a reverse DNS record for this crawler. There is nothing to check a request against, which is why every visit from it is recorded as an unverified claim.
- Operator
- Alibaba
- Token
- Qwen-User
- Counted as
- AI assistant
- Verification
- User agent only
- Runs JavaScript
- No
- Operator docs
- Published
User agent
Qwen-UserMatched as a token, not as a full browser string. Alibaba adds and changes the version and product text around it without notice, so a filter pinned to the whole header stops working the first time they bump a version while one matching Qwen-User keeps working. The same string is what Alibaba names in robots.txt.
Alibaba's other crawlers
Alibaba sends 3 crawlers, each with its own token and its own job. They are counted separately for that reason — the tokens differ by a few characters and what the fetch means does not, so folding them into one operator row would let indexing look like AI interest.
Your analytics never mentioned Qwen-User because it cannot see it.
This crawler takes your HTML and leaves without running a line of JavaScript, so a browser tag records nothing. TrueStat reads it server-side, checks the address, and shows you which pages it fetched — including the ones that returned a 404.