This hostname looks like it belongs to Microsoft's Teams scheduler infrastructure, but it's not a functioning website. When you try to visit sched.usce-02.ic3-calling-scheduler.centralus-prod.cosmic.office.net, the SSL certificate doesn't match the address, so your browser will block the connection. The server returns a 404 error, meaning the route doesn't exist. There's no homepage, no contact info, no privacy policy — nothing to evaluate. In short, there's no real business or service behind this URL. It's likely a misconfigured internal endpoint that shouldn't be exposed to the public. If you're wondering whether sched.usce-02.ic3-calling-scheduler.centralus-prod.cosmic.office.net is a scam, the answer is simpler: it's just a broken link. There's nothing to buy, sign up for, or interact with. Move on.
No — sched.usce-02.ic3-calling-scheduler.centralus-prod.cosmic.office.net doesn't look safe
In plain English
This isn't a real website — it's a broken internal Microsoft service endpoint. The SSL certificate doesn't match the address, the site returns a 404, and there's nothing to interact with. There's no reason to visit it, and no data to trust. Treat it as a dead link.
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 for this hostname, making the site unreachable over HTTPS. This is a critical failure for any site that expects visitors, even an internal endpoint.
The hostname is a subdomain of office.net, which is owned by Microsoft. While the specific subdomain isn't registered separately, the parent domain is a well-known, legitimate organization.
No blacklist hits or Google warnings exist, but the site has no history in the Wayback Machine and no traffic ranking. For an internal service, this is unremarkable.
There is no contact information, about page, or social media presence. That's expected for a backend infrastructure endpoint that isn't meant for public interaction.
No privacy policy or terms of service exist. An internal service has no legal obligation to publish these, so this is not a concern.
DNS resolution works, but the site fails to load due to a TLS error and returns a 404. No security headers or DNSSEC are configured, which is common for internal services but still a sign of poor configuration.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.