Bot traffic: realhotsprings.com

all sites · all domains · last 15 days

All sites · All Domains · Visit realhotsprings.com

Who is really visiting realhotsprings.com?

Between Oct 23 and Nov 6, realhotsprings.com received 21,370 requests. About 95% came from automated software and about 2.3% look like real people.

That works out to about 181 human visitors, roughly 12 a day, who opened 214 pages between them. 33 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 26, with 3,800 requests, of which 66 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.

95%of requests from bots
181human visitors (estimate)
214pages opened by people
21,370total requests, 15 days

Where the requests came from

People 2.3%Named bots 28%Disguised bots 24%Scanners 44%Unclear 2.6%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
01,0002,0003,0004,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Σ 21,370ShareData sentBlockedby the serverWhat this means
Break-in scanners5,83527%6 MB1,330Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers4,60022%95 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.
Scanners posing as browsers3,50516%34 MB38Other requests from an address also caught probing for weak spots.
Other named bots2,29511%49 MB29Any other software that identifies itself as a bot.
Search engines2,0809.7%20 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers1,1335.3%4 MB39AI companies gathering pages or answering a user's question, and saying so.
Unclear5622.6%12 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools4582.1%5 MB2Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools3731.7%2 MB146Commercial tools that sell data about websites.
Likely people3531.7%55 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people1440.7%3 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 sweepers300.1%<1 MB30Touches 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
PetalBotSearch engines949
ClaudeBotAI crawlers720
QlyzeBotOther named bots511
GooglebotSearch engines377
Amzn-SearchBotSearch engines260
ElevenlabsCrawlerOther named bots257
bingbotSearch engines234
meta-webindexerOther named bots180
facebook.comOther named bots172
OAI-SearchBotAI crawlers163
ExaSearchBotOther named bots146
MSIE 8.0Other named bots145
SemrushBotSEO and marketing tools144
serpstatbotSEO and marketing tools142
ReflectionbotOther named bots113

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/153
/relocation.html2
/selling.html2
/search/2

How people arrived

Referring siteHuman visitors
bnbhot.com77
www.google.com31
m.baidu.com19
ehotsprings.com2
www.bing.com1
newbuilds.realhotsprings.com1
ownerfinance.realhotsprings.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/162212
152.53.0.0/161711
5.102.0.0/161673
158.69.0.0/161151
192.42.0.0/1610621
47.82.0.0/168165
87.81.0.0/166763
104.164.0.0/16588

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 233557820427761,07199%
Oct 24282929632868872995%
Oct 2577628203466161,32198%
Oct 2621243731933,134343,80097%
Oct 271922405314356131,12096%
Oct 28151568532764201,12496%
Oct 292022215323528321,12295%
Oct 301820259312705177683%
Oct 31911295247557281,15096%
Nov 114186735071,056362,34795%
Nov 278333422563191,36197%
Nov 3582783881,057741,80695%
Nov 41213444510626951,74191%
Nov 557266499317888490%
Nov 645153313487521,01894%

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.