Pelican in Zambia: host and document checks
2026-11-17
If you are checking Pelican in Zambia, the available documents support a careful source-and-host review rather than a confirmed local identity. Start by recording the exact hostname shown on each document, then compare its stated name, issuer, date and subject with an independent record. A country suffix can describe a domain category, but it does not by itself identify a publisher, grant permission or connect a site to a particular legal party.
What this review can establish
The useful starting point is narrow: one reviewed public terms document uses the Pelican Casino name, while separate reference material explains a country-code domain category and a registration-data access protocol. Those observations should remain separate. They do not authenticate an account hostname, identify a company, confirm a Zambian address or show that a service is available to readers in Zambia.
That distinction matters when a document contains a brand name but the address, issuer or legal party is unclear. A label can be copied, reused or presented in a different market. The correct question is not whether two pages look similar. It is whether an independent record connects the exact host and the named party for the specific purpose being checked.
| Question | Record to capture | What it would answer |
|---|---|---|
| Which host is being discussed? | Exact hostname, including subdomain | Whether two documents refer to the same address |
| Who issued the document? | Named organisation, publication date and issuing channel | Whether the document has an identifiable source |
| What is the document about? | Heading, subject, scope and stated market | Whether it addresses identity, registration or another topic |
| What remains unproved? | Missing party, licence, address or jurisdiction link | Which follow-up record is still needed |
The narrow Pelican-labelled observation
Terms label — check date: 17 November 2026
Pelican Casino appears in the reviewed English terms title. Source: terms page.
This is a naming observation only. It does not establish that the address is an official Pelican host, that the document belongs to a Zambian service, or that a named business stands behind it. It also does not provide a reliable basis for inferring contacts, payment arrangements, account behaviour or a local regulatory position.
When preserving this record, keep the exact address and the visible heading together. Do not replace the address with a shortened brand label. If a second document uses a different hostname, treat it as a separate record until an independent source connects the two. A matching logo, colour scheme or wording would not be enough to make that connection.
How to record the host without overclaiming
A host record should be literal and reproducible. Write the complete hostname as displayed, including any subdomain. Record the page path separately, because a terms page and an account or payment page may not have the same address. Add the date on which you checked the document and describe only what was visible. If a page could not be read, record that limitation rather than filling the gap from another site.
Do not turn a domain name into a legal identity. A hostname is an address component, not a company certificate. Similarly, a brand name in a heading is not proof that the host is owned, operated or authorised by the brand. The working file should therefore have separate fields for the label, host, issuer and legal party. Leave a field blank when the evidence does not supply it.
| Field | Exact entry | Safe wording when absent |
|---|---|---|
| Brand or page label | Text shown in the heading or title | “Label observed; ownership not established” |
| Hostname | Complete host copied exactly | “No exact host recorded” |
| Issuer | Name of the body that published the record | “Issuer not identified in the reviewed material” |
| Legal party | Named company or person, if expressly stated | “No legal party admitted” |
| Market or jurisdiction | Only the market expressly covered | “Local scope not shown” |
What a .zm suffix can and cannot show
Domain category — check date: 17 November 2026
IANA lists .zm as a country-code top-level domain. Source: IANA domain database.
A country-code top-level domain is a useful technical clue about the suffix, but it is not a complete identity record. It does not, on its own, name the publisher of a particular host, show where a service is run, prove that an address belongs to a local business or establish permission to offer a product.
For a practical comparison, place the suffix in one column and the actual identity evidence in another. The suffix may help you describe an address accurately. It should not be used as a substitute for an issuer record, a named party or a document that covers the relevant activity. If the address has no .zm suffix, that absence also does not decide the question by itself.
Keep the country and the source separate in your notes. “The address uses a country-code suffix” is a technical description. “The publisher is a Zambian company” is a different claim requiring its own support. The first cannot be silently expanded into the second.
Why an RDAP reference is not a completed lookup
Protocol description — check date: 17 November 2026
ICANN describes RDAP as a protocol for accessing registration data. Source: ICANN guidance.
A description of RDAP explains the purpose of a protocol. It is not the same as a performed query for a particular hostname. Without a recorded query result, the review cannot attribute a developer, registrant, organisation or exact legal party to the address. Avoid presenting a protocol description as if it were an ownership record.
If a future record is obtained through an authorised and appropriate registration-data channel, preserve the query target, response date and fields returned. Note any privacy redaction or incomplete result. A returned registration field may still need comparison with an issuer or legal document before it can support the identity claim you want to make.
| Evidence type | Useful for | Not enough on its own for |
|---|---|---|
| Visible terms heading | Recording the displayed label and document scope | Authenticating the host or legal publisher |
| Country-code category record | Describing the suffix classification | Showing local ownership or permission |
| Protocol guidance | Explaining how registration data may be accessed | Proving that a query was made or identifying a party |
| Issuer document | Connecting a named party to a stated act or record | Any unrelated host not named in that document |
Build an independent document trail
An independent trail should contain records with different functions, not several copies of the same label. One document may identify an issuer. Another may identify the exact host. A third may describe the activity or jurisdiction covered. The value comes from a clear connection between those records, not from the number of pages collected.
For every proposed connection, write the proposition in plain language. For example: “This issuer record names this party”; “this document names this host”; or “this act covers this stated activity.” Then identify the record supporting that proposition. If no record supports the link, mark it as unresolved. Do not bridge the gap with a search snippet, a visual resemblance or a statement copied from an unverified page.
Keep document dates distinct. The date you checked a page tells the reader when you observed it. A publication or act date tells the reader when the source says the document was issued. Do not merge those dates or present a later check date as the date of the underlying record.
Private worksheet for comparing records
The worksheet below is designed for a private file. Keep secure originals separate from working copies. Remove unnecessary identifying information from copies and do not send identity or bank records to an unverified recipient merely to fill an evidence gap.
| Record | Exact host or reference | Named party | Scope | Open question |
|---|---|---|---|---|
| A | Copy the address exactly | Write only an expressly named party | State the document subject | Who issued it? |
| B | Copy the address exactly | Do not infer ownership | State the stated market or activity | Does it cover the same host? |
| C | Copy the reference or act number | Record the issuer | Record the date and stated purpose | What connection is documented? |
Decision points before relying on a document
Pause when the exact host is missing, when the document names only a brand, or when the alleged issuer cannot be identified from the record itself. Pause again if the document covers a different market or a different activity from the one being considered. These are scope problems, not matters to solve by guessing.
A useful next step is to seek a record that states the relevant party, the relevant host and the relevant purpose in a form that can be checked independently. If those elements are split across documents, record the precise link between them. If there is no link, keep the conclusion limited to the individual observations.
For broader background on checking licences and records, see the licence checks guide and the review methodology. For a general route when a document or transaction needs to be challenged, use complaints guidance. These links provide general context; they do not add an identity finding for Pelican.
Practical record of unresolved points
Write unresolved points as questions that another reviewer can answer from a new document. Suitable questions include: Which hostname is written down? Which body issued the document? What activity does it cover? What date belongs to the document itself? Does an independent record name the same party? Is the proposed connection explicit or merely assumed?
A clean unresolved list is more useful than a confident conclusion unsupported by a source. It also protects against accidentally transferring a name, address or legal description from one market to another. If a later record answers one question, update only that field and retain the earlier scope and date.
FAQ
Does the Pelican label prove the exact host?
No. It records a visible label on the reviewed document, but it does not authenticate an account hostname or establish a publisher.
Does a .zm suffix prove local permission?
No. A country-code suffix describes a domain category; it does not prove local ownership, permission or service availability.
Was an RDAP ownership lookup completed?
No completed lookup is admitted here. Protocol guidance explains access to registration data but does not identify a party without a query result.
What should I write down first?
Record the complete hostname, page path, visible heading, check date and document scope before comparing it with another record.
Can two similar names be treated as one service?
Not without an independent record connecting the exact hosts or parties. Keep similar names as separate records until that link is documented.
What should I do with an incomplete document?
Preserve its exact scope, mark the missing fields and seek an independent issuer or host record rather than filling gaps by inference.
Bottom line for the file
The defensible record is limited: a Pelican-labelled terms page was observed, a .zm suffix is classified as a country-code top-level domain, and RDAP is described as a registration-data access protocol. Those points do not authenticate a particular host, identify a legal party or establish a Zambian permission. Keep the observations in their original scopes, use an independent document for any proposed connection and leave unresolved fields open until the relevant record is available.