Why an address may remain unpublished
A status page should not invent a destination to make a card look complete. It may know that a primary URL or alternative WTN Market mirror is expected while still lacking a current, owner-verified address. In that situation, leaving the address unpublished is the accurate choice.
Common reasons for a pending status
- The source does not clearly identify who controls the address.
- Two otherwise credible sources publish conflicting destinations.
- The most recent review is too old for a time-sensitive claim.
- The address redirects to an unexplained or differently spelled domain.
- The destination responds, but ownership cannot be established.
Availability and verification are separate
A server can respond successfully without being the expected service. Likewise, an authentic address can be temporarily offline. “Operational” describes observed availability; “verified” describes the evidence connecting an address to its claimed role. A professional status page does not collapse these two questions.
What evidence can resolve the status
Resolution requires a traceable source, exact address spelling, a recent review and a clear statement of role. If the address is a mirror, the evidence should explain how it relates to the primary destination. Redirect behaviour and certificate warnings should also be documented rather than ignored.
How the interface should communicate pending
Use direct language such as “Awaiting verified owner URL,” show the last review date and explain that no address is being published until verification is complete. Avoid vague labels like “coming soon” when the actual issue is evidence quality. The note should be visible near the affected status entry.
What happens after a decision
When evidence becomes sufficient, record the address, source, review time and resulting status. If a claim is rejected, keep a concise correction entry so readers understand why it was not published. Both outcomes belong in the change log.
Verification pending protects readers and the credibility of the status page. It makes uncertainty explicit, gives maintainers a clear next step and prevents search engines from indexing a speculative destination as though it were confirmed.