Some cookies are necessary for SecondDoor to work. Others are optional, and tell us how the site and the product are used. Accept all, or decline all optional ones. Without a selection, nothing optional is set. More in our cookie policy.
Basic scanUnclassified/Scanned 8 Sept 2026, 14:25 UTC/1 browser pass
A browser-blocking wall prevents both human agents and AI assistants from reaching the site, while the homepage itself publishes no machine-readable content about what is offered.
Older scan
This report was produced by an earlier version of the scanner. Some findings may not match how the site is measured now.
Severe. Your human funnel and your agent funnel are different products.
Ordered by what the evidence says is costing most. Written for whoever owns the site, not whoever builds it.
1 piece of evidence and the recommended fix are recorded for this issue, with notes written from your own pages.
This is a basic scan, so it raises the three issues the deterministic evidence supports. A deep scan sends two agents over the site and raises up to ten, each with cited evidence and the screens to prove it.
A deep scan walks the site with two agents, records cited evidence and screenshots, and keeps a mission timeline. It comes with the paid plans. Making an account costs nothing and gives you one basic scan a month.
The score and the audit trail stay public. The evidence and the files open with an account.
The audit trail behind every number above. Not measured is not zero.
Machine discoverability
No sitemap, no schema.org markup, and no JSON-LD on the homepage. A real browser is refused with a press-and-hold challenge, and the HTTP response to non-browsers is a 300-byte shell that redirects with JavaScript.
4 observations recorded.
Programmatic onboarding
No API documentation is linked from the homepage. No OpenAPI spec exists at any of the 6 standard paths checked. The product requires no account, so there is no programmatic signup to measure, but there is also no way for an agent to.
3 observations recorded.
Pricing legibility
Could not verify: this scan did not reach the pages that would show it.
1 observation recorded.
Agent-aware instrumentation
No MCP manifest at any of the 3 standard paths checked. No ai-plugin.json, no llms.txt, and no Web Bot Auth signals. The site publishes no machine-readable instructions for how agents should interact with it.
4 observations recorded.
Machine-fetchable trust
No security.txt at /.well-known/security.txt. No trust signals are published in machine-readable form. An agent cannot verify the site's identity or find a security contact.
2 observations recorded.
Commercial rails
.
2 observations recorded.
Steps to first value
The product is usable immediately with no account required and no signup form. A visitor can access the site's core offering without any steps, provided they can get past the browser-blocking wall.
1 observation recorded.
Required fields
No form exists on the homepage. No fields are required because there is no account system. A visitor is asked for nothing.
1 observation recorded.
Verification walls
No account system exists, so there is nothing to verify. A visitor faces no verification wall, email confirmation, or identity check.
1 observation recorded.
Error recovery
No form means no validation errors to recover from. The only error a visitor encounters is the browser-blocking challenge itself, which offers no recovery path or explanation.
1 observation recorded.
It got through 5 of 14.
The agent got through 5 of 14 requests, but could not read the site's own guide for language models. It came up empty on 8 other checks too. That is enough missing for a machine to give up before it reaches a purchase.