Bot traffic: manage.austinspring.com

all sites · all domains · last 15 days

All sites · All Domains · Visit manage.austinspring.com

Who is really visiting manage.austinspring.com?

Between Oct 23 and Nov 6, manage.austinspring.com received 3,710 requests. About 99.6% came from automated software and about 0.1% look like real people.

That works out to about 1 human visitors, roughly fewer than 1 a day, who opened 1 pages between them. 0 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,004 requests, of which 0 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.6%of requests from bots
1human visitors (estimate)
1pages opened by people
3,710total requests, 15 days

Where the requests came from

People 0.1%Named bots 9.0%Disguised bots 1.6%Scanners 89%Unclear 0.4%

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.

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

The breakdown

SourceRequestsΣ 3,710ShareData sentBlockedby the serverWhat this means
Break-in scanners3,27588%<1 MB26Probing for WordPress logins, password files and other common weak spots.
AI crawlers1484.0%<1 MB15AI companies gathering pages or answering a user's question, and saying so.
Other named bots1163.1%<1 MB5Any other software that identifies itself as a bot.
Search engines701.9%<1 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Disguised scrapers511.4%<1 MB0Claims 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 browsers240.6%<1 MB3Other requests from an address also caught probing for weak spots.
Unclear140.4%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools90.2%<1 MB0Programs such as curl or Python, or anything with an unrecognizable name.
Likely people20.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
GooglebotSearch engines30
BravebotOther named bots19
Meta-ExternalFetcherAI crawlers16
DuckAssistBotOther named bots15
Claude-SearchBotAI crawlers13
OAI-SearchBotAI crawlers12
Meta-WebIndexerOther named bots12
Kimi-SearchBotOther named bots11
bingbotSearch engines10
ApplebotSearch engines10
OAI-AdsBotSearch engines10
ChatGLM-SpiderOther named bots10
BaiduspiderSearch engines10
DeepSeekBotAI crawlers10
YouBotAI crawlers10

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 230016031070%
Oct 2400640010100.0%
Oct 250016007100.0%
Oct 2600152,99713,004100.0%
Oct 27001701989%
Oct 2800312131984%
Oct 29000201367%
Oct 30004101683%
Oct 31001201490170100.0%
Nov 11165245011498%
Nov 200127844118099.4%
Nov 30011142114599.3%
Nov 400042112696%
Nov 50021003100.0%
Nov 6002101475%

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