A website address contains more information than its brand word. When checking whether a hostname appears in a regulator’s published record, compare the full address rather than relying on a page title, logo or search snippet.
First separate hostname from the rest of a URL. In a URL such as https://m.example.test/path?ref=abc, the hostname is m.example.test; the protocol, path and query parameter are not domain entries. Record the hostname exactly as the browser shows it. If clicking the link changes the address, record both the hostname entered and the final destination. A listed starting address does not automatically establish that a different destination is covered.
Now compare the hostname with the complete printed string. www.example.test, example.test, mobile.example.test and example.test.ph are different hostnames. A regulator may list several variants, but a reader should not invent one absent from the source. Similar spelling is also not identity: extra hyphens, substituted letters and unrelated suffixes can make a lookalike appear convincing.
The PAGCOR snapshots accessed on 11 November 2026 illustrate the point. They are dated as of 29 October 2026 and print specific domain entries by row. For example, the printed www.okbet.com entry should not silently be treated as evidence for bare okbet.com. This is a statement about the scope of the printed record, not a conclusion that the bare hostname is necessarily unauthorized.
Create a small comparison table with browser hostname, exact source entry, list title and date, match result, and unresolved difference. Use “exact match” only when the strings match. If a hostname is missing, uses another suffix or redirects elsewhere, describe that difference rather than rounding it into a match.
For a concrete hostname exercise, compare www.example.test with www.example.test.attacker.test. The latter belongs beneath attacker.test; a familiar brand string at the beginning does not change that. Inspect the hostname as a whole, not merely its first word. Paths can also contain brand names without identifying the organization responsible for the site.
Exact matching is not a complete security or legal assessment. A hostname can be listed in an old snapshot and later change; a page can be compromised; an app file can come from an untrusted mirror; and a third-party publisher may lack permission even when an operator is listed. Those questions require separate evidence.
For safer navigation, reach a source independently rather than following an unexpected message link, inspect the final hostname before entering information, and avoid credentials on a page whose identity cannot be established. Encryption alone shows a protected connection to that hostname, not that the organization is authentic.
Finally, write down the date. A source marked “as of” a particular day is a snapshot, not a promise about tomorrow. If the question concerns a later date, seek the current official record or confirmation from the relevant authority. Exact-domain matching makes uncertainty precise enough to investigate instead of hiding it behind a familiar logo.