Why are parts of my finder result unconfirmed?
An unconfirmed field means we cannot support an answer about that part of the casino. It is not a yes, a no, or a reason to treat the casino as a fit.
The finder separates what it could check from what it could not. A result can meet one recorded preference while another remains unresolved; when none is confirmed as met, it is shown separately rather than presented as a recommendation.
Who this is for
Someone who has used the finder, seen a missing fact or an unconfirmed result, and wants to understand what the answer actually supports before relying on it.
Where it depends on you
Which preferences you answered and which evidence exists for each field. A gap about a preference you did not set cannot tell you whether the site meets it.
Read the fact and its evidence together
A casino profile is not confirmed in one piece. Each attribute carries its own evidence status, and a sourced field points to the document and date behind it. A checked free-entry route cannot establish a payment method, interface detail or redemption window. Read the line you need, then the evidence attached to that line.
A provisional value is a starting record that has not been established. A missing value is a gap. Neither becomes a fact because another field is well sourced or because the page has a recent date. The published field ledger and source register linked below show what we hold; an article date is not a fresh operator check.
An unknown preference does not earn a match
For preferences that contribute to fit, missing or insufficiently evidenced data counts neither for nor against the calculation. The finder uses only the weighted criteria it could check. A dated internal observation and an operator-published fact have different provenance; the line should tell you which supports it. An unverified seed cannot contribute positive credit.
A must-have has a different job: it decides whether a casino stays in the eligible sample. When an active exclusion cannot establish that a must-have is met, that casino is excluded. Some questions are withdrawn entirely when the records cannot support offering them. A question that is not offered has not silently been answered for you.
Walk through two hypothetical records
Imagine that you ask about free entry and a simpler interface. Record A has supported evidence that meets the free-entry preference, but its interface description is unconfirmed. Its result can explain the supported match and the unresolved preference separately. It must not say that both have been established.
Record B has no usable evidence on either answered weighted preference. An empty evidence base does not make it a stronger match. The engine places such a record after eligible records with known evidence on an answered weighted criterion; the interface separates it from supported fits. These are invented records illustrating the rules, not claims about real casinos.
Even Record A is only a fit on what could be checked. The plain count beside a name does not determine the order by itself: the published rules assign different weights. A higher place cannot settle an unconfirmed fact or certify the operator as a whole.
Three empty answers mean different things
“Nothing cleared every must-have” means no site in this sample passed all the active exclusions for those answers. Read the recorded exclusion reasons. It is not a claim that no suitable operator exists anywhere, and a practical state filter is not a legal determination.
“No confirmed fit” means the returned records do not establish anything you said mattered as met. “Nothing to compare on” means your answers did not supply a weighted comparison criterion. The latter is different from missing evidence: there was no such comparison to make. Neither message should be read as a recommendation to pick the first alphabetic name.
Why a question can be unavailable
A question is useful only if the records and active rules can answer it. The finder withdraws payment and crypto questions while their evidence requirements are unmet; game must-have questions also have their own evidence gate. Their absence describes this publication’s coverage, not what every operator does or does not offer.
A previously saved or shared answer to a withdrawn question does not restore that capability. The process explanation and methodology linked below show the current offered sequence and the running and withdrawn rules. Do not assume that a shorter form has already checked a requirement you could not enter.
Make the next check specific
Identify the unresolved fact that matters to your decision. Open the cited source where one exists, read its date, and check the operator’s current information for that exact point. If no source supports the answer, keep it unresolved. A different preference cannot repair missing evidence about a non-negotiable requirement.
You can return to the finder and answer for yourself, or read the dated corrections log linked below to see what changed. Do not change your state or dismiss a real requirement just to produce a list. A useful result can be a clear explanation of why the available records do not yet justify a choice.
The tradeoffs
- A smaller supported answer is easier to defend, but it may leave the question you most care about unresolved.
- Ordering reflects the published rules and available evidence for your answers. It does not measure every feature, experience or risk at an operator.
Where this answer stops
- This page explains the existing finder. It does not confirm a new operator attribute, change any rule, establish legal eligibility or recommend an unconfirmed site.
- The worked records are hypothetical. For a real result, use that result’s own reasons, drawbacks, dates and source links.