Bot traffic: atxfans.com

all sites · all domains · last 15 days

All sites · All Domains · Visit atxfans.com

Who is really visiting atxfans.com?

Between Oct 23 and Nov 6, atxfans.com received 23,014 requests. About 98% came from automated software and about 0.3% look like real people.

That works out to about 44 human visitors, roughly 3 a day, who opened 63 pages between them. 16 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,481 requests, of which 3 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.

98%of requests from bots
44human visitors (estimate)
63pages opened by people
23,014total requests, 15 days

Where the requests came from

People 0.3%Named bots 24%Disguised bots 21%Scanners 53%Unclear 1.2%

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.

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

The breakdown

SourceRequestsΣ 23,014ShareData sentBlockedby the serverWhat this means
Break-in scanners6,91530%1 MB45Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers5,39723%42 MB21Other requests from an address also caught probing for weak spots.
Disguised scrapers3,66916%123 MB34Claims 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,59511%46 MB3Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,4956.5%28 MB11Any other software that identifies itself as a bot.
AI crawlers1,2405.4%13 MB28AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools1,0864.7%10 MB2Programs such as curl or Python, or anything with an unrecognizable name.
Unclear2711.2%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2291.0%3 MB59Commercial tools that sell data about websites.
Possibly people550.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.
App link sweepers390.2%<1 MB0Touches only login, app or embed links and no actual content.
Likely people220.1%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
No name given10.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,718
OAI-SearchBotAI crawlers435
ClaudeBotAI crawlers402
RiverBotOther named bots260
Amzn-SearchBotSearch engines243
bingbotSearch engines219
GooglebotSearch engines165
ElevenlabsCrawlerOther named bots138
ChatGPT-UserAI crawlers105
WFEditorialResearchOther named bots102
Dataprovider.comOther named bots92
SeznamBotSearch engines86
SERankingBacklinksBotSEO and marketing tools86
ibou-searchOther named bots76
QlyzeBotOther named bots74

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/35
/events/2
/longhorns/football/2
/tickets/texas/dallas-stars/2
/tickets/texas/texas-longhorns/2
/tickets/nba/2

How people arrived

Referring siteHuman visitors
m.baidu.com18
www.google.com15
insurancesolutionforyouesv.blogspot.com4
www.bing.com2
www.ecosia.org1
www.yandex.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/162973
192.42.0.0/1627849
43.157.0.0/1612034
43.166.0.0/168532
43.130.0.0/168237
43.153.0.0/167737
43.134.0.0/166420
170.106.0.0/166329

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2344256432642177797%
Oct 2433315401466211,20698%
Oct 252242424249561,16999.3%
Oct 26334982843,69154,48199.8%
Oct 273336224348981,10599.0%
Oct 28234932081,239201,96499%
Oct 296113031,348300181,99298%
Oct 3012356314807171,49799%
Oct 3122239119927721,35995%
Nov 135485281993121,77699.0%
Nov 20045421444151,11499.6%
Nov 3354051701,366151,96199%
Nov 4692801581771864296%
Nov 557424252768161,46798%
Nov 634265129891750496%

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.