A project may publish a human-readable page while delegating machine-verifiable facts elsewhere. Domain records are a common example: the page introduces the project, while the domain owner controls records that can independently assert a value.
When a document says that a resolver remains authoritative, that wording should narrow the search. It suggests checking the name system rather than guessing another hidden URL.
As always, scope matters. Query only the public record named by the project, and record exactly what was returned at the time of observation.
A verification trail is strongest when each step comes from the project itself: publication, maintainer, release, record identifier, then authoritative response.