Homeβ€Ί Infrastructureβ€Ί 193670-ipv4v6.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net
This site failed important safety checks β€” please read this before going any further.
Be careful β€” Dangerous

No β€” 193670-ipv4v6.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net doesn't look safe

10/ 100 trust score
Industry: Infrastructure Checked Jul 11, 2026 Infrastructure average: 44 24 signals

In plain English

This site is not reachable and its SSL certificate doesn't match the address at all. It looks like a broken internal Microsoft service endpoint that was never intended for public use. You shouldn't interact with it β€” there's nothing of value here and the connection isn't secure.

What you should do now

Don't panic. These steps limit the damage, and the sooner you take them the better.

1

Don't enter any details

No passwords, card numbers or personal information β€” even if the site looks professional.

2

Close the tab

Especially if you got here from an email, text message or social media ad.

3

Already paid? Call your bank

Contact your bank or card provider right away. They can often stop or reverse a recent payment.

4

Warn others

Report the site and share this check with anyone who sent you the link.

N Partner pick
Better safe than sorry. Stay covered everywhere: NordVPN's Threat Protection blocks known scam sites before they load.
Try NordVPN β†’
Cross-referenced 24 live signals from Google Safe Browsing, VirusTotal, WHOIS and more on Jul 11, 2026. How we score β†’

Where the score comes from

We look at six areas. Here's how 193670-ipv4v6.farm.dprodmgd105.aa-rt.sharepoint.com.dual-spo-0005.spo-msedge.net did in each.
10
Security

The SSL certificate is invalid β€” it's issued for a different domain, and the site can't be reached at all. That's a critical failure for any online service.

80
Identity

This is a subdomain on Microsoft's own network. The WHOIS absence is normal for subdomains, and the IPs belong to Microsoft. Ownership isn't a question here.

50
Reputation

No blacklists and no threats detected, but there's no web archive history and the site isn't ranked. There's simply not enough history to form a reputation.

80
Transparency

No contact info or about page, but that's standard for internal infrastructure endpoints. No one expects a staff directory for a CDN hostname.

80
Compliance

Missing privacy policy and terms, but a non-public-facing infrastructure node doesn't need them under any jurisdiction.

40
Infrastructure

DNS resolution works and is on Microsoft's reliable network, but the site can't actually serve content because the SSL handshake fails. No security headers are set either.

What we checked

The 24 signals behind this report.
Security & Transport
Certificate Issuer
Microsoft Corporation
Google Web Risk
Clean
SSL Certificate
Invalid
Security Headers
0 of 6
Site Reachable
Unreachable
Identity & WHOIS
About Page
Not found
Branding
Missing
Business Disclosure
Not found
Contact Info
Not found
Legal Pages
Missing
Infrastructure & DNS
DNS Blacklists
Clean
DNS Resolution
4 IP(s)
DNSSEC
Not enabled
Email (MX Records)
None
Hosting Network (ASN)
AS8075 MICROSOFT-CORP-MSN-AS-BLOCK
Page Load Time
48ms
Reputation & Reach
Sitemap
Not found
Social Media Presence
None found
Structured Data
None found
Tranco Rank
Not ranked
Trustpilot
No Trustpilot profile
Web Archive History
No archive found
Website Status
HTTP 400
robots.txt
Not found

Think this verdict is wrong?

Site owners can request a fresh scan. Scores update automatically as signals change.

This long, auto-generated hostname looks like it belongs to Microsoft's internal network β€” specifically a SharePoint or Azure Edge infrastructure node. But instead of a working service, you get a failed TLS handshake and an error page saying services aren't available. The SSL certificate is issued for a different Azure domain, which means either this address was never meant for public traffic or something is badly misconfigured.

For an infrastructure endpoint (cloud CDN, internal routing, etc.), a valid certificate and HTTPS reachability are the absolute baseline. This site fails both. There's no web history, no consumer-facing content, and no signals that suggest it's a legitimate public service. Is this a scam? Probably not β€” it's more likely a dead or misconfigured Microsoft server. But you can't use it for anything, and it's certainly not safe to trust. If you landed here, you're not supposed to; move along.

More Infrastructure sites

How similar sites score. See all β†’