Bot traffic: ai.wholetech.com

all sites · all domains · last 15 days

All sites · All Domains · Visit ai.wholetech.com

Who is really visiting ai.wholetech.com?

Between Oct 23 and Nov 6, ai.wholetech.com received 30,397 requests. About 98% came from automated software and about 0.7% look like real people.

That works out to about 87 human visitors, roughly 6 a day, who opened 140 pages between them. 13 of them read more than one page.

The biggest source is scanners hunting for security holes. They try the same list of common weak spots on every site they find.

The busiest day was Oct 26, with 6,590 requests, of which 12 came from people.

Bottom line: the hit counts on the All Domains worksheet are almost entirely bots. Use the human visitor figure here to judge this site's real audience.

98%of requests from bots
87human visitors (estimate)
140pages opened by people
30,397total requests, 15 days

Where the requests came from

People 0.7%Named bots 17%Disguised bots 12%Scanners 69%Unclear 1.3%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,0004,0006,0008,000Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

Human visitors per day

Same days, people only, on their own scale so they are visible.

0481216Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

The breakdown

SourceRequestsΣ 30,397ShareData sentBlockedby the serverWhat this means
Break-in scanners15,93452%4 MB206Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers5,18017%9 MB4Other requests from an address also caught probing for weak spots.
Disguised scrapers2,7979.2%31 MB0Claims to be a normal browser but only downloads pages, never the images or icons a real browser fetches, reads many pages without ever clicking a link, or runs from a cloud provider.
AI crawlers2,1567.1%2 MB115AI companies gathering pages or answering a user's question, and saying so.
Other named bots1,8996.2%8 MB21Any other software that identifies itself as a bot.
Search engines9233.0%2 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools6832.2%2 MB0Programs such as curl or Python, or anything with an unrecognizable name.
Unclear3831.3%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2170.7%<1 MB120Commercial tools that sell data about websites.
Likely people1540.5%1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people440.1%<1 MB0Read 1 to 3 pages, arrived from a search engine or social link, no icons fetched. Referrers can be faked, so treat these as maybe.
App link sweepers190.1%<1 MB0Touches only login, app or embed links and no actual content.
No name given60.0%<1 MB0Requests that give no software name at all.
Calendar and feed apps20.0%<1 MB0Software fetching a feed for someone who subscribed.

Named bots

Botas it names itselfTypeRequests
OAI-SearchBotAI crawlers296
ExaSearchBotOther named bots293
GooglebotSearch engines291
AmazonbotAI crawlers213
ApplebotSearch engines198
bingbotSearch engines188
GPTBotAI crawlers175
DeepSeekBotAI crawlers120
CCBotAI crawlers118
ClaudeBotAI crawlers118
MoonshotBotOther named bots117
Meta-ExternalFetcherAI crawlers117
Meta-ExternalAgentAI crawlers112
QwenbotOther named bots112
HunyuanOther named bots111

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/assistants/gemini/44
/assistants/grok/15
/13
/os/5
/videos/4
/assistants/codex/2
/assistants/claude/2

How people arrived

Referring siteHuman visitors
gemini.wholetech.com41
www.google.com10
m.baidu.com1
www.wholetech.com1

Where disguised bots operate from

Address blocks, not individual addresses. A heavily used block with many addresses suggests one operator rotating through them.

Address blockRequestsAddresses used
13.219.0.0/16941
117.132.0.0/16671
163.192.0.0/16601
158.173.0.0/16576
31.44.0.0/16544
192.42.0.0/165234
45.67.0.0/16481
43.157.0.0/163923

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 238101422211812358393%
Oct 2413131422181672958390%
Oct 256521,0222912,380183,77198%
Oct 26771022586,191276,59099.4%
Oct 27221282292002758795%
Oct 28442405241,506172,29399%
Oct 2922116175695241,01397%
Oct 301112528129813461,53896%
Oct 31551231451,448251,74898%
Nov 1236731312,797163,62299.4%
Nov 2551,3381772,141153,67799.4%
Nov 3772351701,694382,14998%
Nov 4771493131893269094%
Nov 5661682664092087097%
Nov 655912583032668395%

How this was measured

Every request in the server log was sorted by what it did, not only what it claimed to be. Bots that name themselves are counted as named. Anything claiming to be a browser had to act like one: open a page, fetch its images or icons, move at human speed, and come from outside the big cloud providers. These are estimates. A careful bot can pass the test, and a person with images blocked or a cached icon can fail it, so read the human figures as a good approximation, not an exact count. One person using two devices counts as two visitors. Google Analytics-style tools would show different numbers because most bots never run their script. Logs are kept for 15 days.

Built 2026-11-06 22:42 UTC from 15 log files.