Bot traffic: wholetech.com

all sites · all domains · last 15 days

All sites · All Domains · Visit wholetech.com

Who is really visiting wholetech.com?

Between Oct 23 and Nov 6, wholetech.com received 4,118,028 requests. About 97% came from automated software and about 1.5% look like real people.

That works out to about 26,111 human visitors, roughly 1,741 a day, who opened 29,111 pages between them. 2,939 of them read more than one page.

The biggest source is bots that say who they are. Most of those are normal and some, like search engines, help people find the site.

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.

97%of requests from bots
26,111human visitors (estimate)
29,111pages opened by people
4,118,028total requests, 15 days

Where the requests came from

People 1.5%Named bots 90%Disguised bots 5.5%Scanners 1.4%Unclear 1.4%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
0100,000200,000300,000400,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.

01,0002,0003,0004,000Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

The breakdown

SourceRequestsΣ 4,118,028ShareData sentBlockedby the serverWhat this means
Search engines2,252,72855%306 MB669Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,452,18735%436 MB583,334Any other software that identifies itself as a bot.
Disguised scrapers211,7135.1%541 MB76,056Claims 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.
Likely people62,1321.5%104 MB28,038Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear56,5711.4%131 MB455Browser name, but fetched only an image or data file and no page. Could be either.
Break-in scanners35,4970.9%7 MB1,021Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers20,3890.5%81 MB734Other requests from an address also caught probing for weak spots.
Scripts and tools13,4400.3%73 MB12Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers8,8970.2%16 MB456AI companies gathering pages or answering a user's question, and saying so.
SEO and marketing tools3,1560.1%7 MB1,165Commercial tools that sell data about websites.
Possibly people6160.0%1 MB28Read 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 sweepers4940.0%<1 MB0Touches only login, app or embed links and no actual content.
No name given1260.0%4 MB1Requests that give no software name at all.
Automated browsers820.0%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.

Named bots

Botas it names itselfTypeRequests
ApplebotSearch engines2,230,736
KeenableBotOther named bots1,163,228
meta-webindexerOther named bots268,761
PetalBotSearch engines6,437
facebook.comOther named bots5,370
GooglebotSearch engines3,618
sogou.comSearch engines3,229
bingbotSearch engines2,751
Baiduspider-renderSearch engines2,532
ClaudeBotAI crawlers2,385
QlyzeBotOther named bots2,120
serpstatbotSEO and marketing tools1,499
OAI-SearchBotAI crawlers1,356
ReflectionbotOther named bots1,271
AionBotOther named bots1,239

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/capitalfactory/5
/about/5
/mastersitemap.html4
/faq/4
/videos.html3
/news/3
/bergeron/bnbhot.com/market-pulse.html2
/actfable/2

How people arrived

Referring siteHuman visitors
www.google.com518
m.baidu.com22
atxlot.com8
austintweet.com8
tvnight.com4
convcast.com4
earthmodel.com3
bastropbeat.com2
firth.com2
globalfilmfests.com2

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
72.63.0.0/1610,0942,400
139.100.0.0/166,6422,221
87.232.0.0/166,0982,160
94.228.0.0/164,6831,718
45.204.0.0/164,3461,210
189.81.0.0/164,0721,226
154.222.0.0/163,9971,119
154.199.0.0/163,8841,044

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23778795327,41611,2641,3813,409345,10999%
Oct 24511527314,2609,9521,1532,881329,71499%
Oct 25355361322,0967,3835,0393,929339,23199%
Oct 26391410336,2388,6228,3884,057358,75598%
Oct 27787799351,5328,9893,2683,115368,60799%
Oct 283,7343,798173,48514,6191,5902,848200,24095%
Oct 293,1343,200210,60115,4661,1272,942236,57896%
Oct 302,2222,267206,80116,1743,3293,821235,42896%
Oct 312,0912,121183,54316,6292,9792,595210,03397%
Nov 12,7052,746199,59721,1316,0515,846238,70595%
Nov 23,7073,763203,90222,0564,8594,481243,22795%
Nov 31,4601,485249,32521,5584,1664,698282,82397%
Nov 41,5701,589240,12218,8354,1126,000272,69596%
Nov 52,8602,906247,12319,4464,2363,419280,54897%
Nov 62,3112,344150,92713,7314,2082,530176,33596%

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:46 UTC from 15 log files.