This address looks like a backend endpoint on Microsoft's SharePoint infrastructure, not a site meant for visitors. But the SSL certificate it presented doesn't match — it was issued for a different domain (azureedge.net). That alone makes any connection untrustworthy, whether you're just checking the page or sending data. The server also returned an error (HTTP 400) and showed only a generic 'services unavailable' message. For a Microsoft-owned host, this is unusual and suggests misconfiguration or misuse. There are no 5017-ipv4v6e.clump.dprodmgd108.aa-rt.sharepoint.com reviews to consult because there's no actual business here. Before trusting any link that starts with this hostname, verify that the destination is what it claims to be. In this case, the lack of a valid certificate and working page means you should treat it as suspicious — not a legitimate service you can rely on.
No — 5017-ipv4v6e.clump.dprodmgd108.aa-rt.sharepoint.com doesn't look safe
In plain English
This isn't a real website you'd browse — it's a Microsoft subdomain with a broken SSL certificate. The connection can't be trusted, and the server isn't serving any usable content. Stay away; there's nothing here that's safe to interact with.
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 doesn't match the hostname — any communication with this server can't be verified. The site also fails to set basic browser protections.
Because this is a subdomain of Microsoft's sharepoint.com, ownership is effectively tied to a known company. The lack of a WHOIS record is normal for a subdomain.
No blacklist entries or Google Web Risk flags. The domain itself carries no negative reputation signals.
No contact or about pages exist, but this is expected for an infrastructure endpoint not meant for public browsing.
Missing privacy policy and terms are irrelevant here — this isn't a commercial site collecting user data.
DNS resolves to Microsoft's network, but the server returns an HTTP 400 error and the SSL handshake fails due to a certificate mismatch.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.