Bot traffic: bastropradio.com

all sites · all domains · last 15 days

All sites · All Domains · Visit bastropradio.com

Who is really visiting bastropradio.com?

Between Oct 23 and Nov 6, bastropradio.com received 65,043 requests. About 99.3% came from automated software and about 0.3% look like real people.

That works out to about 120 human visitors, roughly 8 a day, who opened 180 pages between them. 26 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.3%of requests from bots
120human visitors (estimate)
180pages opened by people
65,043total requests, 15 days

Where the requests came from

People 0.3%Named bots 5.2%Disguised bots 6.3%Scanners 88%Unclear 0.3%

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.

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

The breakdown

SourceRequestsΣ 65,043ShareData sentBlockedby the serverWhat this means
Break-in scanners50,10677%74 MB28,180Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,02411%30 MB28Other requests from an address also caught probing for weak spots.
Disguised scrapers2,6684.1%22 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.
Search engines1,1801.8%7 MB4Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,1781.8%7 MB8Any other software that identifies itself as a bot.
Scripts and tools1,0961.7%3 MB4Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers8811.4%1 MB43AI companies gathering pages or answering a user's question, and saying so.
No name given3130.5%2 MB5Requests that give no software name at all.
Unclear2020.3%3 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1730.3%<1 MB57Commercial tools that sell data about websites.
Likely people1150.2%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people1070.2%<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.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines535
ClaudeBotAI crawlers364
GooglebotSearch engines215
bingbotSearch engines161
QlyzeBotOther named bots139
OAI-SearchBotAI crawlers102
RiverBotOther named bots88
GPTBotAI crawlers81
ElevenlabsCrawlerOther named bots81
ibou-searchOther named bots81
BarkrowlerSEO and marketing tools78
fresh-domain-watchOther named bots67
ExaSearchBotOther named bots59
Amzn-SearchBotSearch engines59
SemrushBotSEO and marketing tools54

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/105
/radio/3
/history/3
/starlink/3
/about/3
/tv/3
/referral/2
/sitemap/2
/social.html2
/resources.html2
/social/2

How people arrived

Referring siteHuman visitors
podsat.com64
m.baidu.com19
www.google.com4
search.yahoo.com1
www.bing.com1
bastropbeat.com1
www.baidu.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/1626540
66.249.0.0/161763
102.129.0.0/161231
185.220.0.0/167511
154.28.0.0/16442
183.207.0.0/16421
148.135.0.0/16401
43.157.0.0/163716

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23453091514,056134,53799.5%
Oct 2415362002093,74664,20299%
Oct 25333111304,073104,53199.6%
Oct 2610122332214,961135,44099.5%
Oct 2722361942355,43065,90499.2%
Oct 288123262175,553296,13999.3%
Oct 2916171575532,48193,21899.2%
Oct 30881471972,626112,98999.4%
Oct 319131941908,701159,12299.6%
Nov 18102331,0642,486253,82199.0%
Nov 2552432344,268104,76299.6%
Nov 3351451973,779174,14499.4%
Nov 4683521561,976152,51099%
Nov 5572151981,631202,07698%
Nov 6231531251,36331,64899.6%

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.