Observed
Visible in the site, source files or links at the check date. This is the strongest basis for describing the .live project itself.
A plain-language summary of what gobet365.live publishes, what remains unresolved, and where to find the detailed access, mobile, domain, product and trust guides.
The checked pages use gobet365.live as the canonical public hostname. Its homepage contains Sports and In-Play navigation, Multi Markets, account-access controls and a grid of casino/game labels.
The public .live files checked do not name a legal operating company, gambling regulator or license number. They also do not establish that similarly named domains are controlled by the same operator. Those questions are kept separate from what can be observed directly on the site.
| Topic | Status | What the evidence supports |
|---|---|---|
| Canonical hostname | OBSERVED | The checked pages use https://gobet365.live/ as the canonical site URL. |
| Public navigation | OBSERVED | Sports, In-Play, Multi Markets, account controls and casino/game tiles are present in the .live interface. |
| Account access | OBSERVED | The checked account route redirects away from the public .live pages; no credential form is embedded in those pages. |
| Mobile files | OBSERVED | The .live project contains responsive/mobile assets. It contains no APK, app-store URL, web-app manifest or service worker. |
| Other Gobet365 domains | MIXED | .me, .net, .org, .biz and .com have separate direct, external or historical records. Common ownership with .live has not been established. |
| Legal operator & license | NOT IDENTIFIED | No legal entity, registration number, gambling regulator or license number is identified in the checked .live sources. |
| Payments & bonuses | NOT PUBLISHED | Complete payment methods, withdrawal terms, fees, limits, bonus amounts and wagering conditions are not published for .live. |
| KYC & identity verification | NOT PUBLISHED | No complete KYC policy, document list, verification timetable or named identity-verification provider was found for the .live project. |
| Privacy & data handling | NOT PUBLISHED | No complete privacy notice, data-controller identity, retention schedule or privacy contact is published in the .live files. |
Visible in the site, source files or links at the check date. This is the strongest basis for describing the .live project itself.
WHOIS records, search-index material, regulatory lists, scans and older third-party records. These can document a date or domain without proving today's ownership or operating status.
The available sources are not strong enough to support the claim. Name similarity, server location or a software identifier is not treated as proof.
The following details should remain unresolved until stronger primary evidence is available:
.live, .me, .net, .org, .biz, .com and .info are controlled by one operator.These gaps should not be filled with data from Bet365, unrelated GoBet brands, old user-uploaded documents or similarly named domains unless a reliable source directly connects that information to the claim.
How the .live access route behaves, what happens after the click and what to check before entering credentials.
Mobile-browser access, the status of app/APK claims and why an m. query does not by itself establish an official mobile hostname.
Android artwork, the absence of an APK in the .live project, and what the separate .me web-app manifest actually proves.
A separate evidence map for .live, .info, .org, .net, .me and other similarly named addresses.
The sports sections, controls and casino/game labels visible in the public interface.
Which payment details are identified for .live, what remains unknown, and what to check before funding or withdrawing.
Identity-check status, missing document rules and safer steps before uploading personal information after account access.
Current offer status, missing wagering terms and what to verify before using a promotion.
Language, hosting and regulatory signals by region, plus why technical access does not prove legal or account eligibility.
What contractual topics are published for .live, what remains incomplete, and what to verify before account use.
What contact channels are visible on .live, which placeholders are not verified, and how to handle common account-support issues safely.
Dated domain and technical observations kept separate from present-day ownership or product claims.
General safer-gambling information and independent help resources, separate from operator claims that have not been verified.
Present-tense statements are checked against the relevant site or project files and dated when practical. Older search records, WHOIS entries, scans and third-party pages are kept as historical context rather than used to overwrite a newer direct observation.
The evidence also has to match the claim. A domain registration date is not a brand launch date; a link between two sites is not proof of common ownership; a server country is not proof of a licensed market; and a chat-software license is not a gambling license.
When stronger primary evidence becomes available, the relevant guide should be updated and the previous observation kept as dated history where it remains useful.