A checked link only confirms a specific destination check at a specific time. It does not establish licensing, safety, solvency or guaranteed payment.
HOW THIS PAGE WORKS
What does link verification actually check?
Link verification means checking the displayed destination domain, following any redirect the link makes, and noting whether the final page loaded over HTTPS on a specific date. It is a technical snapshot, not a safety guarantee, and every row below reflects one dated check.
The three-step check we repeat for every brand
We open the promotional link as published and let it fully load in a browser first. Next we write down the domain shown in the address bar once any redirect settles. Then we note whether that final page loaded over HTTPS. Nothing more is claimed than that.
Why we log a specific date for each record
A domain that loaded correctly last month can be swapped, taken offline, or pointed somewhere new today. Dating each record tells you how old the check is, so you can judge how much weight to give it. Older dates deserve more caution, not less.
SHORT LINKS AND REDIRECTS
Why isn’t the link you click always where you land?
A promotional link can pass through a shortener, a tracking redirect, and a rotating domain before it ever shows you a casino page. Each hop can change where you actually end up, sometimes on the same day the link was shared.
Short links, tracking redirects and rotating domains
Operators often use link-shortening tools so a promo code fits on a poster or a chat message. That shortened link points to a tracking redirect, which then forwards you to whichever domain is active that week. The domain you see first is rarely the one you land on.
A worked example: three hops to the real domain
Picture a shared link reading “heylink.me/promo123”. Clicking it forwards you to a tracking page, which forwards you again to a domain ending in “.vip” instead of the “.com” you expected. We've found that pausing after each hop, rather than clicking through on autopilot, is the only reliable way to catch this. That's exactly why the address bar matters more than the original link text.
i
What “verified” means here
We record the displayed domain, inspect redirects and note whether a destination responded over HTTPS. Each result is time-specific and limited to that technical check.
Reading the table above? See how each column is built and what it does and doesn't tell you in the sections below. ↓
READING THE TABLE
How do you read the columns in the table above?
Each column in the table records one narrow fact: the domain shown after redirects, a short note on what was logged, whether HTTPS responded, and the month of the check. None of the columns rate the operator itself.
Displayed destination and link note
“Displayed destination” is the domain that appeared in the address bar once the link finished loading, not the domain that was originally shared. “Link note” is a short label describing what our check actually recorded, such as “displayed domain logged”, so you know the scope of that row.
HTTPS column and asset date column
“HTTPS” shows whether the destination responded over an encrypted connection at check time, or whether that check still needs to be completed. “Asset date” is the month we last confirmed the domain, and it's the single most important column for judging how current a row is.
Method
What it captures
What it misses
Domain-only check
Records the domain shown at first click, before any redirect.
Misses later redirects and rotating domains entirely.
Redirect-chain check
Follows every hop to the final destination domain.
Still says nothing about the operator behind that domain.
HTTPS-only check
Confirms the connection to the final page is encrypted.
Does not confirm licensing, ownership or fund safety.
Our method (domain + redirect + HTTPS, dated)
Combines all three checks with a logged date for context.
Still a technical snapshot, not an operator safety review.
HTTPS AND CERTIFICATES
What does a valid HTTPS connection actually tell you?
A valid HTTPS connection tells you the data moving between your browser and that specific page is encrypted in transit. It does not tell you who runs the site, whether it's licensed, or whether it will pay out.
What HTTPS confirms
HTTPS confirms the page presented a valid certificate for its own domain and that the connection is encrypted. That reduces the chance of someone quietly intercepting the data you send on that page, such as a login form.
What HTTPS does not confirm
HTTPS does not confirm the operator holds a gaming licence, that funds are held safely, or that withdrawals will be processed. A scam page can carry a valid certificate just as easily as a legitimate one. Treat the padlock as a baseline, not an endorsement.
LIMITATIONS
What does this verification not prove?
Confirming a domain and its HTTPS status is not the same as confirming the operator is legitimate, licensed, or safe to use. This check has clear limits, and we want those limits to be obvious rather than implied.
Licensing and legal status
Our check does not confirm whether an operator holds a gaming licence in any jurisdiction, or whether offering that service is legal where you're located. Licensing and legal status sit entirely outside what a domain and HTTPS check can show.
Fund safety, payout reliability and current offer terms
A checked domain says nothing about whether deposited funds are held safely, whether withdrawals are processed reliably, or whether a promotional offer's terms are still current. Offer terms can change after we log a row, so always confirm current terms directly on the operator's own page before relying on them.
REPORTING CHANGES
How do you report a broken or changed link?
If a link in the table above no longer matches what you see, or the destination domain has changed, tell us through the contact page. Reports help keep the asset dates meaningful for other readers.
What to include in a report
A useful report names the brand row you're looking at, the domain you actually landed on, and roughly when you noticed the change. A screenshot of the address bar helps us confirm it quickly.
What we ask you never to send
Never include passwords, one-time codes, ID documents, or any account credentials in a report. We only need the link details and domain, never your personal account information.
RECHECK CADENCE
How often is this table rechecked?
Asset dates in the table span several recent months rather than sharing one fixed date, which reflects a rolling recheck process instead of a single yearly refresh. Rows get rechecked on an ongoing basis, not all at once.
Our recheck cadence
Rather than promising a fixed interval for every single brand, we work through the list on a rolling basis and update the asset date whenever a row is reconfirmed. The spread of dates you see in the table reflects that rolling process directly.
What happens when a domain changes
When a displayed destination changes, we update the row with the new domain, refresh the HTTPS status, and reset the asset date. If a link stops resolving altogether, the row should be treated as unconfirmed until it's rechecked.
REDIRECT SAFETY
Pause at every handoff.
Short links can hide the final domain and can be changed after publication.
Before entering personal information
Let the destination fully load and read the address bar.
Check spelling, HTTPS and whether the operator identity is disclosed.
Do not trust a padlock as proof of operator legitimacy.
Leave if the page asks you to install an unknown application or profile.
EDITORIAL DEEP DIVE
Link verification is a technical snapshot
A link can resolve correctly today and change tomorrow. Verification should record the displayed URL, redirect chain, final domain, HTTPS response and exact check time.
Display versus destination
Link hubs and shorteners can conceal the operator domain. Pause after every redirect and inspect spelling before entering account or payment data.
What HTTPS proves
Encryption helps protect the connection. It does not prove licence, ownership, fair terms, solvency or willingness to pay.
Report a change
Send the directory page, displayed link, final domain, timestamp and screenshot. Never send passwords, OTPs or identity documents with a report.
