Zambia evidence desk · Adults 18+ · Information, not legal advice

MrPunter in Zambia: checking named public documents

2026-11-19

The supplied public evidence supports one narrow starting point: the English public page title displays the name MrPunter. That observation does not identify a legal publisher, a local host, a licence, local permission, an app, an account, a payment result or service availability in Zambia. The useful question is therefore not whether a name appears, but which separately issued public document connects that name to a specific entity, domain, date and purpose.

What the available evidence establishes

Public page title — checked 19 November 2026

MrPunter appears in the English public page title. Public English page.

Record typeWhat it can showWhat it does not show here
Public English titleA displayed name occurrencePublisher, ownership, licence or Zambian status
Registration-data protocol referenceWhat RDAP is designed to accessA registrant or operator lookup for this brand
Country-code domain categoryThe category assigned to .zmA relationship between a .zm host and this brand

Name occurrence and named publisher are different fields

A displayed name is useful as a search key, but it is not the same as a named legal publisher. For a stronger connection, a reader would need a document that states the entity name and relates it to the relevant service, domain or publication. The document would also need a date or version that makes its scope clear.

Do not fill an empty field with a likely-looking company name. A brand, a domain, a trading name and a legal entity can be different things. The available evidence does not provide an authenticated mapping among them. It also does not establish that a name appearing on one page is the same party named in another record.

Field to compareRecord ARecord BQuestion for the match
Displayed nameWrite the exact spellingWrite the exact spellingAre the characters identical?
Named entityCopy the stated entityCopy the stated entityIs the legal name actually stated?
Host or domainCopy the exact hostCopy the exact hostDoes either record connect the host to the entity?
Date or versionRecord the document dateRecord the document dateDo the dates define the same period?
ScopeDescribe what was reviewedDescribe what was reviewedAre both records about the same service?

What the RDAP reference contributes

RDAP reference — checked 19 November 2026

ICANN describes RDAP as a protocol for accessing registration data. ICANN RDAP reference

For a reader’s own record, separate three things: the protocol description, the result of a particular query and the interpretation of that result. Only the second could contain lookup-specific fields, and even then the relevant field, date and scope would need to be recorded. The available evidence contains no registrant, operator or platform lookup for MrPunter.

RDAP worksheet fieldEntry to recordWhy it matters
Exact query targetFull host or domain as shown on the recordPrevents a result for another host being attached to the wrong service
Returned nameExact registrant or related name, if statedShows whether a named party is actually present
Relationship fieldRole attached to that nameSeparates registrant, administrator and other roles
Record dateDate checked or updatedPlaces the result in time
LimitMissing, restricted or unclear fieldsStops an incomplete result being treated as proof

What the .zm category contributes

A country-code top-level-domain category describes the suffix itself. It does not establish that a brand uses a particular host, that a host is controlled by a particular entity, or that a service has local permission. A suffix can be a useful field in a domain worksheet, but it is not a substitute for a named record.

Domain category — checked 19 November 2026

IANA lists .zm as a country-code top-level domain. IANA .zm category

The relevant comparison is therefore between an exact host and an independently issued record that names the same host or entity. The available material does not establish that connection. Do not infer a Zambian relationship from a suffix category alone, and do not infer a brand relationship from a similar-looking name.

A practical document comparison

When a new public document is available, begin with its heading and issuing body. Then copy the exact entity, host, date and scope before interpreting it. A record that only mentions a name may confirm a name occurrence but may not identify the party behind it. A record that names an entity but does not mention the relevant host may also leave the connection open.

Keep original records separate from working notes. If a document contains unnecessary identifying information, hide those details in the working copy while retaining a secure original. Do not send identity or bank records to an unverified recipient merely because a page requests them. This is a handling precaution, not a finding about any particular recipient.

Document questionClear answer to recordIf the answer is absent
Who issued the document?Exact issuing body or stated publisherMark the issuer as unidentified
What name is used?Exact brand or entity spellingMark the name as unavailable
What host is covered?Exact domain or URL, if statedDo not assign a host from context
What date applies?Document, update or check dateKeep the date unknown
What decision does it support?Only the narrow proposition statedLeave the conclusion open
What does it exclude?Specific limits written in the recordDo not invent a wider limit

Questions about a Zambian connection

A market reference should be explicit. A page written in English is not, by itself, proof of Zambian targeting. A domain suffix category is not, by itself, proof of a local operator. A technical registration reference is not, by itself, proof of local permission. To connect a service to Zambia, the reader would need a dated, relevant record that actually makes that connection.

Use the following order when reviewing a proposed match:

  1. Copy the exact name without correcting its spelling.
  2. Copy the exact host or domain, if one is stated.
  3. Identify the issuing body and the document date.
  4. Read the document’s stated scope and exclusions.
  5. Record only the conclusion supported by those fields.
  6. Leave the local connection open if no record makes it.

This approach keeps a public title, a technical reference and a local record in their proper categories. It also makes a later review easier because another reader can see which field is supported and which field still needs evidence.

What remains unverified

The supplied material does not identify an owner, legal entity, current terms, licence, territorial status, local host, support channel, app, account requirement, payment method, withdrawal result or complaint outcome. It does not establish a registry match, a blacklist or sanction, a rating, a tested account or contact verification. Those are not negative findings; they are unanswered fields within the reviewed scope.

The public English page body was unavailable for the reviewed observation, so its title should not be expanded into claims about the page’s services or conditions. The RDAP reference was reviewed as an introduction, not as a lookup. The .zm reference was reviewed as a category, not as a brand-to-host match. These limits determine how far the current evidence can be taken.

How to keep a dated evidence note

A useful note should allow the reader to reconstruct the narrow claim without relying on memory. Record the source URL, the date checked, the exact visible wording, the document scope and the fields that were not supplied. If a later document changes the position, preserve the earlier note rather than replacing it without explanation.

Use neutral labels such as “name displayed”, “entity stated”, “host stated”, “date stated” and “connection not stated”. Avoid turning an unanswered field into an accusation. The purpose is to distinguish what a record says from what a reader may want it to prove.

Reader checklist

  • Have you copied the brand spelling exactly?
  • Have you recorded whether an entity is actually named?
  • Have you separated a page title from the page body?
  • Have you copied the precise host rather than a guessed domain?
  • Have you recorded the source date and the check date separately?
  • Have you written down the document’s limits?
  • Have you avoided treating a suffix category as an operator match?
  • Have you left unsupported local conclusions open?

For related background, you can compare the general licence-check guidance and the online betting domain checks. Those pages do not change the evidence recorded here. If you want to browse the site’s catalogue, use the reviews catalogue; it is not evidence that a particular operator, host or service has been authenticated.

FAQ

Does an English page prove availability in Zambia?

No. An English title does not establish Zambian targeting, local permission, eligibility, an account, a payment route or service availability.

Does RDAP identify the operator here?

No. The supplied ICANN material explains RDAP as a protocol, but it contains no registrant, operator or platform lookup for MrPunter.

Does a .zm category link a host to MrPunter?

No. It does not establish that a particular host is connected to MrPunter or to a named entity.

What should a new document contain before I record a match?

Record its issuer, exact name, exact host, relevant date, stated scope and any relationship field. Leave the match open when one of those connections is absent.

What is the safest way to handle an incomplete record?

Keep a secure original, use a redacted working copy where needed, record the missing fields and avoid sending identity or bank records to an unverified recipient.

Compare evidence routes

Ready to compare the recorded checks?

Open the single commercial route only after reading the evidence limits.

Compare evidence routes