How to read a failed retrieval
Recording that we could not read a document is as important as recording what we could read. The source list says which of those happened.
- Redirect. The old brand’s domain now points at a successor. That is not a geo-block. Example: Fortune Coins → Fortune Wins.
- Not attempted. We have not yet located a rules URL. Homepage retrieval is not a blocked official-rules document.
- Blocked or unreadable. We requested a specific rules or help path and the response was a refusal, a geo-block, or a page whose text we could not read. That is dated. It is not a finding that no terms exist.
A recorded gap is not an empty page. Where an operator’s own documentation states a minimum or a processing time, the profile is published with every gap named beside it — see Chumba Casino, which states both and has no fee established in the record. Where it states neither, the profile still exists and still lists what we read; it simply is not offered as an answer to a question it cannot answer. What a readable document states is still not what redemptions were seen to do: published is not observed.
Worked-example sources: Fortune Coins redirect response (checked 2026-08-15); Chumba Sweepstakes Rules and Chumba terms addendum (checked 2026-08-21).