The domain rr2---sn-cxnuxa-hxm6.googlevideo.com looks like a random string, but it's actually a subdomain of googlevideo.com, which is owned by Google and used for serving YouTube video content. This isn't a website you visit in a browser — it's a backend server that delivers video streams. That explains why the root URL returns a 404 error and why there's no about page, contact info, or privacy policy. Those things don't apply to a server. The security setup is strong: the connection uses modern encryption, and the certificate is issued by Google's own certificate authority. One blacklist flagged this server, but that's not uncommon for IPs in large content delivery networks and doesn't indicate a real threat. If you see this domain in your browser's address bar or in a video player, it's just a Google server doing its job. There's no scam risk here — it's infrastructure, not a storefront.
Yes — rr2---sn-cxnuxa-hxm6.googlevideo.com looks safe
In plain English
This is a Google video server, not a consumer website. It's part of YouTube's infrastructure and is perfectly safe to connect to. The warnings about missing pages and contact info are irrelevant for a backend server, and the single blacklist listing is likely a false positive.
Where the score comes from
Strong encryption with TLS 1.3 and a valid certificate from Google Trust Services. The server still accepts outdated TLS 1.0/1.1, which is a minor legacy concern but not a practical risk for a Google infrastructure server.
This is a subdomain of googlevideo.com, wholly owned by Google. The lack of WHOIS records for the subdomain is normal and expected for a large company's CDN infrastructure.
Listed on one DNS blacklist (Barracuda), which is unusual for a Google server but may be a false positive or related to past abuse. No web archive history because the server is not a public-facing website.
No contact page, about page, or social media presence, but that's completely normal for a backend video server. The server isn't trying to present itself as a business.
Missing privacy policy and terms of service, but these are not required for a non-commercial infrastructure endpoint. Google handles compliance at the parent domain level.
Solid DNS setup with two IPs, fast load time, and proper security headers for clickjacking protection. No email handling or DNSSEC, which is typical for a CDN server.
What we checked
Run this site? Show your score.
Add a trust badge so visitors can see your live score for themselves.
Get your badge →