Bot traffic: austinpads.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austinpads.com

Who is really visiting austinpads.com?

Between Oct 23 and Nov 6, austinpads.com received 55,615 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 170 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
124human visitors (estimate)
170pages opened by people
55,615total requests, 15 days

Where the requests came from

People 0.6%Named bots 9.9%Disguised bots 9.1%Scanners 80%Unclear 0.6%

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.

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

The breakdown

SourceRequestsΣ 55,615ShareData sentBlockedby the serverWhat this means
Break-in scanners39,74371%60 MB27,328Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers4,6558.4%17 MB29Other requests from an address also caught probing for weak spots.
Disguised scrapers4,3817.9%33 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.
Other named bots2,1153.8%14 MB33Any other software that identifies itself as a bot.
Search engines2,0273.6%15 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers1,0962.0%5 MB37AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools6571.2%12 MB3Programs such as curl or Python, or anything with an unrecognizable name.
Unclear3330.6%8 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2770.5%17 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools2430.4%<1 MB87Commercial tools that sell data about websites.
Possibly people830.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.
App link sweepers30.0%<1 MB0Touches only login, app or embed links and no actual content.
No name given20.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
QlyzeBotOther named bots771
PetalBotSearch engines752
ClaudeBotAI crawlers467
bingbotSearch engines445
Amzn-SearchBotSearch engines326
ElevenlabsCrawlerOther named bots223
fresh-domain-watchOther named bots201
OAI-SearchBotAI crawlers189
GooglebotSearch engines189
BarkrowlerSEO and marketing tools148
ibou-searchOther named bots93
SemrushBotSEO and marketing tools86
BaiduspiderSearch engines85
SeznamBotSearch engines76
BacklinksExtendedBotOther named bots75

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/89
/news/2026-06-04-police-escorts-austin-what-renters-need-to-know4
/sources/4
/under-1500.html3
/renters-guide/2

How people arrived

Referring siteHuman visitors
m.baidu.com21
www.google.com21
austintweet.com13
austinhangout.com4
www.baidu.com2
duckduckgo.com2
search.yahoo.com2
www.bing.com1
aiaustintexas.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
82.80.0.0/165622
47.82.0.0/16246236
192.42.0.0/1621952
158.69.0.0/161801
102.129.0.0/16881
103.4.0.0/16784
183.207.0.0/16756
47.79.0.0/167269

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23783539783,424184,79799.1%
Oct 249111952824,002194,51899.1%
Oct 25446011722,567213,36899.2%
Oct 269124652291,965182,69699%
Oct 2714175472766,555197,43199.3%
Oct 28442521493,435153,86299.3%
Oct 2910122082343,530103,99699.4%
Oct 30555932425,257276,13099.4%
Oct 318102911512,361102,82699.2%
Nov 126323537602,179433,41596%
Nov 2882221702,96273,38599.1%
Nov 38112101552,577383,02297%
Nov 4922314831975542,21496%
Nov 5683843371,902222,65999%
Nov 63649377707121,29699%

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.