Rank #50 · Operator profile
Fano.bet
Spinorhino-licensee sister returning HTTP 403 Forbidden from our test location.
- Licence
- Anjouan
- Test access
- HTTP 403 (Forbidden)
- Licence
- Anjouan
- Licence no.
- ALSI-202509069-FI2
- Licensee
- 3-102-937541 SRL
- Domain
- fano.bet
- KYC threshold
- Not visible from our test location
- Licence expires
- September 29, 2026
Fano.bet is one of eight consumer brands listed under Costa Rican entity 3-102-937541 SRL on Anjouan licence ALSI-202509069-FI2, the same licence as Spinorhino, Baloo, Dragobet, Betoranje, and the other listed sisters1 . The domain returned HTTP 403 (Forbidden) from our test location at time of writing. The licence remains valid. This is a profile, not a tested review.
The HTTP 403 pattern across Spinorhino sisters
Four of the eight Spinorhino-licensee sisters returned HTTP 403 from our test location at time of writing: Fano.bet, Holyluck.com, Likes.bet, and Honeymoney’s adjacent pattern on the Fenix licensee. This is enough of a cluster to flag as an operator-side observation. The 403 may be:
- A WAF or bot-protection layer that screens automated traffic
- An application-layer geo-block configured at the operator’s CDN
- A server-config policy denying unauthenticated GET requests from non-target IP classes
Whichever the cause, it means the player surface is not externally readable from automated tooling. A real player connecting from the operator’s target IP class (which we have not identified) may see the lobby normally.
The .bet TLD signal
The .bet TLD is sports-betting-coded and most commonly used by operators with a sportsbook product or a sports-themed brand positioning. Fano.bet shares this TLD with two other Spinorhino sisters (likes.bet and zumo.bet), suggesting the eight-brand stable contains a sports-betting-coded sub-cluster distinct from the casino-coded brands (baloo.bet, holyluck.com).
For prospective players, the TLD signal alone is not informative about product mix; many .bet operators are casino-first with the TLD chosen for branding or domain availability rather than product alignment.
What we cannot verify
With a 403 response, no operator-published facts (cashier, T&Cs, bonus surface, language) are externally observable from our test location.
The licensee structure
3-102-937541 SRL operates the largest brand-stable in the Anjouan register at time of writing: eight consumer brands across mixed TLDs (.com, .bet) and mixed brand-language signals. The HTTP-403 sub-cluster (Fano, Holyluck, Likes) suggests a shared defensive posture across part of the stable rather than per-brand variation.
What the Anjouan licence actually covers
Fano.bet is licensed by the Anjouan Gaming Authority,
the regulatory body established on the autonomous island of Anjouan
(one of the three islands that make up the Union of the Comoros in
the Indian Ocean). Anjouan's modern iGaming licensing framework was
relaunched in 2023–2024 by Anjouan Licensing Services Inc., the
exclusive licence administrator, and has been adopted at scale since
by operators that previously sat under Curaçao's old master-licence
system.
The operator's licence number is ALSI-202509069-FI2, listed as valid on the
official Anjouan licence register.
What the licence does
- Operator vetting at issue. The framework requires KYC on beneficial owners and directors, clean criminal-record checks, source-of-funds documentation, a written business plan, and AML/KYC/responsible-gaming policies before the licence is issued.
- Game-software certification. Operators must use certified RNG technology, with provider certificates submitted as part of the licensing pack.
- Segregated player funds. Operators must hold player balances in accounts separate from operating funds. This is the single most consequential player-protection clause in the framework.
- Formal complaint process. Operators must publish a complaint-handling procedure and respond to player disputes within the timeframes defined by the regulator.
- Public register and seal verification. Every licensed operator appears on the official register with licence number, issue and expiry dates, status, and authorised domains. Operators may display a seal whose ID resolves to the register entry in real time.
What the licence does not do
- No binding third-party adjudication. Anjouan provides a formal complaint process between player and operator, but it does not offer the binding ADR (alternative dispute resolution) tier that regulators like the UKGC or MGA mandate. If the operator refuses to pay, the regulator can revoke the licence — but does not order the operator to pay the player.
- No deposit caps or central self-exclusion. Unlike MGA, UKGC, KSA, or Sweden's Spelpaus, Anjouan does not run a cross-operator self-exclusion register or impose mandatory deposit limits. Self-exclusion is a per-operator setting; players who want cross-operator protection have to rely on GamStop / Cruks / Spelpaus where applicable.
- Disputes from excluded territories are not mediated. The Anjouan Gaming Board explicitly excludes mediation for players based in jurisdictions the operator was supposed to block. If you played from a restricted country, the regulator will decline the case.
- No public dispute decisions database. There is no published archive of operator complaints and rulings comparable to the UKGC's enforcement-action page or the MGA's player-complaint summaries. Track-record information has to be reconstructed from third-party sources (Trustpilot, AskGamblers, casino-forum threads).
- Limited recourse outside the licence. Anjouan's jurisdiction is the autonomous island, not the Comorian Union. Comorian union-level law treats most gambling as prohibited, which creates a structural mismatch: the licence is real and the regulator acts, but it operates entirely within the island's autonomy carve-out.
How this compares to other offshore licences
Anjouan sits in the same operational tier as the new Curaçao LOK framework (issued directly by the CGB since 2024, replacing the old master/sub-licence system) and Tobique (Canadian First Nation regulator that took over from Kahnawake for many crypto operators). All three offer real but light-touch licensing: operator vetting at issue, mandated segregated funds, formal complaint handling, no binding third-party arbitration, and minimal ongoing player-protection infrastructure compared to MGA, UKGC, or KSA.
In practical terms: an Anjouan licence means the operator has been vetted by a regulator that exists, will respond, and can revoke. It does not mean a player will be made whole by the regulator if the operator decides not to pay. Players who want that should play at UKGC, MGA, or comparable-tier operators, accepting the friction (KYC at every turn, withdrawal holds, deposit limits) that comes with that protection.
Our analytical position
Fano.bet is a Spinorhino-licensee sister that returned HTTP 403 from our test location. The licence is current. The 403 is consistent with an operator-side defensive posture rather than a jurisdictional refusal (which would surface as HTTP 451). Score reflects: same-licence Anjouan baseline (neutral), restrictive external response (mild negative for evaluability), eight-brand-stable portability concern (mild negative).
Score: 5.2 / 10.
Frequently asked questions
Why did Fano.bet return HTTP 403?
HTTP 403 (Forbidden) is the server refusing the request without surfacing a jurisdictional (451) or credential (401) reason. This is consistent with a bot-protection layer, an application-layer geo-policy, or a server configuration. Three other Spinorhino-licensee sisters returned the same response.
Is Fano.bet the same operator as Spinorhino?
Same Anjouan licensee, different consumer brand. Both share licence ALSI-202509069-FI2 under 3-102-937541 SRL.
Does the .bet TLD mean Fano is a sportsbook?
The .bet TLD is sports-betting-coded but many operators choose it for branding rather than product alignment. We cannot verify product mix from a 403 response.
If I see a 403 when I visit Fano.bet, what does it mean?
It means the server is refusing your request. The cause could be bot-protection, a geo-policy, or a network-level block. Try from a different connection if you suspect VPN filtering; otherwise treat the brand as unreachable and consider the sister brands.
When this might not apply to you
We cannot verify operator-side facts from a 403 response. The Anjouan framework does not include cross-operator self-exclusion.
What to read next
- The Spinorhino profile for the front brand on the same licence.
- The Betoranje profile for a sister brand that did return content.
- The Honeymoney profile for another HTTP 403 precedent on a different Anjouan licensee.
References
- Anjouan licence register entry (3-102-937541 SRL) , Anjouan Gaming Authority