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

MrPunter exact website and app publisher check in Zambia

2026-11-19

Answer in brief

The available documents do not establish a verified MrPunter exact website and app publisher for Zambia. They support a narrower conclusion: the English public page title displays the name MrPunter, while the other reviewed material explains where certain types of registration information may be sought. It does not connect a named company, local record, domain, application or publisher to the same operator.

That distinction matters when an address or application uses a familiar name. A matching word is not, by itself, proof of ownership, permission to provide a service in Zambia, an official host, an application publisher or a local company. Record each identifier separately and only connect them when a dated, authoritative document makes the link clear.

Reviewed page — check date: 19 November 2026

English public page title displays MrPunter. Source

What the reviewed evidence establishes

The public title observation is limited. The readable public body was unavailable, so it does not establish ownership, current terms, licensing, territorial status, the service offered, an official host or an application. It also does not identify a company, person, developer account or store listing.

Avoid converting that observation into a statement that the page is the official website, that an application belongs to the same party, or that a service is available or permitted in Zambia.

IdentifierWhat it can showWhat it cannot show alone
Page titleA name displayed on a reviewed pageOwnership, local permission or an app publisher
Web addressThe literal address entered or recordedThat the address is official or controlled by a named company
Application listingA publisher and store identifier, if documentedThat the publisher controls a particular website
Company recordA registered name or number, if matchedThat the company operates a particular domain or application

How to record the exact web address

Write the address literally. Keep the recorded address separate from the displayed brand name. A short name shown in a title can differ from the host that serves the page, and a redirect can lead to another address. Those details should be recorded rather than silently normalised.

A useful record includes the date and time checked, the address as copied, the page title, the redirect path if one is visible, and whether the page content could be read. Do not infer a company, country or application publisher from a domain ending. A country-code ending can describe a domain category or registration space; it does not by itself prove a local operator or local permission.

FieldEntry to preserveReason
Literal addressFull address, including pathPrevents a brand name replacing the actual address
Page titleExact displayed titleSeparates a visible name from an ownership claim
Check dateDate and time with time zone where availableShows when the observation was made
Redirect detailsEach recorded destinationShows whether the address and destination differ
Readable contentAvailable, partial or unavailableDefines the limits of the observation

What RDAP can and cannot contribute

ICANN record — check date: 19 November 2026

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

RDAP is relevant when a domain registration-data question is being examined, but the reviewed material contains no registrant, operator or platform lookup for MrPunter. The existence of a protocol is not a result for a particular domain. It does not establish that a person or company controls a website, and it does not identify an application publisher.

If a dated RDAP result is later obtained through an appropriate source, preserve the exact domain queried, the response date and the fields returned. Treat privacy-redacted, proxy or unavailable fields as limits. A registration contact, where disclosed, would still need to be compared with a separate company, contractual or application record before the records could be connected.

RecordQuestion it may addressConnection still needed
RDAP responseWhat registration data is returned for the queried domain?Whether the returned details match the operator or publisher
Domain pageWhat title or address is displayed?Whether the page is controlled by the named party
App listingWho is shown as publisher?Whether that publisher controls the domain

What a PACRA search would show

PACRA search page — check date: 19 November 2026

PACRA’s business search accepts a registered name or registration number. Source

The reviewed observation is limited to the public search-field label. No actual search was completed, so there is no established company, match, ownership link or gaming permission in the evidence. Do not describe a search result, absence or company identity unless a dated result has actually been captured and checked.

A company-name search and a registration-number search answer different recordkeeping questions. A name may have spelling variations, while a number is intended to identify a particular record. Neither search, standing alone, proves that the company runs a website or publishes an application. That connection needs a separate document naming the relevant address, service or publisher.

Proposed checkRecord to retainDo not conclude without a match
Registered nameSearch term, date and result identifierThat the result owns or operates MrPunter
Registration numberNumber searched and dated resultThat the number belongs to the website or app publisher
Named officers or addressOnly the fields lawfully available in the resultThat a person or address is the public operator
Business descriptionExact wording and document dateThat the description grants permission for a particular service

How to identify an app publisher

