INDEPENDENT RESEARCH

Evidence checked · commercial links labelled · 18+ · no winning or recovery promise

CASINOCHECKINDIA / भारतVIEW A CHECKED CASINO · 18+हिन्दी

Operator evidence file · India · 23 August 2026

Duel in India: Register, Domain and Payment Evidence Check

Duel in India: separate discovery signals from verified facts

AMBER VERDICT · local status open

No exact current India authorization was established for this specific entity/domain combination in the captured official sources.

This is an unresolved local-status finding, not proof that authorization does not exist; foreign authorization is jurisdiction-specific.
Compare a checked option · 18+
Published: 23 August 2026

Affgate was used only for discovery and priority. The verdict and findings come exclusively from the declared evidence sources.

Two records, one brand, and a licence label that does not match

A brand file starts to look unsettled the moment two documents describe the same company in two different ways, and that is exactly the position on record here. The current Anjouan register entry, read on 2026-08-23, binds licence ALSI-202411026-FI1 to Immortal Snail LLC and to the host duel.com, and shows validity running through 2026-11-03. A separate independent listing identifies the same legal entity behind the brand, but attaches a Curacao label to it. Both statements cannot be a current description of the licensing position at the same time, so the mismatch is disclosed here rather than smoothed away.

Table 1 — How the captured records describe the same brand (all read 2026-08-23)
FieldCurrent Anjouan register (IN-DU-001)Independent listings (IN-DU-002, IN-DU-003)
Legal entityImmortal Snail LLCImmortal Snail LLC
Licence referenceALSI-202411026-FI1Curacao label on IN-DU-002; conflicts with the register
Bound hostduel.comBrand-level identification only
Validity shownThrough 2026-11-03Not a validity source
Status in IndiaNot addressedNot addressed

What was established about India, and what was not

No exact current India authorization was established for this specific entity/domain combination in the captured official sources. That sentence is the whole of the local finding, and it should not be stretched in either direction. This is an unresolved local-status finding, not proof that authorization does not exist; foreign authorization is jurisdiction-specific.

The Indian reference point held in the ledger is MeitY's Promotion and Regulation of Online Gaming Act 2025 and notifications hub, preserved for this scope as the current Act and notification hub, with legal review required. It is a statutory and notification source, not a brand register, so it will not confirm or deny any single operator by name. Reading it tells you which central rules and notifications are live; it does not tell you where a particular offshore brand sits within them. Your own state position matters as well, which is covered in our state-level legal context notes and in the summary of the central 2026 online money games framework.

What a foreign licence can carry, and what it cannot

The Anjouan entry is a primary record from the issuing register, and it is worth reading in full rather than in summary. It supports three things: a named legal entity, a licence reference, and a bound domain, each as shown on the date of capture. It does not travel. An authorisation granted in one jurisdiction is an arrangement between that issuer and that licensee, and it creates no permission in India, no consumer remedy under Indian law and no supervisory relationship with any Indian authority.

Where a foreign record genuinely helps an Indian reader is identity. If a payment descriptor, an email footer or a corporate reference later mentions Immortal Snail LLC, the register gives you an independent place where that name already appears in connection with the brand. If a site that presents the same branding names a completely different company, that gap is the finding worth noting. The reasoning pattern is set out in our offshore licence evidence guide, and the reverse claim, where an offshore brand implies Indian permission, is handled in the no-India-licence claim check.

The domain question: duel.com is the host the register binds

Domain identity is the part of this file that is cleanest, so it is worth using. The register entry read on 2026-08-23 binds the licence reference to duel.com and to no other host. Anything else that carries the same colours and wordmark is unverified until the same register shows it: a hyphenated variant, an added country word, a different extension, a shortened link inside a message, or an APK offered outside an official store listing.

That single anchor is enough to run a practical check without trusting marketing material. Type the host yourself instead of following a forwarded link. Compare the string character by character, including the extension. Note that a valid certificate, a polished layout and a responsive chat window prove only that someone built a working website. Where an app is involved, the package name and the source of the installer matter more than the icon, which is the trap described in our fake gaming app and APK warning and in the wider notes on fake apps and phishing.

