Availability answers whether a resource responds; authenticity asks whether the destination and publisher relationship are supported by evidence.
Measure availability narrowly
Record response status, timing and observation date for the exact URL under review.
A successful response is an operational fact, not an identity conclusion.
Review authenticity independently
Check source provenance, domain history, publication continuity and contradictory claims.
These questions remain necessary even when the page loads quickly and looks complete.
Handle outages without overreacting
Temporary downtime can result from maintenance, routing or rate limits.
Move the operational label only when repeated evidence supports the change.
Avoid design-based confidence
Logos, familiar wording and copied layouts can appear on unrelated destinations.
Use branding as a comparison point rather than proof.
Publish two separate findings
State the observed availability and the evidence-based verification status in distinct fields.
Readers can then understand that reachable does not mean verified.