Bot traffic: atxsportsfans.com

all sites · all domains · last 15 days

All sites · All Domains · Visit atxsportsfans.com

Who is really visiting atxsportsfans.com?

Between Oct 23 and Nov 6, atxsportsfans.com received 16,021 requests. About 99% came from automated software and about 0.5% look like real people.

That works out to about 57 human visitors, roughly 4 a day, who opened 80 pages between them. 23 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 3,787 requests, of which 6 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.

99%of requests from bots
57human visitors (estimate)
80pages opened by people
16,021total requests, 15 days

Where the requests came from

People 0.5%Named bots 27%Disguised bots 19%Scanners 53%Unclear 0.7%

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.

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

The breakdown

SourceRequestsΣ 16,021ShareData sentBlockedby the serverWhat this means
Break-in scanners5,84536%1 MB25Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers2,73017%79 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.
Scanners posing as browsers2,56816%22 MB5Other requests from an address also caught probing for weak spots.
Search engines2,33515%44 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,4188.9%27 MB7Any other software that identifies itself as a bot.
AI crawlers4272.7%2 MB10AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools3202.0%6 MB0Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools1721.1%1 MB70Commercial tools that sell data about websites.
Unclear1190.7%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people790.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.
Likely people40.0%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
No name given20.0%<1 MB0Requests that give no software name at all.
App link sweepers20.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,635
RiverBotOther named bots259
Amzn-SearchBotSearch engines248
QlyzeBotOther named bots156
bingbotSearch engines155
WFEditorialResearchOther named bots153
ElevenlabsCrawlerOther named bots136
GooglebotSearch engines109
OAI-SearchBotAI crawlers106
SEOJuice-SearchBotOther named bots97
ClaudeBotAI crawlers92
SERankingBacklinksBotSEO and marketing tools80
meta-webindexerOther named bots71
ibou-searchOther named bots70
SeznamBotSearch engines69

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/29
/tickets/nba/2
/tickets/texas/texas-longhorns/2

How people arrived

Referring siteHuman visitors
www.google.com36
m.baidu.com19

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/1627243
43.157.0.0/1610034
43.130.0.0/169336
49.51.0.0/167527
43.165.0.0/167419
43.153.0.0/167031
170.106.0.0/166935
43.164.0.0/166515

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2357172278283574698%
Oct 2458239188188763098%
Oct 2512378256297994299%
Oct 26563142513,21153,78799.7%
Oct 2746339298286893799%
Oct 284639614917957797%
Oct 293427123589281,41099.1%
Oct 3058373195532101,11998%
Oct 3134165136198550898%
Nov 1910346211821131,40298%
Nov 235396250213787199%
Nov 334208149309367399%
Nov 433254157784141,21299%
Nov 546327180841160897%
Nov 611174121298559999%

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.