Bot traffic: bastropbuilder.com

all sites · all domains · last 15 days

All sites · All Domains · Visit bastropbuilder.com

Who is really visiting bastropbuilder.com?

Between Oct 23 and Nov 6, bastropbuilder.com received 64,284 requests. About 99.1% came from automated software and about 0.4% look like real people.

That works out to about 83 human visitors, roughly 6 a day, who opened 174 pages between them. 41 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
83human visitors (estimate)
174pages opened by people
64,284total requests, 15 days

Where the requests came from

People 0.4%Named bots 8.1%Disguised bots 7.9%Scanners 83%Unclear 0.6%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,5005,0007,50010,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.

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

The breakdown

SourceRequestsΣ 64,284ShareData sentBlockedby the serverWhat this means
Break-in scanners44,66069%66 MB25,794Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers8,77014%41 MB32Other requests from an address also caught probing for weak spots.
Disguised scrapers3,9246.1%34 MB31Claims 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 engines1,7502.7%10 MB7Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers1,5772.5%2 MB105AI companies gathering pages or answering a user's question, and saying so.
Other named bots1,5762.5%10 MB26Any other software that identifies itself as a bot.
Scripts and tools1,1571.8%3 MB7Programs such as curl or Python, or anything with an unrecognizable name.
Unclear3690.6%7 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools2740.4%1 MB79Commercial tools that sell data about websites.
Likely people1420.2%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people830.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 given20.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines782
ClaudeBotAI crawlers446
GooglebotSearch engines390
bingbotSearch engines178
QlyzeBotOther named bots161
ISPDomainVerifierOther named bots144
OAI-SearchBotAI crawlers138
GPTBotAI crawlers115
BytespiderAI crawlers103
ibou-searchOther named bots95
RiverBotOther named bots90
BarkrowlerSEO and marketing tools86
BaiduspiderSearch engines85
SERankingBacklinksBotSEO and marketing tools81
Kimi-SearchBotOther named bots76

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/44
/trades/5
/press/4
/guide/4
/about/3
/sources/3
/faq/3
/builders/2
/resources/2
/history/2
/research/2
/news/2

How people arrived

Referring siteHuman visitors
www.google.com31
m.baidu.com19
claudefieldguide.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/1627439
91.99.0.0/161741
64.16.0.0/1617126
82.26.0.0/1613021
102.129.0.0/161002
66.249.0.0/16813
158.69.0.0/16682
183.207.0.0/16642

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 238113031733,975284,49899%
Oct 248131972992,655303,19699%
Oct 25556491904,540285,41499.4%
Oct 266101122753,094143,51099.2%
Oct 278232562554,630175,18499.2%
Oct 28452102954,292284,83399.3%
Oct 29572063932,067132,68899.2%
Oct 307163932043,172193,80699.0%
Oct 319141962098,871329,32999.4%
Nov 1698361,5003,537475,93499%
Nov 27242624454,637185,39099.1%
Nov 3471773163,108163,62599.3%
Nov 4578281641,834182,85299.1%
Nov 55183582482,148422,81798%
Nov 635194117870191,20898%

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.