FAQ
Find answers to common questions about the Sitebulb Labs Extension, including how it scans sites, handles data and reports AI agent readiness.
What does the extension send outside my browser?
Your browser requests public pages and files from the site you’re scanning,
and from another host only where that site declares it as its own agent
endpoint. If you enable emerging checks, the extension also sends the site’s hostname
to Cloudflare for a DNS lookup. It does not send Cloudflare the full page URL
or your audit results. Nothing goes through a Sitebulb server. Results are
cached temporarily in chrome.storage.session and cleared when the browser
session ends. See the full Privacy Policy for details.
Why does a check show “N/A” instead of “Fail”?
Several Protocol Discovery and Commerce checks (MCP Server Card, x402, UCP, ACP, and others) probe standards that are still emerging — their well-known paths may evolve, and most sites correctly have no reason to implement them yet. An unverified probe returns “not detected” (N/A) rather than “fail” for these, so a normal site’s score isn’t unfairly punished for not adopting a standard that’s still taking shape.
Why does DNS-AID show N/A?
DNS for AI Discovery is a proposed TXT-record convention that isn’t finalized. If you enable emerging checks, the extension checks for it using DNS-over-HTTPS via Cloudflare. A site without an agent-discovery TXT record shows N/A rather than Fail, so its score is not penalized.
Why does the extension request access to all sites?
It needs to audit whichever site you choose, including as you browse with the side panel open. Chrome grants access to HTTP and HTTPS sites for that purpose; the extension does not prompt separately for each domain. See the Privacy Policy for the permission details.
Can I choose which checks run?
You can turn emerging checks on or off in settings; they are off by default. The extension also skips content-only checks for hostnames that identify themselves as APIs. There is no manual check-set selector. See Check reference.
Where do the check definitions live?
They’re in a data-driven registry, one file per category, each returning a status, a human-readable detail, an optional recommendation, and evidence. See Check reference for the full list.