Bot traffic: austinblogger.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austinblogger.com

Who is really visiting austinblogger.com?

Between Oct 23 and Nov 6, austinblogger.com received 101,597 requests. About 99.4% came from automated software and about 0.3% look like real people.

That works out to about 126 human visitors, roughly 8 a day, who opened 200 pages between them. 61 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 29, with 18,169 requests, of which 26 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.4%of requests from bots
126human visitors (estimate)
200pages opened by people
101,597total requests, 15 days

Where the requests came from

People 0.3%Named bots 8.7%Disguised bots 5.7%Scanners 85%Unclear 0.3%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
05,00010,00015,00020,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.

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

The breakdown

SourceRequestsΣ 101,597ShareData sentBlockedby the serverWhat this means
Break-in scanners53,02052%4 MB32,160Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers33,29633%56 MB18Other requests from an address also caught probing for weak spots.
Search engines5,6495.6%33 MB6Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Disguised scrapers3,6893.6%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.
Scripts and tools2,0752.0%7 MB7Programs such as curl or Python, or anything with an unrecognizable name.
Other named bots1,4431.4%6 MB12Any other software that identifies itself as a bot.
AI crawlers1,3841.4%2 MB63AI companies gathering pages or answering a user's question, and saying so.
Unclear3370.3%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2520.2%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Calendar and feed apps2490.2%<1 MB0Software fetching a feed for someone who subscribed.
SEO and marketing tools1370.1%<1 MB99Commercial tools that sell data about websites.
Possibly people610.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.
No name given50.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines3,482
GooglebotSearch engines659
sogou.comSearch engines477
ClaudeBotAI crawlers401
ApplebotSearch engines323
bingbotSearch engines302
BaiduspiderSearch engines208
OAI-SearchBotAI crawlers175
ISPDomainVerifierOther named bots170
GPTBotAI crawlers92
SemrushBotSEO and marketing tools76
DuckAssistBotOther named bots75
symfony-scannerOther named bots68
ChatGLM-SpiderOther named bots66
Perplexity-UserAI crawlers65

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/108
/about/4
/faq/3
/faq.html2
/about.html2

How people arrived

Referring siteHuman visitors
m.baidu.com22
austintweet.com10
www.google.com7
austin-nightlife.latinadanza.com2
www.bing.com2
search.yahoo.com1
scriblihelp.com1
www.austin-nightlife.latinadanza.com1
miniature.io1
google.com, http:1

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/16243118
192.42.0.0/1616146
91.98.0.0/16942
45.141.0.0/16661
192.210.0.0/16611
183.207.0.0/16603
47.79.0.0/165829
102.129.0.0/16561

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23671,1342866,282247,74199.5%
Oct 249135012485,221226,01199.3%
Oct 25111877429110,4031011,50799.7%
Oct 269136674372,971124,10399.3%
Oct 277124585648,130209,18899.6%
Oct 2812155952474,272325,17099%
Oct 29111846742417,2322018,16999.7%
Oct 30454642407,146217,87899.6%
Oct 31575882013,597204,41699.3%
Nov 121409601,0952,831344,98698%
Nov 27124782314,158234,91099.1%
Nov 310163964093,683114,52699.2%
Nov 4355543722,270223,22499.1%
Nov 511134245573,136374,17899%
Nov 6464021674,984295,59099.3%

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.