Bot traffic: austinretire.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austinretire.com

Who is really visiting austinretire.com?

Between Oct 23 and Nov 6, austinretire.com received 64,327 requests. About 99% came from automated software and about 0.6% look like real people.

That works out to about 124 human visitors, roughly 8 a day, who opened 155 pages between them. 31 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
124human visitors (estimate)
155pages opened by people
64,327total requests, 15 days

Where the requests came from

People 0.6%Named bots 6.2%Disguised bots 6.6%Scanners 86%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.

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

The breakdown

SourceRequestsΣ 64,327ShareData sentBlockedby the serverWhat this means
Break-in scanners46,01172%69 MB27,529Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers9,37815%31 MB35Other requests from an address also caught probing for weak spots.
Disguised scrapers3,0234.7%20 MB1Claims 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.
Other named bots1,3922.2%8 MB30Any other software that identifies itself as a bot.
Search engines1,2892.0%8 MB10Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools1,1991.9%7 MB7Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers1,1011.7%2 MB90AI companies gathering pages or answering a user's question, and saying so.
Likely people3460.5%18 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear3110.5%5 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2180.3%<1 MB90Commercial tools that sell data about websites.
Possibly people590.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.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines501
GooglebotSearch engines282
QlyzeBotOther named bots150
ClaudeBotAI crawlers143
OAI-SearchBotAI crawlers134
Amzn-SearchBotSearch engines118
ElevenlabsCrawlerOther named bots101
pathscanOther named bots98
serpstatbotSEO and marketing tools93
GPTBotAI crawlers91
BaiduspiderSearch engines88
BytespiderAI crawlers83
SemrushBotSEO and marketing tools82
GrokBotAI crawlers76
bingbotSearch engines74

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/104
/social.html2
/social/2
/sources/2

How people arrived

Referring siteHuman visitors
m.baidu.com19
austintweet.com7
www.google.com6
austinhangout.com4
www.bing.com2
www.facebook.com1
duckduckgo.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
192.42.0.0/1625347
103.4.0.0/161138
158.69.0.0/161071
104.164.0.0/16979
102.129.0.0/16911
171.22.0.0/16752
5.102.0.0/16723
45.138.0.0/16722

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23671131813,496283,83799%
Oct 24461173333,83874,30199.7%
Oct 2511123451705,375115,92699.4%
Oct 2614181032245,52765,89799.3%
Oct 27694022713,164123,86699.2%
Oct 2810102671163,951464,44098%
Oct 298101282262,625153,00799.1%
Oct 30771311698,320348,68799.2%
Oct 31683421892,648173,20899.1%
Nov 131397451,4753,467315,81598%
Nov 2442711863,650114,13199.4%
Nov 38101371833,455453,86498%
Nov 4673511651,873162,41699%
Nov 5232142271,750122,21399.0%
Nov 6353341072,250202,71999%

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.