Bot traffic: ame.wholereach.com

all sites · all domains · last 15 days

All sites · All Domains · Visit ame.wholereach.com

Who is really visiting ame.wholereach.com?

Between Oct 25 and Nov 6, ame.wholereach.com received 1,214 requests. About 96% came from automated software and about 0.6% look like real people.

That works out to about 4 human visitors, roughly fewer than 1 a day, who opened 7 pages between them. 3 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 Nov 4, with 251 requests, of which 1 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.

96%of requests from bots
4human visitors (estimate)
7pages opened by people
1,214total requests, 13 days

Where the requests came from

People 0.6%Named bots 28%Disguised bots 5.7%Scanners 61%Unclear 3.9%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
075150225300Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

Human visitors per day

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

01234Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

The breakdown

SourceRequestsΣ 1,214ShareData sentBlockedby the serverWhat this means
Break-in scanners51843%<1 MB0Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers22819%<1 MB1Other requests from an address also caught probing for weak spots.
AI crawlers20617%<1 MB0AI companies gathering pages or answering a user's question, and saying so.
Other named bots796.5%<1 MB1Any other software that identifies itself as a bot.
Disguised scrapers594.9%<1 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.
Unclear473.9%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Search engines423.5%<1 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
SEO and marketing tools181.5%<1 MB4Commercial tools that sell data about websites.
Scripts and tools100.8%<1 MB0Programs such as curl or Python, or anything with an unrecognizable name.
Possibly people70.6%<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.

Named bots

Botas it names itselfTypeRequests
ClaudeBotAI crawlers173
GPTBotAI crawlers17
RiverBotOther named bots17
PetalBotSearch engines16
OAI-SearchBotAI crawlers16
bingbotSearch engines14
ru-linkindexOther named bots12
SERankingBacklinksBotSEO and marketing tools12
facebook.comOther named bots11
CensysInspectOther named bots9
ElevenlabsCrawlerOther named bots8
ibou-searchOther named bots6
UmaiBotOther named bots5
Amzn-SearchBotSearch engines4
SemrushBotSEO and marketing tools4

How people arrived

Referring siteHuman visitors
www.google.com3
m.baidu.com1

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 250097011794%
Oct 26003913055791%
Oct 270045382313398%
Oct 2800403054890%
Oct 29001442524596%
Oct 3000268023694%
Oct 31004423318099%
Nov 100496136319498%
Nov 20040684913994%
Nov 33697145317095%
Nov 411100238225199%
Nov 500104041878%
Nov 600106372673%

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:41 UTC from 13 log files.