Bot traffic: wholereach.com

all sites · all domains · last 15 days

All sites · All Domains · Visit wholereach.com

Who is really visiting wholereach.com?

Between Oct 23 and Nov 6, wholereach.com received 80,222 requests. About 72% came from automated software and about 28% look like real people.

That works out to about 10,833 human visitors, roughly 722 a day, who opened 11,293 pages between them. 460 of them read more than one page.

The biggest source is software pretending to be ordinary web browsers. It usually comes from thousands of rotating addresses to avoid being blocked, and it takes content without sending any readers back.

72%of requests from bots
10,833human visitors (estimate)
11,293pages opened by people
80,222total requests, 15 days

Where the requests came from

People 28%Named bots 11%Disguised bots 54%Scanners 6.4%Unclear 0.2%

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.

03126259371,250Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

The breakdown

SourceRequestsΣ 80,222ShareData sentBlockedby the serverWhat this means
Disguised scrapers43,30454%79 MB41,336Claims 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 people22,42828%9 MB11,220Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Search engines5,6317.0%28 MB4,829Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots2,8543.6%118 MB2,295Any other software that identifies itself as a bot.
Break-in scanners2,8373.5%77 MB8Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers2,2852.8%3 MB9Other requests from an address also caught probing for weak spots.
AI crawlers3680.5%1 MB27AI companies gathering pages or answering a user's question, and saying so.
SEO and marketing tools1920.2%<1 MB170Commercial tools that sell data about websites.
Unclear1670.2%<1 MB1Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools910.1%1 MB0Programs such as curl or Python, or anything with an unrecognizable name.
Possibly people650.1%4 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.

Named bots

Botas it names itselfTypeRequests
Epochal-SearchSearch engines4,632
AionBotOther named bots2,055
bingbotSearch engines368
ElevenlabsCrawlerOther named bots303
ClaudeBotAI crawlers260
PetalBotSearch engines254
Amzn-SearchBotSearch engines164
QlyzeBotOther named bots120
OAI-SearchBotAI crawlers82
SERankingBacklinksBotSEO and marketing tools78
SemrushBot-BASEO and marketing tools63
SeznamBotSearch engines57
GooglebotSearch engines57
RiverBotOther named bots56
ApplebotSearch engines49

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/41
/google2bf66de4f0cb84d8.html3
/fableprompts/transcript2
/insta2

How people arrived

Referring siteHuman visitors
www.google.com33
m.baidu.com10
far-uvclight.com6
austintweet.com4
podsat.com3
tvnight.com2
wordpressretreat.com1
videoretreat.com1
bastropbeat.com1
memsist.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
139.100.0.0/162,0431,731
87.232.0.0/161,9881,654
72.63.0.0/161,9411,576
94.228.0.0/161,7521,426
154.222.0.0/161,5581,292
45.204.0.0/161,5541,283
154.199.0.0/161,3941,178
207.168.0.0/16971797

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 236706743922,55621094,50270%
Oct 243183201871,13547472,42574%
Oct 252792792421,012222112,03972%
Oct 262652652781,10122172,12875%
Oct 272882891791,0921,590183,45583%
Oct 281,1451,1485013,8943496,73266%
Oct 291,0231,0273653,85565246,35967%
Oct 301,1351,1404973,63712206,44264%
Oct 311,0711,0784563,86925266,73668%
Nov 19159183584,17373067,10074%
Nov 21,0781,0804114,66935657,59772%
Nov 36526541,5583,10748996,47080%
Nov 44144183,0721,826242135,98186%
Nov 51,0461,0503484,4202496,89470%
Nov 69439532013,049201145,36264%

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