Bot traffic: austintechnews.live

all sites · all domains · last 15 days

All sites · All Domains · Visit austintechnews.live

Who is really visiting austintechnews.live?

Between Oct 23 and Nov 6, austintechnews.live received 55,900 requests. About 99% came from automated software and about 0.5% look like real people.

That works out to about 72 human visitors, roughly 5 a day, who opened 98 pages between them. 26 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.

99%of requests from bots
72human visitors (estimate)
98pages opened by people
55,900total requests, 15 days

Where the requests came from

People 0.5%Named bots 11%Disguised bots 11%Scanners 76%Unclear 0.6%

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.

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

The breakdown

SourceRequestsΣ 55,900ShareData sentBlockedby the serverWhat this means
Break-in scanners35,05363%59 MB21,745Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,63714%27 MB4Other requests from an address also caught probing for weak spots.
Disguised scrapers4,8278.6%34 MB1Claims 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.
Search engines2,2434.0%14 MB13Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,9523.5%10 MB31Any other software that identifies itself as a bot.
Scripts and tools1,4012.5%18 MB13Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers1,3172.4%5 MB81AI companies gathering pages or answering a user's question, and saying so.
SEO and marketing tools7241.3%3 MB110Commercial tools that sell data about websites.
Unclear3360.6%1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2140.4%17 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Automated browsers1480.3%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
Possibly people480.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.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,036
serpstatbotSEO and marketing tools472
ClaudeBotAI crawlers440
Amzn-SearchBotSearch engines416
ExaSearchBotOther named bots325
GooglebotSearch engines269
QlyzeBotOther named bots269
fresh-domain-watchOther named bots249
bingbotSearch engines246
OAI-SearchBotAI crawlers189
BarkrowlerSEO and marketing tools128
SemrushBotSEO and marketing tools105
BacklinksExtendedBotOther named bots95
ibou-searchOther named bots79
GPTBotAI crawlers77

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/49
/news/2026-06-14-el-nino-arrives-austin-texas-summer-weather-impact.html2
/videos/2

How people arrived

Referring siteHuman visitors
m.baidu.com18
www.google.com9
duckduckgo.com2
www.bing.com1
cn.bing.com1
austen.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/1617433
47.82.0.0/16173169
158.69.0.0/161481
93.123.0.0/161081
102.129.0.0/16891
5.102.0.0/16742
45.138.0.0/16613
185.220.0.0/165812

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23235781,223758262,58999%
Oct 2410122372841,731252,32297%
Oct 25002432084,305184,77499.6%
Oct 26685602122,700173,50099.2%
Oct 27355535436,323227,44799.6%
Oct 2811114842643,777424,60798%
Oct 29462723061,733102,32899.3%
Oct 30226523067,282198,26299.7%
Oct 31343712752,035172,70299.2%
Nov 116194951,3712,259474,25097%
Nov 2557062044,160165,10099.4%
Nov 3352183052,369122,91099.4%
Nov 4564883221,213202,05199%
Nov 5462243291,384181,96898%
Nov 646155224661271,09095%

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.