Bot traffic: aiaustintexas.com

all sites · all domains · last 15 days

All sites · All Domains · Visit aiaustintexas.com

Who is really visiting aiaustintexas.com?

Between Oct 23 and Nov 6, aiaustintexas.com received 22,513 requests. About 97% came from automated software and about 2.1% look like real people.

That works out to about 168 human visitors, roughly 11 a day, who opened 209 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.

97%of requests from bots
168human visitors (estimate)
209pages opened by people
22,513total requests, 15 days

Where the requests came from

People 2.1%Named bots 26%Disguised bots 23%Scanners 47%Unclear 1.2%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,0002,0003,0004,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.

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

The breakdown

SourceRequestsΣ 22,513ShareData sentBlockedby the serverWhat this means
Break-in scanners5,76526%11 MB1,816Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers4,92622%17 MB64Other requests from an address also caught probing for weak spots.
Disguised scrapers3,87217%41 MB8Claims 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.
Other named bots2,48911%19 MB20Any other software that identifies itself as a bot.
Search engines1,9798.8%15 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools1,3996.2%15 MB5Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers1,1185.0%7 MB52AI companies gathering pages or answering a user's question, and saying so.
Likely people3691.6%26 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear2751.2%5 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2090.9%<1 MB143Commercial tools that sell data about websites.
Possibly people1070.5%<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.
No name given40.0%<1 MB0Requests that give no software name at all.
App link sweepers10.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines668
RiverBotOther named bots574
QlyzeBotOther named bots484
GooglebotSearch engines482
ClaudeBotAI crawlers266
Amzn-SearchBotSearch engines246
bingbotSearch engines226
ExaSearchBotOther named bots216
OAI-SearchBotAI crawlers202
ElevenlabsCrawlerOther named bots156
SemrushBotSEO and marketing tools140
SeznamBotSearch engines94
ibou-searchOther named bots81
ApplebotSearch engines71
GPTBotAI crawlers69

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/90
/directory/12
/live/10
/events/8
/about/4
/directory.html3
/news/2026-05-05-emerson-ut-austin-semiconductor-ai-partnership2
/news/2026-05-19-austin-ai-traffic-signals-smart-transportation-upgrades.html2
/videos/2

How people arrived

Referring siteHuman visitors
www.google.com51
m.baidu.com19
memsist.com7
duckduckgo.com5
www.bing.com3
austinhangout.com2
www.google.co.uk1
claudefieldguide.com1
fableguide.com1
search.brave.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/1643464
158.69.0.0/162922
47.82.0.0/168985
185.220.0.0/168344
5.102.0.0/16803
148.135.0.0/16702
104.164.0.0/166010
173.46.0.0/16587

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2315168441771,374222,44998%
Oct 2446186341789131,34098%
Oct 2577212201491349394%
Oct 261418732333755181,88097%
Oct 271925342520507111,41497%
Oct 28692992651,414162,01798%
Oct 297917324080851995%
Oct 301315203196540501,05389%
Oct 3168259195576111,05398%
Nov 122277921,571889173,34597%
Nov 214146142322,220153,11698%
Nov 31315200180702141,12097%
Nov 41216236299693066791%
Nov 5101357637970591,68499%
Nov 6911127147222836382%

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.