Bot traffic: firth.com

all sites · all domains · last 15 days

All sites · All Domains · Visit firth.com

Who is really visiting firth.com?

Between Oct 23 and Nov 6, firth.com received 152,097 requests. About 89% came from automated software and about 3.7% look like real people.

That works out to about 1,332 human visitors, roughly 89 a day, who opened 1,701 pages between them. 214 of them read more than one page.

The biggest source is bots that say who they are. Most of those are normal and some, like search engines, help people find the site.

89%of requests from bots
1,332human visitors (estimate)
1,701pages opened by people
152,097total requests, 15 days

Where the requests came from

People 3.7%Named bots 38%Disguised bots 19%Scanners 32%Unclear 7.2%

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.

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

The breakdown

SourceRequestsΣ 152,097ShareData sentBlockedby the serverWhat this means
Break-in scanners33,61822%3 MB19,558Probing for WordPress logins, password files and other common weak spots.
Other named bots32,39321%390 MB101Any other software that identifies itself as a bot.
Disguised scrapers21,54414%238 MB18Claims 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 engines18,13812%140 MB28Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scanners posing as browsers15,24710%23 MB36Other requests from an address also caught probing for weak spots.
Unclear11,0037.2%50 MB0Browser name, but fetched only an image or data file and no page. Could be either.
AI crawlers4,9873.3%26 MB227AI companies gathering pages or answering a user's question, and saying so.
Likely people4,9253.2%52 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
No name given4,1282.7%<1 MB0Requests that give no software name at all.
Scripts and tools3,0962.0%35 MB2Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools2,2901.5%12 MB709Commercial tools that sell data about websites.
Possibly people7070.5%10 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 browsers120.0%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
Calendar and feed apps80.0%<1 MB0Software fetching a feed for someone who subscribed.
App link sweepers10.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines5,299
facebook.comOther named bots4,864
tphotobotOther named bots3,665
sogou.comSearch engines2,661
meta-webindexerOther named bots2,391
Googlebot-ImageSearch engines1,953
ExaSearchBotOther named bots1,934
crawlerOther named bots1,362
ClaudeBotAI crawlers1,343
Baiduspider-renderSearch engines1,322
GooglebotSearch engines1,299
ReadBotOther named bots1,290
bingbotSearch engines1,246
ibou-searchOther named bots1,152
QlyzeBotOther named bots1,074

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/624
/upcoming.html188
/films.html87
/news/46
/bio.html23
/news.html22
/chronology/20
/love.html20
/theater.html17
/lastleg.html15
/news/2026-06-08-colin-firth-new-girlfriend-red-carpet-2024.html15
/austen/14

How people arrived

Referring siteHuman visitors
www.google.com501
bolhas-bloguistas.blogspot.com120
hatfieldpa.blogspot.com80
graciasporlamusica-mammamiamovie2.blogspot.com69
duckduckgo.com45
www.bing.com42
maureen-ratherbe.blogspot.com33
m.baidu.com25
retorno-a-manderley.blogspot.com22
search.yahoo.com9

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
5.181.0.0/1699920
66.249.0.0/169715
128.140.0.0/166821
64.16.0.0/1634057
67.217.0.0/162941
216.213.0.0/162881
69.10.0.0/162651
144.126.0.0/162436

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 231972253,0891,3023,9614099,28990%
Oct 242493073,2391,0803,0094048,36088%
Oct 251001174,2101,8955,60535612,44794%
Oct 26911144,8491,6895,71737513,12993%
Oct 2763733,9441,7182,8154169,16393%
Oct 2880973,6791,3751,6528637,98584%
Oct 2964864,3671,8761,4598338,88387%
Oct 30781022,8212,7441,5741,0438,63683%
Oct 31821004,0052,5607,7951,01215,72091%
Nov 1831174,3481,3092,0641,4039,56581%
Nov 252674,9041,5062,3006759,61891%
Nov 370903,7481,7021,9625058,22090%
Nov 462713,3391,9111,7576657,93188%
Nov 559785,4175,4835,8511,60618,65590%
Nov 643571,8576311,3444384,49685%

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