Bot traffic: wholehomebuild.com

all sites · all domains · last 15 days

All sites · All Domains · Visit wholehomebuild.com

Who is really visiting wholehomebuild.com?

Between Oct 23 and Nov 6, wholehomebuild.com received 9,272 requests. About 95% came from automated software and about 2.3% look like real people.

That works out to about 39 human visitors, roughly 3 a day, who opened 46 pages between them. 5 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 3, with 1,701 requests, of which 0 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.

95%of requests from bots
39human visitors (estimate)
46pages opened by people
9,272total requests, 15 days

Where the requests came from

People 2.3%Named bots 22%Disguised bots 16%Scanners 56%Unclear 3.0%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
05001,0001,5002,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.

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

The breakdown

SourceRequestsΣ 9,272ShareData sentBlockedby the serverWhat this means
Break-in scanners2,87331%<1 MB7Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers2,33925%29 MB9Other requests from an address also caught probing for weak spots.
Disguised scrapers1,45116%29 MB6Claims 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 engines8639.3%18 MB5Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers5145.5%1 MB5AI companies gathering pages or answering a user's question, and saying so.
Other named bots4855.2%10 MB2Any other software that identifies itself as a bot.
Unclear2743.0%2 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2152.3%10 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools1822.0%2 MB151Commercial tools that sell data about websites.
Scripts and tools710.8%<1 MB0Programs such as curl or Python, or anything with an unrecognizable name.
No name given40.0%<1 MB0Requests that give no software name at all.
Possibly people10.0%<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
PetalBotSearch engines549
GPTBotAI crawlers276
ClaudeBotAI crawlers133
SemrushBot-BASEO and marketing tools117
bingbotSearch engines107
GooglebotSearch engines86
ibou-searchOther named bots79
Amzn-SearchBotSearch engines63
ReflectionbotOther named bots45
OAI-SearchBotAI crawlers41
SEOJuice-SearchBotOther named bots38
CensysInspectOther named bots34
SeznamBotSearch engines30
SemrushBotSEO and marketing tools28
archive.org_botOther named bots24

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/30
/directory/4
/concepts/2
/topics/2

How people arrived

Referring siteHuman visitors
www.google.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/1612320
104.164.0.0/16815
103.4.0.0/16332
185.220.0.0/16326
103.196.0.0/16211
177.249.0.0/16172
158.173.0.0/16173
5.9.0.0/16151

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23331096652422580%
Oct 246799176687221,04292%
Oct 25221365842923186%
Oct 26571139032325481%
Oct 27111091033481457697%
Oct 28001377610923296%
Oct 292598132526877498%
Oct 303315182962036690%
Oct 3133135545001370797%
Nov 1111122253421169298%
Nov 244215120257861996%
Nov 300356951,236141,70199.2%
Nov 48896676204287490%
Nov 511117991511838795%
Nov 61161834271959296%

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.