An application publisher should be recorded from the relevant official listing or an independently documented application record, not from an icon, file name or a web page title. Capture the application name, publisher or developer field, store identifier, listing address, version or update date if shown, and the date checked. If the application is supplied outside a recognised listing, record that limitation rather than treating the file as authenticated.

The publisher name must then be compared with the exact web address and any company record. A similar spelling is not enough. A publisher can use a brand name that differs from a legal entity, and a brand name can be displayed by more than one unrelated page. The available evidence contains no app listing, publisher name, store identifier or application verification.

Do not install an unverified file or remove device protections to test an identity. For a private record, retain secure originals separately and use a working copy with unnecessary identifying information hidden. Avoid sending identity or bank records to a recipient whose identity has not been independently established.

Connection worksheet

Use one row per identifier. Record only documented fields; do not infer a relationship. A blank field is more accurate than a guessed relationship.

IdentifierExact valueSource and dateRelationship evidence
Web address
App publisher
Store identifier
Company name or number

To make a connection, look for a document that names two identifiers together, such as a dated publisher record that identifies the exact domain, or a company document that identifies the relevant service and address. Keep the document’s scope and date beside the claimed relationship. A name appearing in two separate places is not the same as a document connecting those places.

Separate complaint and payment records

A complaint, receipt or payment document should be assessed as its own record. Preserve the date, sender or recipient as displayed, reference number, stated amount where relevant, and the exact wording. Do not use a complaint to establish ownership unless the complaint is supported by a competent record that identifies the same entity. Do not use a payment name to establish an app publisher or local permission.

For privacy, keep original documents in a secure location and remove unnecessary identity, account and banking details from working copies. Do not publish those details or send them to an unverified recipient. If a record cannot be connected to the exact address, named company or publisher, mark the connection as unresolved.

Record typeCompareResult to record
ComplaintNamed party, date and subjectAllegation, supported finding or unresolved record
Payment documentRecipient, date and referencePayment record only unless a wider link is documented
Company recordName or number and stated activityCompany record only unless the address is also identified
Application listingPublisher and store identifierApplication listing only unless the website is named

What remains unverified

The reviewed evidence does not establish ownership, a current operator, a licence, territorial status, local eligibility, an official host, an app, an app publisher, a store identifier, support contacts, payment outcomes, withdrawal outcomes or any individual case outcome. It also does not establish a company match or a search result.

Those are not minor wording points. Each claim requires a record that addresses that particular question. A page title can support only the limited observation recorded above. RDAP information, if separately obtained, would address a registration-data question. A PACRA result, if separately obtained, would address a business-record question. An app listing would address a publisher field. None should be substituted for another.

For general background on domain checks, see online betting domain checks. For recordkeeping principles, see the editorial methodology. Brand-specific document questions can be kept with the MrPunter named-document checklist.

Practical decision checklist

  1. Copy the exact web address and record the date checked.
  2. Record the displayed title separately from the domain and any redirect.
  3. Find a dated application listing before recording a publisher or store identifier.
  4. Keep any RDAP response tied to the exact domain queried.
  5. Record a PACRA result only after an actual search and preserve its identifier.
  6. Require a document connecting the domain, company and publisher before treating them as one entity.
  7. Keep complaints and payment records separate from identity conclusions.
  8. Hide unnecessary personal and banking information in working copies.

This approach leaves unresolved fields visible instead of filling them with assumptions. It also keeps the public name observation, domain record, company record and application record in their proper categories.

Frequently asked questions

What does a country-code domain show?

It can describe a domain category or registration space. It does not, by itself, prove a local operator, local permission or a connection to an application.

What does RDAP describe?

ICANN describes RDAP as a protocol for accessing registration data. The protocol description is not a lookup result for a particular domain.

Where would the publisher be identified?

Record the publisher or developer field from a dated application listing or other independently documented application record, together with its store identifier.

What else is needed to establish a link?

A dated record must connect the exact address, named company or application publisher. Similar names appearing in separate records are not enough.

Does the reviewed evidence verify an official MrPunter app?

No. The reviewed evidence contains no application listing, publisher name, store identifier or app verification.

Browse the review catalogue

Compare evidence routes

Ready to compare the recorded checks?

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

Compare evidence routes