Reading the independent listings without upgrading them

Two independent listings sit in the ledger. Gamblers Connect identifies Immortal Snail LLC for the brand while carrying a Curacao label that conflicts with the current register, and Casinos.org supplies a second independent identification of the same brand-and-company relationship. Neither is a regulator, neither issues or withdraws a licence, and neither establishes authorisation in India. They are independent context that happens to agree on the corporate name, which is the one point where agreement is meaningful.

Used that way, they raise confidence in identity and leave the licensing question to the issuer's register. Used carelessly, the Curacao label becomes a second-hand fact that overrides a primary record, which is the specific error this file is built to avoid. Our methodology notes explain how source roles are separated before anything is written, and the same separation drives the India licence-check walkthrough.

Table 2 — Claim-by-claim support map for the captured ledger
Source IDRole and tierWhat it supportsWhat it does not support
IN-LAW-001Law, primaryThe current central Act and notification hub for online gaming in IndiaAny statement about one brand, domain or company
IN-DU-001Official regulator record, primaryImmortal Snail LLC, licence ALSI-202411026-FI1, duel.com, validity shown through 2026-11-03Indian permission, payment safety or service quality
IN-DU-002Reliable independent, independent tierIndependent identification of Immortal Snail LLC for the brand; a disclosed Curacao label mismatchThe current licensing jurisdiction, or Indian status
IN-DU-003Reliable independent, independent tierA second independent identification of the brand and company relationshipAuthorisation in India in any form

Payments: what an Indian money trail can actually prove

Because the local-status question stays open, the strongest records an Indian reader can create are their own payment records. A UPI or bank trail does not settle legality, and nothing in the ledger describes any deposit route, withdrawal timing or verification outcome for this brand. What a trail does prove is that a specific amount left a specific account at a specific time and reached a specific named beneficiary. That is the material every grievance channel asks for first, and it is the material that quietly disappears if you wait.

The beneficiary string is the field people overlook. When the name shown against a gaming payment is an unrelated firm, an individual, or a payment intermediary that does not match any company you were told about, that gap belongs in your file exactly as it appeared, without correction or paraphrase. Our guides on UPI merchant name mismatch evidence, UTR and withdrawal evidence and collect-request risk in gaming apps cover the capture steps in detail.

Table 3 — Payment fields worth capturing on the same day
Field to captureWhere it usually appearsWhy it matters later
UTR or RRNUPI app history, bank statement narrationUnique handle used by banks and complaint portals
Beneficiary or merchant name stringPayment confirmation screen, statement narrationShows who was actually paid, mismatch included
VPA or account identifierUPI transaction detail viewLinks the payment to a specific collection route
Exact timestampTransaction detail, device clock in screenshotAnchors a sequence rather than an impression
Requested and credited amountsStatement plus your own withdrawal noteSeparates a fee dispute from a non-payment dispute
Statement PDF for the full periodNet banking downloadKeeps context that isolated screenshots lose

An evidence-preservation checklist you can finish today

  1. Screenshot the register entry for licence ALSI-202411026-FI1 with the URL bar and system date visible, then save the page as PDF.
  2. Screenshot both independent listings the same way, so the Curacao label mismatch is preserved as you found it rather than as you remember it.
  3. Download the full bank or UPI statement for the period as a PDF, not as cropped images.
  4. Record every UTR or RRN in a plain text or spreadsheet file, one row per transaction, with amounts and timestamps.
  5. Copy the beneficiary and VPA strings character for character, including spacing and abbreviations.
  6. Note the exact host you typed and the exact host that finally loaded, along with any redirect you noticed.
  7. If an app is involved, record the package name and where the installer came from; do not reinstall over it first.
  8. Keep original files unedited in one dated folder, and work only on copies.
  9. Write a short dated timeline of what happened, marking clearly which entries are your own recollection.
  10. Store one backup outside the phone used for the transactions.

Continue via our tracked link

Where a complaint involving this brand can go in India

Routing matters more than volume, and the correct channel depends on what went wrong. Where money left an account through fraud or unauthorised use, the financial cyber-fraud route is time sensitive and should not wait for a support reply; the steps sit in our guide to 1930 and the National Cybercrime Reporting Portal and in the notes on unauthorised UPI gaming payments.

