The automated traffic DC Hub sends to its own site and APIs, and how to verify it.
DC Hub Monitor is first-party monitoring run by DC Hub (Martone Advisors, LLC). It checks that dchub.cloud is up, that its data is fresh, and that its REST and MCP APIs still return what they promise. It reads each response, checks it and discards it. It does not collect, index, cite or train on content.
It requests DC Hub’s own site and APIs only. When it loads one of our pages in a headless browser, that browser also fetches the page’s own assets (fonts, scripts) the way any visitor would; those asset requests are not signed.
Its requests carry a user agent starting with DCHub- or dchub-, for example:
DCHub-SentinelDCHub-WarmerDCHub-Smoke-Testdchub-site-qadchub-contract-guardA user agent alone proves nothing, because anyone can copy it. Use the signature below.
Requests are signed with Web Bot Auth (HTTP Message Signatures, Ed25519). A signed request carries Signature, Signature-Input (with tag="web-bot-auth") and Signature-Agent headers. The public key is published at:
https://dchub.cloud/.well-known/http-message-signatures-directory
Questions or problems with this bot: [email protected].