Bot traffic: austintechtrends.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austintechtrends.com

Who is really visiting austintechtrends.com?

Between Oct 23 and Nov 6, austintechtrends.com received 13,890 requests. About 96% came from automated software and about 2.3% look like real people.

That works out to about 114 human visitors, roughly 8 a day, who opened 130 pages between them. 15 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 Oct 26, with 4,178 requests, of which 30 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.

96%of requests from bots
114human visitors (estimate)
130pages opened by people
13,890total requests, 15 days

Where the requests came from

People 2.3%Named bots 21%Disguised bots 17%Scanners 58%Unclear 1.9%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,2502,5003,7505,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Σ 13,890ShareData sentBlockedby the serverWhat this means
Break-in scanners5,50840%1 MB27Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers2,54218%4 MB5Other requests from an address also caught probing for weak spots.
Disguised scrapers2,19616%12 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 bots1,1308.1%8 MB10Any other software that identifies itself as a bot.
Search engines9436.8%4 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers6514.7%<1 MB18AI companies gathering pages or answering a user's question, and saying so.
Likely people2722.0%11 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear2691.9%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1891.4%<1 MB86Commercial tools that sell data about websites.
Scripts and tools1351.0%<1 MB0Programs such as curl or Python, or anything with an unrecognizable name.
Possibly people520.4%<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.
App link sweepers20.0%<1 MB0Touches only login, app or embed links and no actual content.
No name given10.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines352
ClaudeBotAI crawlers248
GooglebotSearch engines171
SecurityResearchOther named bots132
OAI-SearchBotAI crawlers120
sogou.comSearch engines95
QlyzeBotOther named bots94
ibou-searchOther named bots84
bingbotSearch engines81
Amzn-SearchBotSearch engines70
SemrushBotSEO and marketing tools70
ExaSearchBotOther named bots69
CensysInspectOther named bots62
BarkrowlerSEO and marketing tools59
ElevenlabsCrawlerOther named bots54

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/77
/news/5
/austin/3
/resources/3
/faq/2
/methodology/2
/about/2
/capital-factory/2
/global/2
/news.html2
/austin-business-journal/2
/bastrop-corridor/2

How people arrived

Referring siteHuman visitors
memsist.com18
m.baidu.com17
www.google.com13
www.bing.com1
duckduckgo.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
93.123.0.0/161551
192.42.0.0/1612431
23.180.0.0/16981
45.138.0.0/16623
5.102.0.0/16533
185.220.0.0/16409
43.157.0.0/163924
148.135.0.0/16361

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23710782441281248293%
Oct 2466131120432970098%
Oct 252212610753929896%
Oct 2610105132273,40264,17899.1%
Oct 271212164289615161,09697%
Oct 281216242143769171,20296%
Oct 2978186216286570498%
Oct 3018213751253195895086%
Oct 3133157864171167797%
Nov 188167136399873196%
Nov 2331331071661542895%
Nov 378115156552885496%
Nov 410101921371596059582%
Nov 533188145801543994%
Nov 6810146962732055693%

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.