mySites.guru service traffic

mySites.guru monitors, audits, updates and backs up WordPress, Joomla and PHP sites for the people who run them. It is operated by Blue Flame Digital Solutions Limited, United Kingdom.

It only contacts sites whose owner added them to mySites.guru. It does not crawl, follow links, index pages or collect content for AI training.

User-Agents and addresses

Connector calls and uptime checks each come from one address, and each address has matching forward and reverse DNS.

Traffic	User-Agent	IP address	Reverse DNS
Connector callsSigned · Ed25519	User-Agent `mySites/6.0 (+https://mysites.guru/bot/)`	IP address `178.62.5.35`	Reverse DNS`main-workers.mysites.guru`
Uptime checks	User-Agent `mySites/6.0 (+https://mysites.guru/bot/)`	IP address `165.227.239.229`	Reverse DNS`monitor-engine.mysites.guru`

On OVH hosts the connector sends the bare mySites/6.0, because OVH rejects a User-Agent with brackets in it. Connector calls and uptime checks also send the header X-Questions: Please email phil@phil-taylor.com. The same addresses are published as plain text at manage.mysites.guru/ips.

What we request

The requests mySites.guru sends to a connected site, how often, by which method, and what each asks for
Request	How often	Method	What it asks for
Uptime check	Every 5 minutes	HEAD	The site's home URL
Connector call	Snapshots about every 12 hours; audits, backups and updates when the owner runs them	POST	The connector the site owner installed
robots.txt and sitemaps	With each snapshot	GET	`/robots.txt`, then up to six sitemap URLs
Header check	With each snapshot	GET	A URL that should not exist
Admin URL	With each snapshot	GET	`/administrator/` on Joomla, `/wp-admin/` on WordPress
Certificate check	At most twice a day	TLS handshake	The SSL certificate
Favicon	During an audit only	GET	The home page and its favicon

The uptime check has a 45 second timeout, follows redirects, and ends on a 2xx response. Nothing else on the site is requested. Only if it fails do we try again: a second HEAD 10 seconds later, then a GET 10 seconds after that.

The connector lives at /plugins/system/bfnetwork/ on Joomla,/wp-content/plugins/mywpguru/ on WordPress and/bfnetwork/ on other PHP sites. Only one audit runs at a time per server, and with the update queue on, only one update at a time per account and server.

The sitemap request reads up to three sitemaps that robots.txt declares, plus/sitemap.xml,/sitemap_index.xml and/wp-sitemap.xml, and takes at most 600 bytes of each. The header check fetches /X-mySites-guru-Header-Check-For-Snapshot-Should-Be-A-404 to read the security headers the server sends, and the admin URL request shows whether the admin area is restricted; neither follows redirects. The favicon request checks whether the site still uses the default Joomla icon, and sends no User-Agent today.

robots.txt

We read robots.txt to tell the site owner what it says, for example that it blocks search engines by mistake. We are not a crawler, so we do not apply its rules to our own requests: each one goes to a site its owner registered with us.

Is it really us?

Look up the reverse DNS for the address in your log, then look up the name it returns. If the second answer is the address you started with, the request came from us. A request with our User-Agent from any other address did not come from us.

178.62.5.35

dig +short -x 178.62.5.35
dig +short main-workers.mysites.guru

165.227.239.229

dig +short -x 165.227.239.229
dig +short monitor-engine.mysites.guru

Check the signature

Connector calls are signed with Web Bot Auth (the IETF HTTP Message Signatures for bots draft, built on RFC 9421), using Ed25519. Each request has the headers Signature, Signature-Input and Signature-Agent: sig1="https://manage.mysites.guru". The signature covers the host and the signature-agent member and is valid for 60 seconds, so a copied header is useless against another site and expires within a minute. Check it against the public key in the directory at https://manage.mysites.guru/.well-known/http-message-signatures-directory.

Key ID

PetbnHRFHSGbLUOwohXvoGOqNry-ox7cKdq34htUz-A

Uptime checks are not signed yet. Verify those with the reverse DNS lookup above.

Let it through Cloudflare

If your site is behind Cloudflare and our checks are being challenged, add a WAF custom rule with this expression and the Skip action:

Expression

(http.user_agent contains "mySites/" and ip.src in {178.62.5.35 165.227.239.229})

Cloudflare now lists mySites.guru as a verified agent, with a public listing on Cloudflare Radar. On plans with Super Bot Fight Mode, a rule on cf.client.bot with the Skip action, or the Verified bots group set to Allow, lets connector calls through without naming us. The User-Agent and address rule above remains the fallback, and there is no harm in keeping both.

Have it skip Super Bot Fight Mode and the managed rules, plus any custom rules of your own that challenge automated traffic. The rule matches the User-Agent and the address together, so a stranger copying our User-Agent from another address is still challenged. Bot Fight Mode, the free plan's version, cannot be skipped by a rule; if it blocks us, turning it off is the only fix.

How to stop it

The site owner can stop both kinds of traffic. Deleting the site's uptime monitor in mySites.guru stops the uptime checks. Removing the site from mySites.guru and uninstalling the connector stops everything else, because without the connector there is nothing for us to call. If you run the server rather than the site, email us and we will contact the owner.

Contact

Email phil@phil-taylor.com, the address in the X-Questions header. A person reads it.

Changes

31 October 2026
Cloudflare lists mySites.guru as a verified agent in its Bots and Agents Directory, classified under Monitoring & Operations and Security Testing: the listing on Cloudflare Radar.
24 October 2026
We incremented the version to 6.0. Connector calls and uptime checks now both send mySites/6.0 (+https://mysites.guru/bot/).
24 October 2026
Connector requests are now signed with Web Bot Auth. Uptime checks are not.
24 October 2026
Page published. Both User-Agents now point here. Before this the connector sent mySites/5.4 (+https://manage.mySites.guru) and the uptime checks sent Mozilla/5.0+(compatible; mySites/1.0; https://monitor.mysites.guru/).

Last reviewed 31 October 2026. This page is maintained by hand and updated whenever our traffic changes.