1. An exact domain match
Input: https://spinow.com/. Parsed hostname: spinow.com. Result: listed. This matches the published brand-owner directory. It does not prove that a specific offer, page or transaction is valid. The current site is an information resource, not a player-account service.
2. A familiar name inside another domain
Input: https://spinow.com.example.invalid/login. Parsed hostname: spinow.com.example.invalid. Result: unlisted. Read the entire hostname: putting a familiar name at the left does not make the destination spinow.com. The words after a slash are a path, but the words before the first slash following https:// are part of the authority to inspect.
3. The @ sign changes what you are reading
Input: https://spinow.com@example.invalid/login. Parsed hostname: example.invalid. Result: warning. The text before @ is user information, not the destination. Our checker warns about this construction even if the hostname after @ happens to be on the list. Do not enter credentials into a page merely because a brand name appears somewhere in its URL.
4. A plausible subdomain is not a confirmed service
Input: https://login.spinow.com/. Parsed hostname: login.spinow.com. Result: unlisted. The directory deliberately uses exact matches. It does not confirm every conceivable subdomain. This example does not say that the subdomain exists or belongs to an attacker; it says that this resource has not listed it as an available service.
5. A tracking parameter does not change the hostname
Input: https://spinow.com/?source=example. Parsed hostname: spinow.com. Result: listed. The checker ignores the path, query and fragment when comparing identity. It does not examine where a redirect parameter might lead. Inspect the address again after opening a real link. Never paste password-reset tokens or other private URLs.
6. HTTP and unusual ports need separate attention
Input: http://spinow.com/. The hostname matches, but the checker notes that the submitted address is not HTTPS. A match does not mean the connection is encrypted. Input: https://spinow.com:8443/. The non-standard port causes a warning because the domain directory does not approve arbitrary services on that host. Do not override a browser certificate warning.
Make the check reproducible
Use the checker with these public examples, compare the displayed hostname, then clear the input. No network request is made to the submitted destination. For a real claim, separately record the source page, what it says, the date and the evidence supporting it. A hostname check and an offer check answer different questions.
Keep these checks in mind
- Read the parsed hostname, not a link label.
- Treat a directory match as a limited identity check.
- Do not treat unlisted as a finding of fraud.
- Check the final address after redirects.
- Keep private links and credentials out of examples.