Comparing origin and edge evidence without exposing private infrastructure
Origin and edge observations can help locate a response difference, but infrastructure details should stay in an authorized operational record. Public reporting needs the symptom and verified outcome, not private endpoints.
Compare equivalent requests safely
Have an authorized operator record the public URL response and the corresponding origin behavior under known conditions. Capture timestamps, intended route, status and a safe content fingerprint. Do not publish private hostnames, access tokens or bypass instructions. If the two requests require different routing or authentication, note that limitation instead of claiming a perfect comparison.
Use the difference to narrow the repair
If the origin has the intended content but the public response differs, investigate the relevant delivery layers. If both are wrong, examine the application or stored content. These are investigative directions, not proof of a particular cause. After repair, verify the normal public URL because that is the route visitors use.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Should an origin address be added to a customer-facing report?
Usually the useful evidence is the observed difference and resulting public behavior. Keep sensitive operational details in the restricted record needed by the responsible operator.