dreamcatcher official website: how to verify the platform.

Source the URL

Confirm the URL from a verified source such as the platform verified social account or its app store listing.

Check SSL

Check the SSL certificate is valid and matches the platform domain.

Match the licence

Verify the platform name appears on the licence disclosure page.

Match the company

Match the registered company name on the footer with the platform published company data.

Licence holder

Licence holder name and licence number.

Regulator

Regulator name and complaint pathway.

Responsible play

Responsible-play controls and self-exclusion pathway.

RNG certification

RNG certification disclosure with named testing lab.

Search the brand token directly

Type the brand token directly into the browser's address bar instead of clicking a paid search result. The browser will route you to the platform's published URL. Paid search results above the official URL are a common phishing vector.

Check the SSL certificate

Click the padlock in the address bar and read the certificate. The certificate should match the platform's published company name. A certificate issued to an unrelated organisation or an unrecognised domain is a warning sign.

Cross-reference with the app store

If the platform publishes a mobile app, search the app store for the platform's published name. The app store entry lists the publisher name; the publisher name should match the platform's published company name. An app store entry that points to a different publisher is a warning sign.

Read the platform's published terms

The official site carries the platform's published terms, KYC method and responsible-play controls. A mimic site may copy the home page but will not carry the current version of the terms. Compare the terms URL and the home URL; both should sit on the same registered domain.

What the desk does not publish

The desk does not publish customer-care phone numbers, ownership data or app-store ratings not already published on the platform itself. Where a reader wants to verify a phone number, the desk directs the reader to the platform's own contact page.

Source 1: the platform's app store listing

The reader searches the official app store for the platform's brand token. The reader reads the publisher field on the app store listing; the publisher name should match the platform's published company name. The reader cross-checks the publisher name against the home page of the official site.

Source 2: the platform's published terms

The reader visits the official site's terms page. The reader reads the publisher's registered name and the registered office address. The reader cross-checks the registered name against the home page of the official site. The reader does not rely on the home page alone; the reader reads the terms page.

Source 3: the platform's published responsible-play tab

The reader visits the official site's responsible-play tab. The reader reads the responsible-play controls the platform publishes. The reader cross-checks the controls against the controls the desk publishes on the comparison shelf. Where the controls differ, the desk's source is the platform's own page, not the comparison shelf.

What the desk recommends

The desk recommends the reader verify the official site against at least two of the three sources above. The desk recommends the reader verify the official site before the reader registers on the platform. The desk recommends the reader verify the official site before the reader makes the first deposit.

What the desk does not recommend

The desk does not recommend relying on a single source for verification. The desk does not recommend clicking a paid search result without reading the URL. The desk does not recommend registering on a platform whose official site the reader cannot verify against two sources.

How the reader reports an impersonation

Where the reader finds an impersonation site, the reader reports the impersonation to CERT-In at the cybercrime.gov.in portal. The reader also reports the impersonation to the platform's abuse-reporting channel. The desk reads impersonation reports at the editorial email but does not act as the response channel.

How the desk handles an impersonation report

The desk reads impersonation reports sent to the editorial email. The desk does not host the reported site; the desk directs the reader to the CERT-In incident reporting portal and to the platform's own abuse-reporting channel. The desk publishes a note on the relevant comparison shelf where the impersonation is widespread.

How the desk handles a brand-token collision

Where two platforms share a brand token, the desk distinguishes them in the body copy and lists both in the comparison shelf. The desk does not endorse either platform; the desk reads the published terms and surfaces the difference for the reader.

How the desk handles a redirect chain

Some platforms redirect from a marketing URL to a regional URL. The desk lists both URLs in the comparison shelf. The desk does not follow the redirect for the reader; the reader verifies the final URL themselves.