Bot traffic: austen.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austen.com

Who is really visiting austen.com?

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

That works out to about 1,235 human visitors, roughly 82 a day, who opened 1,573 pages between them. 261 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.

95%of requests from bots
1,235human visitors (estimate)
1,573pages opened by people
132,562total requests, 15 days

Where the requests came from

People 2.3%Named bots 21%Disguised bots 12%Scanners 62%Unclear 2.7%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
05,00010,00015,00020,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.

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

The breakdown

SourceRequestsΣ 132,562ShareData sentBlockedby the serverWhat this means
Break-in scanners65,05749%100 MB36,062Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers16,80913%73 MB69Other requests from an address also caught probing for weak spots.
Disguised scrapers13,28710%106 MB2Claims 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 engines12,3619.3%64 MB15Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots9,8017.4%56 MB60Any other software that identifies itself as a bot.
AI crawlers4,0173.0%22 MB178AI companies gathering pages or answering a user's question, and saying so.
Unclear3,5582.7%14 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools2,6152.0%24 MB3Programs such as curl or Python, or anything with an unrecognizable name.
Likely people2,5481.9%14 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools1,9341.5%8 MB482Commercial tools that sell data about websites.
Possibly people5370.4%5 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 given260.0%<1 MB0Requests that give no software name at all.
Calendar and feed apps90.0%<1 MB0Software fetching a feed for someone who subscribed.
Automated browsers20.0%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
App link sweepers10.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
sogou.comSearch engines2,828
PetalBotSearch engines2,166
Amzn-SearchBotSearch engines1,945
bingbotSearch engines1,759
BaiduspiderSearch engines1,326
ClaudeBotAI crawlers1,061
QlyzeBotOther named bots821
ChatGPT-UserAI crawlers765
ExaSearchBotOther named bots722
RiverBotOther named bots689
GooglebotSearch engines679
meta-webindexerOther named bots599
OAI-SearchBotAI crawlers598
ibou-searchOther named bots533
Baiduspider-renderSearch engines519

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/399
/persuade/72
/pride/72
/jane-austen/60
/adaptations/58
/sanditon/53
/novels.htm32
/sense/15
/emma/14
/sanditon/01.html14
/about/11
/pride/vol2ch12.htm10

How people arrived

Referring siteHuman visitors
www.google.com130
mind-muffins.blogspot.com90
duckduckgo.com64
italian-scot.blogspot.com54
heather-homeandfamily.blogspot.com50
www.bing.com50
mimisbooks.blogspot.com49
rullsenbergrules.blogspot.com45
m.baidu.com24
thescritchynib.blogspot.com19

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
148.135.0.0/167033
45.66.0.0/1641811
192.42.0.0/1630359
43.173.0.0/16177156
104.28.0.0/1616172
216.213.0.0/161561
70.53.0.0/161391
45.135.0.0/1613611

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 233083231,7961,1515,8281819,36294%
Oct 242062371,8021,0736,4921169,93694%
Oct 251391562,0161,0346,2931689,83995%
Oct 2659741,9051,0626,2122099,54796%
Oct 27671181,8611,7997,63543611,94095%
Oct 2852642,1539025,2221858,59696%
Oct 2975941,4551,11312,63721915,66597%
Oct 3051701,7021,2496,60829810,03695%
Oct 3149702,0881,1393,2823106,99193%
Nov 146642,3437756,45831110,04595%
Nov 254772,1188203,0142916,42693%
Nov 342621,8939744,0162457,25195%
Nov 451671,7059092,3482285,31493%
Nov 543652,0271,1923,9111967,46895%
Nov 623321,2587391,9101654,14694%

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.