Bot traffic: codedspring.com

all sites · all domains · last 15 days

All sites · All Domains · Visit codedspring.com

Who is really visiting codedspring.com?

Between Oct 23 and Nov 6, codedspring.com received 23,896 requests. About 99.1% came from automated software and about 0.2% look like real people.

That works out to about 30 human visitors, roughly 2 a day, who opened 34 pages between them. 2 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.1%of requests from bots
30human visitors (estimate)
34pages opened by people
23,896total requests, 15 days

Where the requests came from

People 0.2%Named bots 20%Disguised bots 32%Scanners 46%Unclear 0.8%

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.

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

The breakdown

SourceRequestsΣ 23,896ShareData sentBlockedby the serverWhat this means
Break-in scanners9,29839%2 MB31Probing for WordPress logins, password files and other common weak spots.
Disguised scrapers7,48631%65 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 browsers1,7857.5%8 MB23Other requests from an address also caught probing for weak spots.
Search engines1,7327.2%10 MB1Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,6446.9%10 MB4Any other software that identifies itself as a bot.
SEO and marketing tools8013.4%4 MB2Commercial tools that sell data about websites.
AI crawlers6822.9%1 MB1AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools2381.0%2 MB4Programs such as curl or Python, or anything with an unrecognizable name.
Unclear1870.8%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people340.1%<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 given40.0%<1 MB0Requests that give no software name at all.
App link sweepers30.0%<1 MB0Touches only login, app or embed links and no actual content.
Likely people20.0%<1 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.

Named bots

Botas it names itselfTypeRequests
GooglebotSearch engines552
SemrushBotSEO and marketing tools491
PetalBotSearch engines423
bingbotSearch engines381
ClaudeBotAI crawlers337
Amzn-SearchBotSearch engines245
OAI-SearchBotAI crawlers233
JambotOther named bots200
SEOJuice-SearchBotOther named bots195
QlyzeBotOther named bots166
AhrefsBotSEO and marketing tools137
GoogleOtherOther named bots123
ibou-searchOther named bots86
DotBotSEO and marketing tools82
DzzyXtractOther named bots66

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/10
/products/pm-detent-polymagnet-pair-4-position-90-degree-6-ctsk-1-d-sh/3
/videos/3
/products/pm-spring-latch-polymagnet-pair-keyed-center-hole-1-diameter/2
/products.html2
/products/pm-small-tablet-polymagnet-pair-twist-release-1-125-diameter/2
/go/polymagnet/2

How people arrived

Referring siteHuman visitors
www.google.com26
www.bing.com2
noai.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
192.42.0.0/161,13067
5.102.0.0/163553
185.220.0.0/1624052
104.199.0.0/162321
103.196.0.0/161443
66.249.0.0/16994
34.22.0.0/16961
104.164.0.0/16962

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2321214161,16843692,05198%
Oct 241340546436061,23899.3%
Oct 2524365338727141,44899%
Oct 2633332602811161,76499%
Oct 2700451592483121,53899.2%
Oct 28003014801601095199%
Oct 2911338752116121,22099%
Oct 3011495393499181,40699%
Oct 3100269396901111,57799.3%
Nov 1004234511,58592,46899.6%
Nov 20020243469671,33999.5%
Nov 3002544742,690113,42999.7%
Nov 411241538658151,45399%
Nov 500182356815171,37099%
Nov 6001852931462064497%

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.