Bot traffic: austincast.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austincast.com

Who is really visiting austincast.com?

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

That works out to about 259 human visitors, roughly 17 a day, who opened 313 pages between them. 36 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
259human visitors (estimate)
313pages opened by people
74,678total requests, 15 days

Where the requests came from

People 0.8%Named bots 12%Disguised bots 8.0%Scanners 79%Unclear 0.5%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,5005,0007,50010,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Σ 74,678ShareData sentBlockedby the serverWhat this means
Break-in scanners40,82855%4 MB22,153Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers18,17424%50 MB26Other requests from an address also caught probing for weak spots.
Disguised scrapers3,1814.3%18 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.
Search engines2,3573.2%8 MB7Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers2,3503.1%3 MB89AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools2,0662.8%5 MB2Programs such as curl or Python, or anything with an unrecognizable name.
Other named bots1,9722.6%7 MB23Any other software that identifies itself as a bot.
Calendar and feed apps1,6402.2%<1 MB0Software fetching a feed for someone who subscribed.
No name given7261.0%3 MB4Requests that give no software name at all.
Likely people5550.7%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools4330.6%<1 MB132Commercial tools that sell data about websites.
Unclear3420.5%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people410.1%<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.
Automated browsers120.0%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
App link sweepers10.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines678
GooglebotSearch engines641
ClaudeBotAI crawlers473
ApplebotSearch engines267
BaiduspiderSearch engines224
OAI-SearchBotAI crawlers199
serpstatbotSEO and marketing tools192
bingbotSearch engines166
ISPDomainVerifierOther named bots161
YouBotAI crawlers149
GPTBotAI crawlers145
Claude-SearchBotAI crawlers129
OAI-AdsBotSearch engines124
cohere-aiAI crawlers121
Meta-ExternalFetcherAI crawlers119

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/240
/live/2

How people arrived

Referring siteHuman visitors
google.com, http:67
m.baidu.com19
touchofthephoenix.blogspot.com9
www.google.com2
www.baidu.com1
search.brave.com1
www.ringaraja.net1

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/16442211
192.42.0.0/1613342
47.79.0.0/1611255
66.249.0.0/168715
31.76.0.0/16742
86.109.0.0/16671
43.166.0.0/166634
102.129.0.0/16601

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 238299871334,542235,74499%
Oct 24683581622,526143,07299.2%
Oct 25441,1833358,361149,90199.8%
Oct 2661635723465,013306,08497%
Oct 2710123084316,762217,54299.5%
Oct 28783281402,020152,52099%
Oct 2915183425344,325205,25399.0%
Oct 3011126381677,189338,05399.3%
Oct 31682921661,388191,87898%
Nov 111141,3771,9513,279186,64999.4%
Nov 2664942173,144143,88099.4%
Nov 314173542682,644373,33198%
Nov 422284574751,036212,04396%
Nov 543457785304,646276,07098%
Nov 640412841312,127362,65896%

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.