This URL is a subdomain under sharepoint.com, meaning it's part of Microsoft's own infrastructure. That alone rules out any typical scam operation, but it doesn't mean the site is ready for use. The SSL certificate is misconfigured, which prevents a secure connection, and the server returns a 400 error with a message that services are unavailable. For a consumer trying to access a SharePoint resource, this is a clear sign that the endpoint is either temporary, misconfigured, or retired. A legitimate Microsoft service should have a valid certificate and respond normally. There's no evidence of malware or blacklisting, but the broken state means you shouldn't attempt to use it. If you expected to find a working SharePoint site here, contact your IT administrator or Microsoft support instead. The domain itself is fine, but this specific path is not functional.
Not sure — double-check 188923-ipv4v6e.farm.dprodmgd104.aa-rt.sharepoint.com first
In plain English
This is a Microsoft SharePoint infrastructure endpoint that isn't currently working. It's not a scam, but the broken SSL certificate and unreachable status mean you shouldn't rely on it for anything. Treat it as a dead link until Microsoft fixes the configuration.
Where the score comes from
The SSL certificate is invalid for this hostname, which is a critical failure for any service that needs to be reached securely. Combined with the unreachable status, this is a serious red flag even if the underlying domain is Microsoft.
The subdomain is part of sharepoint.com, a well-known Microsoft property, so the overall ownership is clear. However, the specific endpoint has no distinct registration or identity, which is normal for infrastructure but offers no transparency about its purpose.
No blacklist hits or Google Safe Browsing flags, so there's no history of abuse. The lack of Wayback snapshots is expected for a backend endpoint that was never meant to be a public-facing site.
This is an infrastructure endpoint, not a business or consumer site. The absence of an About page, contact info, or social media is entirely normal for a technical service like this.
No privacy policy or terms of service are expected for a backend service that doesn't collect user data or facilitate transactions. This is not a compliance gap.
The hosting is on Microsoft's own ASN, which is solid, but the TLS misconfiguration and the HTTP 400 error indicate the service is broken or misconfigured. Missing security headers and DNSSEC are minor concerns for an internal endpoint but still worth noting.
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 →