Bot traffic: touroftexas.com

all sites · all domains · last 15 days

All sites · All Domains · Visit touroftexas.com

Who is really visiting touroftexas.com?

Between Oct 23 and Nov 6, touroftexas.com received 49,944 requests. About 98% came from automated software and about 1.0% look like real people.

That works out to about 138 human visitors, roughly 9 a day, who opened 198 pages between them. 50 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.

98%of requests from bots
138human visitors (estimate)
198pages opened by people
49,944total requests, 15 days

Where the requests came from

People 1.0%Named bots 12%Disguised bots 9.5%Scanners 77%Unclear 1.1%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,5003,0004,5006,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Σ 49,944ShareData sentBlockedby the serverWhat this means
Break-in scanners33,91568%29 MB20,222Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers4,4678.9%16 MB6Other requests from an address also caught probing for weak spots.
Disguised scrapers4,3128.6%30 MB12Claims 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,5913.2%9 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Calendar and feed apps1,4312.9%<1 MB0Software fetching a feed for someone who subscribed.
Other named bots1,2322.5%7 MB12Any other software that identifies itself as a bot.
AI crawlers1,1422.3%2 MB50AI companies gathering pages or answering a user's question, and saying so.
Unclear5601.1%6 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools4220.8%7 MB3Programs such as curl or Python, or anything with an unrecognizable name.
Likely people4060.8%34 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools3640.7%<1 MB189Commercial tools that sell data about websites.
Possibly people890.2%<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.
Automated browsers110.0%1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
No name given20.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
ClaudeBotAI crawlers503
PetalBotSearch engines453
sogou.comSearch engines329
GooglebotSearch engines279
OAI-SearchBotAI crawlers199
ReflectionbotOther named bots182
ApplebotSearch engines169
bingbotSearch engines150
SemrushBot-BASEO and marketing tools126
ibou-searchOther named bots78
GPTBotAI crawlers77
SemrushBotSEO and marketing tools73
QlyzeBotOther named bots73
SeznamBotSearch engines69
Amzn-SearchBotSearch engines64

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/94
/hill-country/10
/news/4
/best-bbq/4
/about/4
/rss-api3
/about.html2
/faq/2
/act/2
/news.html2

How people arrived

Referring siteHuman visitors
www.google.com27
m.baidu.com19
austintweet.com7
duckduckgo.com5
www.bing.com3
search.yahoo.com1
www.baidu.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
102.129.0.0/161351
192.42.0.0/1612221
103.4.0.0/16859
152.228.0.0/16822
5.102.0.0/16763
158.69.0.0/16742
196.119.0.0/16631
45.144.0.0/16612

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23695322494,669305,49499.2%
Oct 2413173013822,759553,53197%
Oct 25563953084,011164,74099.5%
Oct 2616192923204,747305,45098%
Oct 271114336324610291,32996%
Oct 28674303592,966693,83998%
Oct 29912337412400291,19396%
Oct 3014173173651,909612,71795%
Oct 319123272981,139191,79998%
Nov 115227625761,313412,75396%
Nov 2783222453,338243,95899%
Nov 39173392852,085282,78797%
Nov 416233612564,375705,12897%
Nov 5562922132,864223,40899%
Nov 6594171551,197371,81897%

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.