Where the failure is a regulated payment-system entity mishandling your grievance, the sequence starts with a written complaint to the bank or provider and escalates through the RBI CMS complaint route. Where the dispute is service-related rather than criminal, the boundary is explained in consumer complaint versus cybercrime. A suspicious website itself can be raised through the suspect gaming website check, and general routing is collected on our report and complain hub. If play has stopped being a choice, stop play and get help lists Indian support options.

Dated source ledger for this file

Every row below was read on 2026-08-23 and is stored with its role and tier, because the role decides how much weight a row can carry. Nothing else was used, and nothing was inferred to fill a gap.

Table 4 — Sources, roles and capture dates
Source IDSourceRoleTierChecked on
IN-LAW-001MeitY Act and notification hubLawPrimary2026-08-23
IN-DU-001Anjouan licence register entryOfficial regulatorPrimary2026-08-23
IN-DU-002Gamblers Connect brand listingReliable independentIndependent2026-08-23
IN-DU-003Casinos.org brand listingReliable independentIndependent2026-08-23

What would move this finding away from amber

The signal here is amber on open evidence, and it is honest about why. A green reading would need current primary evidence attaching Indian authorisation to this precise entity and domain pairing, which the captured sources do not contain. A red reading would need an official adverse record, or corroborated documented evidence of harm, and neither exists in the ledger. Absence of a captured local match is not proof that no permission exists anywhere.

Three developments would change the file. First, a primary Indian record naming the entity or the bound host, which would settle the local question in one direction or the other. Second, a fresh reading of the issuer's register after 2026-11-03, since a validity date shown today says nothing about renewal. Third, resolution of the jurisdiction label, either by an updated independent listing or by a register change. Until then, treat the position as open, keep your own records intact, and see the operator research backlog for what is queued next.

Frequently asked questions

Is Duel legal in India?

No exact current India authorization was established for this specific entity/domain combination in the captured official sources. This is an unresolved local-status finding, not proof that authorization does not exist; foreign authorization is jurisdiction-specific. The Anjouan licence recorded for Immortal Snail LLC speaks to identity and to that issuer's own register, never to Indian permission, and MeitY's Act and notification hub remains the central reference point that needs legal review for your own state and circumstances.

Which Duel domain is genuine?

The current Anjouan register entry binds licence ALSI-202411026-FI1 to duel.com, so that host is the only one supported by a primary record read on 2026-08-23. A look-alike spelling, an extra word, a different extension, a forwarded short link or an APK from outside an official store listing stays unverified until the same register shows it. A chat agent's assurance or an advertisement is not a substitute for the register entry.

How do I preserve UPI evidence for Duel?

Capture the payment record on the same day: download the full statement as a PDF, note every UTR or RRN, and copy the beneficiary name and VPA strings exactly as displayed, mismatches included. Screenshot each transaction detail with the timestamp visible, keep the originals unedited in one dated folder, and work on copies. Add a short timeline of what happened and mark clearly which parts are recollection rather than record.

Where can I report a problem involving Duel?

For money lost through fraud or unauthorised use, the financial cyber-fraud route via 1930 and the National Cybercrime Reporting Portal is time sensitive and should not wait for an operator reply. For a payment-system grievance, complain in writing to the bank or provider first, then escalate through the RBI complaint management route. Service disputes may belong to the consumer route instead, and a suspicious site itself can be reported separately.

Does validity shown through 2026-11-03 mean anything for an Indian reader?

It means the register entry was live when read on 2026-08-23 and displayed that end date, nothing more. A validity date is an issuer's own administrative marker; it can change earlier through suspension or surrender, and renewal is never automatic. It also carries no Indian effect at all. Re-read the register entry before relying on it, and treat any date you did not see yourself as unchecked.

Dated source captures

Anjouan register - Duel
Verified source capture · anjouangaming.com · 2026-08-23 · IN-DU-001
Gamblers Connect - Duel
Verified source capture · gamblersconnect.com · 2026-08-23 · IN-DU-002