r3.sn-a5mlrnls.c.2mdn.net isn't a website in the usual sense. It's a subdomain of Google's 2mdn.net ad-serving infrastructure, but it's not working properly. The HTTPS certificate is invalid for this address, and the server throws a 404 error on every request. That means there's nothing to see or use. For a Google-owned endpoint, the lack of a valid certificate is unusual and points to a misconfigured or retired server. There's no phishing or malware flagged, but that's because the site simply doesn't deliver any content. If you've encountered this URL in an ad or redirect, it's likely a broken link. Don't expect any functionality, and don't enter any personal information on a 404 page. The domain itself is reputable, but this specific subdomain isn't a working service. There are no r3.sn-a5mlrnls.c.2mdn.net reviews because there's nothing to review. Treat it as dead infrastructure and move on.
No — r3.sn-a5mlrnls.c.2mdn.net doesn't look safe
In plain English
This site is not functional and shouldn't be used. The SSL certificate doesn't match the address, so your connection can't be verified, and the server returns nothing but a 404 error. It's a broken piece of infrastructure, not a place to visit intentionally.
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 is invalid for this hostname, and the site is unreachable over HTTPS. That's a fundamental failure for any server meant to be accessed securely.
This is a subdomain of the Google-owned 2mdn.net, so the operator is known even though the specific subdomain isn't registered independently. That's normal for infrastructure like this.
Clean on blacklists and Google Web Risk, but the site has no history in the Wayback Machine and no traffic ranking. It appears to be a very low-profile or broken endpoint.
No contact info, about page, or social presence exists, but this is an ad-server subdomain, not a consumer-facing business. Transparent communication isn't expected here.
No privacy policy or terms of service, which is fine for a non-commercial technical server. There's no content or data collection to regulate.
DNS resolves to Google IPs, and the page loads quickly for a 404 error. But missing DNSSEC and email records are minor for a static endpoint.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.