This hostname belongs to Microsoft's infrastructure, but something is badly misconfigured. The SSL certificate was issued for a different Azure endpoint, and the browser won't let you connect — you'll get a security warning before any content loads. The page itself shows only a generic error message, suggesting this is a backend node that shouldn't be exposed directly to the public. There's no evidence of phishing or malware (Google Web Risk is clean), but the broken certificate makes it untrustable as-is. For an infrastructure endpoint — like a CDN edge or SharePoint backend — you'd expect flawless TLS configuration. Here, that's missing, and the lack of any contact or documentation means no one to fix it. If you arrived here through a link, that link is almost certainly broken. Don't try to bypass the certificate warning; this site isn't meant to be accessed by regular users, and forcing a connection won't reveal anything useful.
No — 2537-ipv4v6e.clump.dprodmgd104.aa-rt.sharepoint.com doesn't look safe
In plain English
This site is in bad shape. The certificate is invalid, the SSL handshake fails, and the page never actually loads. It appears to be a misconfigured Microsoft Azure backend endpoint, not a functioning website, and no amount of clean blacklists changes the fact that your browser won't let you connect securely.
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 completely invalid for this domain, pointing instead to a Microsoft Azure CDN hostname. That means any connection is blocked by modern browsers, and the site was unreachable during testing. Even though it hasn't been flagged by Google Web Risk, a broken certificate is a fundamental security failure.
This hostname is a subdomain of sharepoint.com, but WHOIS returns no match for the full address — it's not a separately registered domain. There's no about page, no team, and no indication of who configured this endpoint. That's normal for behind-the-scenes infrastructure, but it also means no accountability if something goes wrong.
No blacklists or threat lists have flagged this hostname, and it hasn't been seen by the Wayback Machine — it likely never had a public face. The complete absence of any external trust signals (no reviews, no archived history) means there's no way to gauge its track record.
There is zero contact information or social media presence tied to this specific hostname. As an infrastructure endpoint that's not intended for direct public interaction, that's not surprising, but it also means anyone who ends up here has no way to ask questions or report issues.
No privacy policy or terms of service are available. For a generic error page served from a backend system, that's expected — there's nothing being sold or data being collected. Still, it's one more missing piece that would be required if this were a live commercial service.
The hosting network is Microsoft's own, which normally means solid reliability, but the TLS misconfiguration undermines that. DNS resolution works and page load is fast, but the server returns a 400 status and fails to complete a secure connection. Basic browser protections are also absent.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.