Bot traffic: wholeaustin.com

all sites · all domains · last 15 days

All sites · All Domains · Visit wholeaustin.com

Who is really visiting wholeaustin.com?

Between Sep 1 and Nov 6, wholeaustin.com received 7,405 requests. About 98% came from automated software and about 0.7% look like real people.

That works out to about 26 human visitors, roughly 2 a day, who opened 30 pages between them. 4 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 1, with 1,776 requests, of which 2 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.

98%of requests from bots
26human visitors (estimate)
30pages opened by people
7,405total requests, 16 days

Where the requests came from

People 0.7%Named bots 15%Disguised bots 35%Scanners 48%Unclear 1.2%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
05001,0001,5002,000Sep 1Oct 24Oct 26Oct 28Oct 30Nov 1Nov 3Nov 5

Human visitors per day

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

036912Sep 1Oct 24Oct 26Oct 28Oct 30Nov 1Nov 3Nov 5

The breakdown

SourceRequestsΣ 7,405ShareData sentBlockedby the serverWhat this means
Break-in scanners2,97340%<1 MB0Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers1,43019%4 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.
Scripts and tools1,15316%<1 MB1Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools6618.9%<1 MB0Commercial tools that sell data about websites.
Scanners posing as browsers5857.9%<1 MB0Other requests from an address also caught probing for weak spots.
Other named bots3344.5%<1 MB0Any other software that identifies itself as a bot.
Unclear881.2%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Search engines771.0%<1 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Likely people510.7%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
No name given320.4%<1 MB0Requests that give no software name at all.
AI crawlers180.2%<1 MB0AI companies gathering pages or answering a user's question, and saying so.
Possibly people30.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
SemrushBot-BASEO and marketing tools626
leakix.netOther named bots98
ForestEngineOther named bots71
MSIE 7.0Other named bots36
DataForSeoBotSEO and marketing tools32
DuckDuckBotSearch engines28
MSIE 10.0Other named bots25
MSIE 8.0Other named bots22
bingbotSearch engines14
GooglebotSearch engines13
MSIE 5.0Other named bots12
MSIE 4.5Other named bots12
Let's Encrypt validation serverOther named bots10
PetalBotSearch engines10
ClaudeBotAI crawlers8

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/9

How people arrived

Referring siteHuman visitors
www.baidu.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
43.167.0.0/162699
43.133.0.0/1610715
43.130.0.0/164531
43.134.0.0/164227
43.157.0.0/164024
43.153.0.0/163122
43.156.0.0/163126
43.106.0.0/163130

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Sep 191211519823436193%
Sep 20058445113599.3%
Oct 240003003100.0%
Oct 25222415014419696%
Oct 26005020212326799%
Oct 272260133741028195%
Oct 2811698723118298%
Oct 293313411613427297%
Oct 3022702081832148595%
Oct 3111513264091680498%
Nov 111664831,21961,77699.5%
Nov 22211179241443998%
Nov 300104133243348399.4%
Nov 42291173453572699%
Nov 5117594305648199%
Nov 61165146301051499.6%

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 15 log files.