Bot traffic: commercialaustin.com

all sites · all domains · last 15 days

All sites · All Domains · Visit commercialaustin.com

Who is really visiting commercialaustin.com?

Between Oct 23 and Nov 6, commercialaustin.com received 44,162 requests. About 98% came from automated software and about 0.9% look like real people.

That works out to about 99 human visitors, roughly 7 a day, who opened 143 pages between them. 37 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.

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
99human visitors (estimate)
143pages opened by people
44,162total requests, 15 days

Where the requests came from

People 0.9%Named bots 9.8%Disguised bots 8.9%Scanners 80%Unclear 0.6%

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.

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

The breakdown

SourceRequestsΣ 44,162ShareData sentBlockedby the serverWhat this means
Break-in scanners27,84063%32 MB14,955Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,45317%31 MB32Other requests from an address also caught probing for weak spots.
Disguised scrapers2,6516.0%19 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.
AI crawlers1,5283.5%3 MB120AI companies gathering pages or answering a user's question, and saying so.
Other named bots1,5113.4%7 MB32Any other software that identifies itself as a bot.
Scripts and tools1,1912.7%9 MB4Programs such as curl or Python, or anything with an unrecognizable name.
Search engines1,1432.6%7 MB18Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Likely people3220.7%20 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear2660.6%3 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1260.3%<1 MB61Commercial tools that sell data about websites.
Possibly people580.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.
Automated browsers550.1%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
No name given170.0%<1 MB0Requests that give no software name at all.
App link sweepers10.0%<1 MB1Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
GooglebotSearch engines329
ClaudeBotAI crawlers303
PetalBotSearch engines235
bingbotSearch engines183
pathscanOther named bots167
OAI-SearchBotAI crawlers138
BytespiderAI crawlers99
ApplebotSearch engines89
GPTBotAI crawlers88
Kimi-SearchBotOther named bots85
SeznamBotSearch engines83
BravebotOther named bots83
QwenbotOther named bots83
ChatGPT-UserAI crawlers82
BaiduspiderSearch engines79

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/80
/news/4
/rss-api3
/faq/2

How people arrived

Referring siteHuman visitors
m.baidu.com19
austintweet.com10
www.google.com6
www.bing.com2
www.google.com.hk1

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
45.138.0.0/161683
102.129.0.0/161382
192.42.0.0/1610426
167.235.0.0/16991
104.164.0.0/16725
158.69.0.0/16551
204.8.0.0/16444
5.102.0.0/16433

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23341152002,14392,48099.1%
Oct 241317881731,266161,60795%
Oct 25113421672,46262,97899.8%
Oct 2610132612344,62675,14799.5%
Oct 27911912952,844123,26499%
Oct 289121791351,326371,71396%
Oct 29579939966641,18199%
Oct 3012146052011,722332,60997%
Oct 31361041644,213134,50599.5%
Nov 117246931,2192,406404,42997%
Nov 2466492043,839214,72499.3%
Nov 39113931512,775153,35899%
Nov 4235271341,803142,48199.3%
Nov 59101001582,176282,50197%
Nov 63462811,026111,18599%

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.