This address is a subdomain under googlevideo.com, which is owned by Google and used for video content delivery. But if you've landed on rr5.sn-5hne6nsk.googlevideo.com directly, there's nothing useful here. The SSL certificate doesn't match this hostname, the site is unreachable, and it returns a plain 404 error. This is not a consumer-facing website. It's a backend server that isn't configured correctly for direct access. There are no rr5.sn-5hne6nsk.googlevideo.com reviews or user accounts to check because there's no business behind it. A legitimate infrastructure endpoint should at least respond with a valid certificate. Because the security is broken and the server can't serve content, there's no reason to trust this URL for anything. Don't enter any data or attempt to interact with it.
No — rr5.sn-5hne6nsk.googlevideo.com doesn't look safe
In plain English
This is a Google infrastructure subdomain that isn't working properly. The SSL certificate doesn't match the address and the site returns a 404 error. There's nothing here for a consumer to use, so treat it as untrustworthy for any practical purpose.
What you should do now
Don't panic. These steps limit the damage, and the sooner you take them the better.
Don't enter any details
No passwords, card numbers or personal information — even if the site looks professional.
Close the tab
Especially if you got here from an email, text message or social media ad.
Already paid? Call your bank
Contact your bank or card provider right away. They can often stop or reverse a recent payment.
Warn others
Report the site and share this check with anyone who sent you the link.
Where the score comes from
The SSL certificate doesn't match this address, and the site can't be reached at all. For a backend server this is a critical failure, even if it's part of Google's network.
This subdomain belongs to Google's googlevideo.com. WHOIS shows no registration for the subdomain itself, but the parent domain is clearly owned by a major company. No identity concerns here.
No blacklist hits and no archive history, which is normal for a technical subdomain that isn't meant for public browsing.
There's no contact info or about page, but for an infrastructure subdomain that's not designed to be visited by consumers, this is expected.
No privacy policy or terms of service, which is standard for a backend server that doesn't collect user data directly.
The technical setup is basic: no email, no DNSSEC, but it's hosted on Google's own network. The invalid certificate is the main drawback.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.