Bot traffic: wholetexas.com

all sites · all domains · last 15 days

All sites · All Domains · Visit wholetexas.com

Who is really visiting wholetexas.com?

Between Oct 23 and Nov 6, wholetexas.com received 24,890 requests. About 98% came from automated software and about 1.5% look like real people.

That works out to about 115 human visitors, roughly 8 a day, who opened 208 pages between them. 38 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 Nov 4, with 4,522 requests, of which 12 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.

98%of requests from bots
115human visitors (estimate)
208pages opened by people
24,890total requests, 15 days

Where the requests came from

People 1.5%Named bots 8.5%Disguised bots 12%Scanners 77%Unclear 1.0%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,2502,5003,7505,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Σ 24,890ShareData sentBlockedby the serverWhat this means
Break-in scanners16,62367%20 MB10,603Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers2,4389.8%10 MB27Other requests from an address also caught probing for weak spots.
Disguised scrapers2,0318.2%12 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.
Scripts and tools1,0734.3%2 MB11Programs such as curl or Python, or anything with an unrecognizable name.
Search engines7433.0%3 MB1Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots7383.0%3 MB10Any other software that identifies itself as a bot.
AI crawlers5012.0%<1 MB33AI companies gathering pages or answering a user's question, and saying so.
Likely people2921.2%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Unclear2381.0%2 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1320.5%<1 MB75Commercial tools that sell data about websites.
Possibly people770.3%<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 given40.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
ClaudeBotAI crawlers277
PetalBotSearch engines211
GooglebotSearch engines167
bingbotSearch engines160
OAI-SearchBotAI crawlers85
SemrushBotSEO and marketing tools68
DuckDuckBotSearch engines63
QlyzeBotOther named bots61
meta-webindexerOther named bots53
Amzn-SearchBotSearch engines50
leakix.netOther named bots48
SeznamBotSearch engines47
ibou-searchOther named bots46
GPTBotAI crawlers45
ElevenlabsCrawlerOther named bots40

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/82
/about/9
/videos/7
/best-places-to-visit/7
/news/5
/rss-api5
/faq/5
/resources/4
/sources/3
/expanse/3
/news/2026-dark-texas-charles-petrie/2
/history/2

How people arrived

Referring siteHuman visitors
m.baidu.com20
austintweet.com15
www.google.com15
duckduckgo.com1
touroftexas.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
66.249.0.0/16796
192.42.0.0/167216
148.135.0.0/16671
5.102.0.0/16542
183.207.0.0/16482
43.157.0.0/164118
102.129.0.0/16401
173.46.0.0/16382

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 231622162119855231,20894%
Oct 248111001711,131181,43298%
Oct 25351401281,41181,70099%
Oct 26915192186676111,08997%
Oct 278122091871,344131,76898%
Oct 28441401393031660397%
Oct 2914191052671,131151,55597%
Oct 301216135129911241,23495%
Oct 31577915580891,05998%
Nov 19392219441,448212,69397%
Nov 2491291321,82882,11299%
Nov 38111331572,00892,32499%
Nov 4561711624,155224,52299.2%
Nov 51527154133868301,24193%
Nov 64544991841135093%

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:42 UTC from 15 log files.