Bot traffic: austintexasfans.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austintexasfans.com

Who is really visiting austintexasfans.com?

Between Oct 23 and Nov 6, austintexasfans.com received 62,993 requests. About 99% came from automated software and about 0.8% look like real people.

That works out to about 168 human visitors, roughly 11 a day, who opened 219 pages between them. 50 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
168human visitors (estimate)
219pages opened by people
62,993total requests, 15 days

Where the requests came from

People 0.8%Named bots 11%Disguised bots 10%Scanners 78%Unclear 0.5%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
03,1256,2509,37512,500Oct 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Σ 62,993ShareData sentBlockedby the serverWhat this means
Break-in scanners44,54071%68 MB28,245Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers4,3807.0%48 MB2Claims 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.
Scanners posing as browsers4,2846.8%18 MB14Other requests from an address also caught probing for weak spots.
Search engines3,0054.8%23 MB5Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots2,3623.7%21 MB22Any other software that identifies itself as a bot.
Scripts and tools1,9733.1%17 MB13Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers1,0181.6%6 MB28AI companies gathering pages or answering a user's question, and saying so.
SEO and marketing tools6031.0%3 MB97Commercial tools that sell data about websites.
Likely people3880.6%16 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear3300.5%2 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people1090.2%<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 given10.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,828
QlyzeBotOther named bots543
bingbotSearch engines410
ClaudeBotAI crawlers341
RiverBotOther named bots316
PerplexityBotAI crawlers284
ElevenlabsCrawlerOther named bots250
DataForSeoBotSEO and marketing tools221
SeznamBotSearch engines202
SERankingBacklinksBotSEO and marketing tools183
Amzn-SearchBotSearch engines158
OAI-SearchBotAI crawlers157
GooglebotSearch engines141
ExaSearchBotOther named bots134
ibou-searchOther named bots121

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/72
/stadiums/dkr-texas-memorial-stadium/15
/videos.html12
/gameday/parking/6
/gameday/4
/events/4
/faq/4
/gameday/tailgating/3
/videos/3
/tickets/3
/tickets/texas/texas-longhorns/2
/tickets/mls/2

How people arrived

Referring siteHuman visitors
www.google.com28
m.baidu.com20
duckduckgo.com12
www.bing.com4
search.yahoo.com4
austintweet.com3
austinhangout.com3
www.baidu.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
158.69.0.0/162902
192.42.0.0/1622840
66.249.0.0/161653
102.129.0.0/161641
103.4.0.0/161609
104.164.0.0/16958
43.157.0.0/168629
171.22.0.0/16862

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 239104004884,044164,96799.3%
Oct 2424293714003,638224,51398%
Oct 25667443553,328184,45499.4%
Oct 2610142373041,09081,66998%
Oct 2713166036695,578136,89199.4%
Oct 289103453354,029474,78998%
Oct 2912173692451,621202,27798%
Oct 3012145552629,2811910,14399.6%
Oct 3115202852452,77393,33799%
Nov 117236731,7672,292464,85198%
Nov 2775001813,14673,84599.5%
Nov 3576052693,446164,34799.4%
Nov 417193993131,439602,27994%
Nov 59116753372,269143,32399%
Nov 61316227184850151,30896%

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.