If you came across 193814-ipv4.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spov-0006.spov-msedge.net, you might wonder if it's safe. The short answer is that it's not really a website at all. This address is a deeply nested subdomain of Microsoft's sharepoint.com, likely a CDN edge node that's either misconfigured or temporarily offline. The SSL certificate is issued for a different hostname, so any browser will block the connection. The page returns a 400 error and a message that services aren't available. There's no business, no contact information, and no privacy policy because there's nothing to buy or sign up for. For a technical infrastructure node, all of this is unremarkable. But if you were expecting a functional site, you found a dead end. There's no evidence of malicious intent, but also nothing to trust. Treat it as a broken link and move on.
Not sure — double-check 193814-ipv4.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spov-0006.spov-msedge.net first
In plain English
This isn't a real website. It's a technical endpoint that appears to be down or misconfigured. There's no business behind it, no content to evaluate, and the SSL certificate doesn't match. You shouldn't treat this as a site you can use or trust for anything.
Where the score comes from
The SSL certificate is invalid for this hostname, which means any connection attempt fails. For a technical endpoint, this is a configuration error, not a deliberate attack, but it blocks any secure interaction.
This hostname is a subdomain of Microsoft's sharepoint.com, so the underlying domain is owned by a major corporation. The specific subdomain is not registered separately, which is expected for infrastructure nodes.
No blacklists or malware flags, but there's no web archive history or external trust signals. It's essentially a blank slate with no track record.
No contact info, about page, or social media presence, but that's completely normal for a backend CDN node. It's not intended to be a public-facing business.
No privacy policy or terms of service, which is expected for a non-commercial infrastructure endpoint. There's no consumer interaction to regulate.
DNS resolves to Microsoft IPs, but the site is unreachable due to a certificate mismatch, and it returns an HTTP 400 error. Basic security protections like browser headers are absent, but that's secondary to the core connectivity failure.
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 →