If you've come across r3.sn-hp57yne7.c.2mdn.net somewhere online, you might be wondering if it's safe. The short answer is that this isn't a normal website at all. It's a subdomain within Google's ad-serving infrastructure, and it appears broken. The SSL certificate doesn't match the address, and trying to visit it returns a 404 error. That doesn't mean it's a scam, but it does mean you shouldn't expect this URL to serve any legitimate content or handle any personal information. For infrastructure like this, missing legal pages and contact info are standard, but the invalid certificate and unreachable status are real red flags. Don't click links that point here or treat them as trustworthy destinations. The most likely explanation is a misconfigured server endpoint, not a phishing attempt, but either way it's not a site you need to interact with.
No — r3.sn-hp57yne7.c.2mdn.net doesn't look safe
In plain English
This URL is part of Google's ad-serving backbone, but it's not a functioning website you should interact with. The SSL certificate is invalid for this exact address, and the page simply returns a 404 error. There's no reason to trust this link for anything.
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 cover this specific subdomain, so any connection to it is not encrypted properly. That's a critical flaw, especially for a site that's part of Google's ad delivery network.
This is a subdomain owned by Google (2mdn.net). While WHOIS isn't visible for subdomains, the parent domain is well-known and trustworthy. No concerns about who runs it.
The site isn't on any blacklists and Google Web Risk sees no threats. But it has no Wayback Machine history or traffic rank, which is normal for a technical endpoint that isn't meant to be browsed by people.
As an infrastructure subdomain, missing contact info, about page, and social links are completely normal. No transparency expectations for a backend server.
Legal pages like privacy policies live at the parent domain level. For a subdomain used only for ad serving, the absence of its own legal docs is expected and fine.
DNS works and hosting is on Google's network, which is solid. But DNSSEC isn't enabled, there's no email handling, and security headers are minimal. Acceptable for a CDN endpoint, not great for anything else.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.