When you come across a hostname like eo-perfops5.qcloudteo.com.eo.dnse5.com, the first thing to know is that it's not a typical website. It belongs to a CDN infrastructure used by cloud providers, but in this case, the SSL certificate doesn't even match the domain, so you can't connect safely. There's no owner information, no contact details, and no privacy policy or terms of service. That's perfectly normal for a backend server, but if someone directed you here thinking it's a real site, that's a red flag. Legitimate CDN nodes usually have valid certificates and are part of a known network. This one appears misconfigured or abandoned. If you're asking whether this is a scam, the better question is whether it's functional at all. For any consumer-facing purpose, this hostname is not safe to trust.
No — eo-perfops5.qcloudteo.com.eo.dnse5.com doesn't look safe
In plain English
This hostname doesn't work as a regular website. The SSL certificate is invalid and nobody claims ownership, which makes it untrustworthy for any real use. It's likely a misconfigured or abandoned CDN endpoint, not a service meant for visitors.
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 and doesn't match the domain, so the site can't be reached securely. That's a major red flag for any online service.
There's no visible ownership or registration information for this hostname. It's essentially anonymous, which is a serious concern if this is meant to be a real website.
The hostname hasn't been flagged by security blacklists and has no history, which is typical for new or non-public infrastructure. There's nothing actively harmful on record.
No contact details, about page, or social media presence were found. For an infrastructure hostname this is normal, but if someone tried to use it as a consumer site, it would be untrustworthy.
Legal pages like privacy policies aren't expected for a backend hostname. There's no compliance violation here given the nature of the site.
The hostname resolves to a single IP and is hosted on a legitimate CDN provider. Basic DNS setup is functional, which is fine for infrastructure.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.