This domain is a subaddress on Yandex's content delivery network, not a front-facing website. Because of that, many typical trust signals — like an about page, contact details, or privacy policy — don't apply here. What does matter is that the server still allows old, insecure encryption methods (TLS 1.0 and 1.1) and has been flagged on one spam blacklist. For an infrastructure node, these are real but not alarming weaknesses; they suggest less attentive maintenance rather than malicious intent. If you encounter this address while browsing (for example, loading a resource from a Yandex-hosted site), it's unlikely to be a scam. But the blacklist listing is worth noting. The bottom line: this isn't a site you evaluate with the same checklists as an online store. It's a technical component, and the main risk here is that it could serve content for other sites with questionable security. Most users will never see it directly.
Not sure — double-check ext-cloudcdn-uztas01uztl-01.cdn.yandex.net first
In plain English
This looks like a technical endpoint on Yandex's content network, not a typical website you'd visit or buy from. The server has some configuration issues — it's listed on a spam blacklist and still supports outdated encryption. For a backend node, that's worth caution, but it's not a sign of a scam operation. You likely won't interact with this domain directly; if you do, proceed carefully and understand it's part of a larger infrastructure, not a standalone business.
Where the score comes from
The SSL certificate is valid and uses modern TLS 1.3, but the server still accepts outdated TLS 1.0 and 1.1, which are known to be insecure. This is a weak point for any server, even infrastructure.
This is a subdomain of yandex.net, a well-known company. The lack of direct WHOIS is normal for a CDN subdomain, so identity is not a concern here.
The domain is listed on one DNS blacklist and has no web archive history, suggesting this endpoint may have been used for unwanted activity or is very new.
As an infrastructure subdomain, the absence of contact info, about page, or social media is completely expected. No transparency concerns for this type of endpoint.
No legal pages are expected for a CDN edge server. This is a technical component, not a commercial website, so compliance requirements do not apply.
The server uses nginx and TLS 1.3, but the DNS blacklist listing and acceptance of legacy TLS indicate configuration issues. The hosting in Uzbekistan is unusual for a Yandex CDN but not inherently problematic.
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 →