Bot traffic: aiwholetech.com

all sites · all domains · last 15 days

All sites · All Domains · Visit aiwholetech.com

Who is really visiting aiwholetech.com?

Between Oct 23 and Nov 6, aiwholetech.com received 28,751 requests. About 99% came from automated software and about 0.5% look like real people.

That works out to about 72 human visitors, roughly 5 a day, who opened 87 pages between them. 15 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 5,849 requests, of which 17 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.

99%of requests from bots
72human visitors (estimate)
87pages opened by people
28,751total requests, 15 days

Where the requests came from

People 0.5%Named bots 21%Disguised bots 15%Scanners 63%Unclear 0.8%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,5003,0004,5006,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.

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

The breakdown

SourceRequestsΣ 28,751ShareData sentBlockedby the serverWhat this means
Break-in scanners12,56844%2 MB2,016Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers5,45819%6 MB69Other requests from an address also caught probing for weak spots.
Disguised scrapers3,72613%25 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.
Search engines2,3638.2%14 MB3Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,9236.7%9 MB13Any other software that identifies itself as a bot.
AI crawlers1,1634.0%4 MB32AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools6292.2%12 MB0Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools5451.9%2 MB154Commercial tools that sell data about websites.
Unclear2350.8%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people920.3%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people410.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 sweepers60.0%<1 MB0Touches only login, app or embed links and no actual content.
No name given20.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,109
ClaudeBotAI crawlers584
QlyzeBotOther named bots538
Amzn-SearchBotSearch engines518
RiverBotOther named bots316
ElevenlabsCrawlerOther named bots306
SERankingBacklinksBotSEO and marketing tools291
GooglebotSearch engines210
bingbotSearch engines198
SemrushBotSEO and marketing tools152
OAI-SearchBotAI crawlers136
BaiduspiderSearch engines123
SeznamBotSearch engines69
BacklinksExtendedBotOther named bots66
ibou-searchOther named bots61

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/45
/no-ai-slop/10
/news/2

How people arrived

Referring siteHuman visitors
www.google.com17
memsist.com16
claudefieldguide.com2
m.baidu.com2
www.baidu.com2
fableguide.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
192.42.0.0/1624661
47.82.0.0/16204194
66.249.0.0/1618417
93.123.0.0/161462
64.16.0.0/168113
5.102.0.0/16553
43.157.0.0/165219
82.26.0.0/16529

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2345313415991221,74898%
Oct 2444190417709101,33099%
Oct 2556782152496131,45398%
Oct 26997402784,796185,84999.4%
Oct 2710123424401,717112,52699%
Oct 28233381761,322101,85299.1%
Oct 29893051951,591112,11899%
Oct 3022504413703271,64998%
Oct 3136234169809141,23698%
Nov 133346505734121,60299%
Nov 2447363021,027102,08399.1%
Nov 3452401551,224101,63499.1%
Nov 4792752773953499495%
Nov 5452143003551689198%
Nov 6354351691,157171,78699%

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.