The agent could not access the site directly due to sustained HTTP 429 rate limiting and assembled the answer entirely from web search snippets and third-party guides. The answer is structurally complete but secondhand and unverified against the site's actual current content.

• ›All direct fetches of certificeerwijzer.nl failed with HTTP 429; the agent never read a single page from the target domain. The entire answer derives from search engine summaries (steps [3] and [7]).
• ›Search results [3] and [7] contained actionable summaries (business model, standards covered, cost ranges, matching process), but these are search engine extracts, not the site's own content—the agent could not verify current accuracy or completeness.
• ›The agent identified a potential red flag ('Test mode' text in some pages) and cost figure conflicts across sources (Normwijzer vs. CertificeerWijzer), showing critical thinking despite the access barrier, but could not validate either against the live site.
• ›The agent did not reach the About page, FAQ, request form, or certifier list—critical pages that would answer 'how it works' and 'who it's for' more directly—and had to infer business model and scope from search snippets.
• ›The site appears to have rate-limiting enforcement that blocked automated fetches entirely; the agent worked around this by relying on search engine caches and external third-party commentary (Diks Process Support), which shifted the answer away from first-party authority.