Bot traffic: austinspring.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austinspring.com

Who is really visiting austinspring.com?

Between Oct 23 and Nov 6, austinspring.com received 208,704 requests. About 96% came from automated software and about 0.9% look like real people.

That works out to about 583 human visitors, roughly 39 a day, who opened 969 pages between them. 111 of them read more than one page.

The biggest source is bots that say who they are. Most of those are normal and some, like search engines, help people find the site.

The busiest day was Nov 5, with 49,196 requests, of which 139 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
583human visitors (estimate)
969pages opened by people
208,704total requests, 15 days

Where the requests came from

People 0.9%Named bots 63%Disguised bots 19%Scanners 14%Unclear 3.2%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
012,50025,00037,50050,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.

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

The breakdown

SourceRequestsΣ 208,704ShareData sentBlockedby the serverWhat this means
Other named bots42,43120%662 MB142Any other software that identifies itself as a bot.
AI crawlers38,58818%424 MB183AI companies gathering pages or answering a user's question, and saying so.
Disguised scrapers33,79816%487 MB670Claims 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 engines31,77615%402 MB114Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
SEO and marketing tools19,1689.2%407 MB2,541Commercial tools that sell data about websites.
Break-in scanners18,3508.8%3 MB88Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers10,1644.9%27 MB9Other requests from an address also caught probing for weak spots.
Unclear6,6433.2%57 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools5,6722.7%19 MB3Programs such as curl or Python, or anything with an unrecognizable name.
Likely people1,6750.8%14 MB129Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Automated browsers3270.2%1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
Possibly people1040.0%1 MB19Read 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 given80.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
QlyzeBotOther named bots25,337
GPTBotAI crawlers24,254
ClaudeBotAI crawlers12,203
PetalBotSearch engines11,209
ApplebotSearch engines8,461
ElevenlabsCrawlerOther named bots7,035
serpstatbotSEO and marketing tools6,786
BarkrowlerSEO and marketing tools4,996
SERankingBacklinksBotSEO and marketing tools4,422
Amzn-SearchBotSearch engines4,066
ExaSearchBotOther named bots3,629
GooglebotSearch engines3,502
bingbotSearch engines2,450
SemrushBotSEO and marketing tools2,118
br-crawlerOther named bots1,478

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/bbs/live/api/site/comments155
/136
/bbs/tv/69/22
/bbs/live/13
/bbs/help/password.html10
/bbs/live/signup8
/bbs/live/api/members8
/bbs/bronte/26/7
/bbs/atxbbs/7
/bbs/live/rt/stream7
/bbs/drool/134/6
/bbs/movies/5

How people arrived

Referring siteHuman visitors
globalfilmfests.com157
www.google.com70
m.baidu.com21
cardsadpartlim.blogspot.com8
altonsennalims.blogspot.com3
austinhangout.com3
aocscannerlims.blogspot.com2
jane.austen.com1
www.google.com.hk1
m.facebook.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
47.82.0.0/162,4971,538
47.79.0.0/161,720671
43.173.0.0/161,272712
43.172.0.0/16655370
44.248.0.0/164921
32.191.0.0/164891
192.42.0.0/1643866
161.120.0.0/16258172

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23484912,1341,77651530914,85297%
Oct 2439554,3271,7845703927,17493%
Oct 2539503,5271,9442,9095599,03193%
Oct 26511646,7051,7744,73722713,70796%
Oct 2731512,5371,5251,8041596,11696%
Oct 2826287,1421,1501,74333110,42196%
Oct 2940656,6541,9453621969,27497%
Oct 3057834,1991,7933,90522410,28496%
Oct 3139437,4001,6431,56123310,92497%
Nov 1365028,0611,9321,65715431,91399.2%
Nov 250833,7048551,8701426,73695%
Nov 327302,9851,8761,9703487,22994%
Nov 468883,1595,4052,08192611,73891%
Nov 5578133,34212,3971,9841,33449,19697%
Nov 622496,0872,0068461,10910,10988%

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:44 UTC from 15 log files.