If you've landed on this long Microsoft subdomain, you're probably not looking at a typical website. It's part of Microsoft's Azure and SharePoint CDN infrastructure, and right now it's broken. The SSL certificate doesn't match the hostname, so your browser won't let you connect securely. The page itself returns an error saying services aren't available. For infrastructure like this, the lack of contact info or legal pages is normal, but the invalid certificate is a real problem. If you're wondering is 194189-ipv4v6.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net fake? No, it's genuine Microsoft infrastructure. But is 194189-ipv4v6.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net safe to use? No—it fails the most basic security check. Avoid accessing this URL until the certificate issue is fixed.
Not sure — double-check 194189-ipv4v6.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net first
In plain English
This site isn't a scam, but it's not functioning as a trustworthy service either. It's a Microsoft infrastructure endpoint with an invalid SSL certificate and can't be reached. You have no reason to trust it with any data or traffic.
Where the score comes from
The SSL certificate is invalid and the site is unreachable due to a TLS handshake failure. That's a critical red flag, regardless of what the site claims to be.
This is a subdomain of sharepoint.com, which is owned by Microsoft, so the parent organization is clear. But the specific hostname isn't a registered domain, and there's no indication of who manages it.
No blacklist entries and no web history at all. It's essentially a blank slate, which for a Microsoft infrastructure endpoint isn't suspicious but doesn't build confidence either.
No contact info, about page, or social links. That's normal for a technical endpoint that isn't meant to be a public-facing business.
No privacy policy or terms of service. Since this is not a commercial site and doesn't collect user data, this is acceptable.
DNS resolves to Microsoft IPs quickly, and the host is on Microsoft's network. The lack of common security headers is normal for a CDN edge node.
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 →