The domain 14636-ipv4v6e.clump.dprodmgd105.aa-rt.sharepoint.com is a subdomain under Microsoft's sharepoint.com, which on its own is a trusted brand. But this specific address isn't behaving like a typical Microsoft endpoint. The SSL certificate it uses was issued for a different domain (azureedge.net), so your browser will show a security warning if you try to visit. On top of that, the server returns a 400 status code and the site is unreachable. This combination is a classic sign of a misconfigured backend service, not a phishing page or a fake site. For anyone wondering 'is this a scam?', the answer is almost certainly no. But is it safe to use? Also no, because you can't establish a secure connection. If you came across this URL in a document or an email, treat it as a broken link and look for the correct address. Most legitimate infrastructure endpoints from Microsoft have valid certificates and actually load; this one lacks both.
Not sure — double-check 14636-ipv4v6e.clump.dprodmgd105.aa-rt.sharepoint.com first
In plain English
This looks like a broken Microsoft server, not a scam. The invalid SSL certificate and the 400 error mean the site simply isn't working. If you were pointed here, it's almost certainly a misconfiguration, and you shouldn't rely on this address for anything.
Where the score comes from
The SSL certificate is invalid, which means any connection to this site is unverifiable. While this looks like a configuration mistake rather than an attack, it makes the site unusable for anything secure.
This is a subdomain of sharepoint.com, a domain owned and operated by Microsoft. The parent company is well-known and transparent, so there is no mystery about who runs this endpoint.
The subdomain is not found on any blacklists or threat databases. However, it has no history in the Wayback Machine, which is unusual for a Microsoft endpoint and suggests it may be very new or rarely accessed.
There is no contact or about page, but for an infrastructure subdomain that isn't meant for public interaction, that's perfectly normal. No one expects a customer service line here.
No privacy policy or terms of service are needed for a backend endpoint. This is a non-commercial technical resource, so compliance obligations don't apply.
The domain resolves quickly to Microsoft's own network, but it returns a 400 error and lacks basic browser protections. For a service that's supposed to deliver content, this is a sign it's not working correctly.
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 →