Bot traffic: austin.com.co

all sites · all domains · last 15 days

All sites · All Domains · Visit austin.com.co

Who is really visiting austin.com.co?

Between Oct 23 and Nov 6, austin.com.co received 32,645 requests. About 97% came from automated software and about 1.5% look like real people.

That works out to about 143 human visitors, roughly 10 a day, who opened 199 pages between them. 56 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 5, with 8,159 requests, of which 65 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.

97%of requests from bots
143human visitors (estimate)
199pages opened by people
32,645total requests, 15 days

Where the requests came from

People 1.5%Named bots 12%Disguised bots 21%Scanners 64%Unclear 1.2%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,5005,0007,50010,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Σ 32,645ShareData sentBlockedby the serverWhat this means
Break-in scanners17,94455%26 MB9,483Probing for WordPress logins, password files and other common weak spots.
Scripts and tools4,06012%27 MB104Programs such as curl or Python, or anything with an unrecognizable name.
Scanners posing as browsers2,9659.1%10 MB11Other requests from an address also caught probing for weak spots.
Disguised scrapers2,8118.6%26 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.
Other named bots1,3064.0%11 MB26Any other software that identifies itself as a bot.
AI crawlers1,2313.8%5 MB50AI companies gathering pages or answering a user's question, and saying so.
Search engines1,1053.4%6 MB8Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Unclear3951.2%5 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people3861.2%22 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools2540.8%<1 MB88Commercial tools that sell data about websites.
No name given950.3%<1 MB5Requests that give no software name at all.
Possibly people930.3%<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 engines397
ClaudeBotAI crawlers300
GooglebotSearch engines260
OAI-SearchBotAI crawlers166
bingbotSearch engines142
meta-webindexerOther named bots100
ApplebotSearch engines99
facebook.comOther named bots93
PerplexityBotAI crawlers90
GPTBotAI crawlers83
SemrushBotSEO and marketing tools82
ChatGPT-UserAI crawlers71
SEOJuice-SearchBotOther named bots69
NVBotOther named bots68
Amzn-SearchBotSearch engines64

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/81
/events/12
/outdoors/2
/neighborhoods/2
/videos.html2

How people arrived

Referring siteHuman visitors
www.google.com28
m.baidu.com18
austintweet.com13

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
102.129.0.0/161492
192.42.0.0/1613515
185.220.0.0/16967
148.135.0.0/16801
158.69.0.0/16642
27.115.0.0/16464
128.24.0.0/16411
43.157.0.0/164019

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2369140224602201,00396%
Oct 249111071794671780693%
Oct 2546134211751131,11698%
Oct 261317384172575211,19595%
Oct 271113166247644221,10096%
Oct 281620258204741371,30492%
Oct 298101773133,367103,87999.4%
Oct 307103141974061595396%
Oct 31812444166933191,58397%
Nov 115194191,1261,336623,00996%
Nov 213162112562,326282,86797%
Nov 312171181901,636292,01497%
Nov 4691582981,121171,60598%
Nov 518242693,0704,690658,15998%
Nov 6465971131,314202,05299%

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:43 UTC from 15 log files.