If you landed on japaneast1-6.pushnp.svc.ms expecting a website, you probably saw a 404 error. That's fine — this isn't a site you're meant to visit. It's a backend address used by Microsoft's push notification service, part of the svc.ms domain family. The certificate, hosting, and server all come straight from Microsoft. There's no scam or fake here. For context, legitimate service endpoints like this often lack legal pages, contact info, or social media because they're not designed for human interaction. The security is solid: modern encryption, no blacklists, and no threats detected. If you're checking whether japaneast1-6.pushnp.svc.ms is a scam, the answer is no — it's just a piece of Microsoft's infrastructure. Nothing to worry about.
In plain English
This is a Microsoft service endpoint, not a consumer website. The 404 error you see is expected — it's a backend address used for push notifications, not something you browse. All signals point to legitimate Microsoft infrastructure. There's nothing to worry about here.
Where the score comes from
Strong security: modern TLS, valid Microsoft-issued certificate, HSTS enforced, and no threats detected. This is exactly what you'd expect from a Microsoft-owned infrastructure endpoint.
The domain is a subdomain of svc.ms, which belongs to Microsoft. The certificate issuer and hosting network both confirm Microsoft ownership. The WHOIS timeout is irrelevant for a known corporate domain.
Clean on all blacklists and Google Web Risk. No Wayback Machine history is expected for a low-level service endpoint — it's not a public website. No negative signals.
There is no about page, contact info, or social media presence, but that's normal for a backend service endpoint not intended for public interaction. The absence isn't a red flag here.
No privacy policy or terms of service, but this is a machine-to-machine service endpoint, not a consumer-facing site. Legal compliance expectations don't apply to the same degree.
Hosted on Microsoft's own network with fast load times and proper TLS 1.3. No MX records are fine since it's not an email server. DNSSEC is not enabled, but that's common for internal service domains.
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 →