Bot traffic: austincoffeeshowdown.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austincoffeeshowdown.com

Who is really visiting austincoffeeshowdown.com?

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

That works out to about 88 human visitors, roughly 6 a day, who opened 123 pages between them. 33 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
88human visitors (estimate)
123pages opened by people
58,543total requests, 15 days

Where the requests came from

People 0.5%Named bots 8.3%Disguised bots 7.1%Scanners 84%Unclear 0.5%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,0004,0006,0008,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.

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

The breakdown

SourceRequestsΣ 58,543ShareData sentBlockedby the serverWhat this means
Break-in scanners43,37574%68 MB27,530Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers5,5419.5%18 MB38Other requests from an address also caught probing for weak spots.
Disguised scrapers2,8604.9%20 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 engines1,9003.2%11 MB9Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,4112.4%6 MB28Any other software that identifies itself as a bot.
Scripts and tools1,2952.2%9 MB6Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers1,2442.1%2 MB73AI companies gathering pages or answering a user's question, and saying so.
Unclear3160.5%4 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2850.5%<1 MB113Commercial tools that sell data about websites.
Likely people2580.4%14 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people550.1%<1 MB1Read 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 sweepers30.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines897
ClaudeBotAI crawlers401
ApplebotSearch engines229
Amzn-SearchBotSearch engines227
GooglebotSearch engines226
QlyzeBotOther named bots182
ElevenlabsCrawlerOther named bots140
OAI-SearchBotAI crawlers128
SERankingBacklinksBotSEO and marketing tools122
SemrushBotSEO and marketing tools105
pathscanOther named bots99
bingbotSearch engines97
GPTBotAI crawlers92
ibou-searchOther named bots81
SeznamBotSearch engines70

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/59
/news/4
/live/3
/sources/3
/videos/3
/faq/2

How people arrived

Referring siteHuman visitors
m.baidu.com18
www.google.com9
01beees.blogspot.com2
austintweet.com2
austinhangout.com2

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/1627141
158.69.0.0/161231
93.123.0.0/161001
45.138.0.0/16713
148.135.0.0/16632
5.102.0.0/16603
102.129.0.0/16531
47.82.0.0/165048

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23456742473,912194,86199.4%
Oct 247121432433,536203,96599%
Oct 25222691942,891183,37499.4%
Oct 26685984862,255143,37299.0%
Oct 27692493545,762176,40999.3%
Oct 28443951404,053154,61899.4%
Oct 29453891705,350125,92999.7%
Oct 3011115711896,475457,32099%
Oct 31351481782,602182,95199.2%
Nov 18111951,0312,095153,36799%
Nov 2331851823,233113,61999.5%
Nov 38122491532,627193,07299%
Nov 414203422451,586522,28995%
Nov 5672992351,850222,42498%
Nov 6791341116891997396%

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.