When you land on rr3---sn-2aqu-jbtk.googlevideo.com, you get a plain 404 error page. That's because this isn't a website meant for visitors — it's a technical backend server used by Google's video infrastructure. The domain is part of googlevideo.com, which Google owns and operates worldwide. For a server like this, you wouldn't expect contact info, privacy policies, or social media links. The security checks pass: valid encryption, no blacklist entries, and no malware flags. If you're wondering whether rr3---sn-2aqu-jbtk.googlevideo.com is a scam, the answer is no — but there's also nothing here to use or buy. It's simply a dead end. Most infrastructure of this kind blocks crawlers and has no web presence, so the lack of archive history is normal. There's no reason to worry about this subdomain, and no action needed from you.
Yes — rr3---sn-2aqu-jbtk.googlevideo.com looks mostly safe
In plain English
This is not a real website but a Google Video CDN endpoint that returns a 404 error. There's no evidence of scams or malicious activity. You can safely ignore it — there's nothing here to interact with or trust.
Where the score comes from
Solid security setup: valid certificate from Google Trust Services, modern TLS 1.3, and clickjacking protection. No blacklist or threat detection. The only minor concern is legacy TLS support, not relevant to a backend server.
This is a subdomain of googlevideo.com, which is owned by Google. Even though WHOIS doesn't show a direct match for this specific hostname, the parent domain is well-established. For an infrastructure endpoint, identity is clear enough.
No blacklist issues and no threats from Google Web Risk. However, the site has no web archive history and is not ranked; that's typical for a non-public server. No negative signals, but also no positive track record.
Missing contact info and about page are expected for a backend CDN server. This is not a consumer-facing business, so the lack of transparency is normal. No social media presence is also expected.
No privacy policy or terms of service, but that's standard for infrastructure services not intended for direct public interaction. GDPR/compliance requirements don't apply to a 404 endpoint.
Hosted on a Philippine network (PLDT), which is unusual for Google but plausible for a local CDN node. DNS resolves correctly, but DNSSEC is not enabled and no MX records exist. The robots.txt blocking all crawlers is normal for a non-public 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 →