When you look at 192070-ipv4mte.farm.dprodmgd105.aa-rt.sharepoint.com, the first thing that stands out is that it's technically part of Microsoft's infrastructure but the subdomain itself is a mess. The SSL certificate doesn't match the domain, so any connection attempt fails. That's a dealbreaker for trust. The site returns an error page saying services aren't available, and there's no contact info or legal pages. For an infrastructure endpoint, you'd expect either a fully working service or a clear indication that it's internal. Right now, it acts like a misconfigured resource that accidentally became reachable. There are no malware flags or blacklist hits, but the invalid certificate alone means you shouldn't try to access it. If you're wondering whether 192070-ipv4mte.farm.dprodmgd105.aa-rt.sharepoint.com is a scam, there's no evidence of malicious intent – just poor configuration. But until the certificate is fixed, it's not safe to use in any capacity.
No — 192070-ipv4mte.farm.dprodmgd105.aa-rt.sharepoint.com doesn't look safe
In plain English
This site is not currently working and has a broken security certificate. It looks like an internal Microsoft test endpoint that leaked public exposure, not something you should use or trust. My advice is to steer clear.
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 and the site can't be reached securely. That's a hard stop for any legitimate service, even a test endpoint.
This is a subdomain under microsoft.com, so the parent organization is known, but the specific subdomain has no public ownership details. That's not unusual for internal resources.
No blacklists or threat flags, which is good. But there's no web archive history to confirm past behavior, so the reputation is neutral at best.
No contact info, about page, or social presence. For a service aimed at end users, that would be a big red flag; here it suggests the site isn't meant for public interaction.
No privacy policy or terms, but that's normal for backend infrastructure that doesn't collect user data. The parent Microsoft handles compliance at a higher level.
DNS works and the page loads fast, but there are no security headers or DNSSEC. It's a minimal setup, consistent with a test or internal service.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.