Bot traffic: colinfirth.com

all sites · all domains · last 15 days

All sites · All Domains · Visit colinfirth.com

Who is really visiting colinfirth.com?

Between Oct 23 and Nov 6, colinfirth.com received 43,976 requests. About 99% came from automated software and about 0.7% look like real people.

That works out to about 154 human visitors, roughly 10 a day, who opened 245 pages between them. 35 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.

99%of requests from bots
154human visitors (estimate)
245pages opened by people
43,976total requests, 15 days

Where the requests came from

People 0.7%Named bots 8.9%Disguised bots 9.2%Scanners 81%Unclear 0.6%

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.

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

The breakdown

SourceRequestsΣ 43,976ShareData sentBlockedby the serverWhat this means
Break-in scanners26,65661%34 MB17,474Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers8,79920%43 MB55Other requests from an address also caught probing for weak spots.
Disguised scrapers2,9436.7%22 MB6Claims 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.
Other named bots1,2522.8%6 MB33Any other software that identifies itself as a bot.
Search engines1,2202.8%5 MB7Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers1,1782.7%2 MB110AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools1,0742.4%2 MB8Programs such as curl or Python, or anything with an unrecognizable name.
Unclear2790.6%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2490.6%<1 MB91Commercial tools that sell data about websites.
Likely people1870.4%1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people1260.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 given120.0%<1 MB0Requests that give no software name at all.
App link sweepers10.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines339
GooglebotSearch engines311
OAI-SearchBotAI crawlers198
ClaudeBotAI crawlers196
bingbotSearch engines178
BytespiderAI crawlers118
ReadBotOther named bots97
GPTBotAI crawlers94
pathscanOther named bots93
ApplebotSearch engines81
ChatGPT-UserAI crawlers78
SemrushBotSEO and marketing tools76
sogou.comSearch engines68
ibou-searchOther named bots67
BarkrowlerSEO and marketing tools66

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/138
/history/6
/rss-api6
/news/5
/social.html5
/resources/4
/social/4
/faq/3
/news.html3
/faq.html2
/spring.html2

How people arrived

Referring siteHuman visitors
minnospiggy.blogspot.com83
m.baidu.com19
www.google.com4
firth.com1
www.reddit.com1
com.google.android.googlequicksearchbox1
www.wholetech.com1
duckduckgo.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
183.207.0.0/161495
102.129.0.0/161234
66.249.0.0/16953
207.241.0.0/16722
192.42.0.0/166329
104.164.0.0/16573
45.156.0.0/165241
167.235.0.0/16441

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2312272342123,288193,78799%
Oct 2419211422251,201101,60098%
Oct 2561613951844,926205,58899%
Oct 2613311382371,857122,28698%
Oct 27462723744,124194,79699.5%
Oct 28332381951,474281,93998%
Oct 291229115314602141,08295%
Oct 309102621691,502341,98597%
Oct 31242081755,108135,50899.7%
Nov 17224091,2122,398164,07199%
Nov 2335151932,762193,49499.3%
Nov 3591671432,202122,53699.1%
Nov 4465371601,338282,07098%
Nov 5681641011,511131,80399%
Nov 6451031361,162221,43198%

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.