imengine.public.prod.cdr.navigacloud.com looks like a backend content-delivery subdomain, not a consumer storefront. For this kind of infrastructure service, the most important checks are about stability and ownership. The domain has a five-year history, clean threat reports, and a legal disclosure that names the operator. Those are good signs. On the downside, the site accepts older encryption and doesn't set common browser security headers — typical for older or less maintained servers. If you're a developer considering integrating this service, check whether they've addressed TLS 1.0/1.1 support and ask about their security policy. Otherwise, for a behind-the-scenes platform, imengine.public.prod.cdr.navigacloud.com passes the basic trust tests without raising red flags.
Yes — imengine.public.prod.cdr.navigacloud.com looks mostly safe
In plain English
This site is mostly safe. It has a solid track record and clear legal documentation, but its security configuration has a few gaps worth noting. For an infrastructure service, these don't warrant alarm, but they suggest room for improvement.
Where the score comes from
The site uses a valid TLS certificate and supports modern encryption, but it still accepts outdated protocols that have known flaws. It also lacks basic browser protections like anti-clickjacking headers. This is a reasonable setup for a backend service, but not ideal.
A legal-entity disclosure (Impressum) provides a real-world anchor for who runs this service, and an About page exists. No direct contact info appears on the homepage, which is somewhat common for infrastructure subdomains.
The domain has been on the web for 5 years with no appearances on blacklists or threat databases. No negative reputation signals were found.
An About page and legal disclosure are present, but there's no contact information on the main page and no social media presence. For a service that handles content delivery, this is acceptable but lean.
Privacy policy, terms of service, and a business-disclosure page are all in place. This meets the core legal obligations for a commercial operation in most regions.
Hosted on a major CDN with fast load times, but missing DNSSEC and security headers. Accepting older TLS versions and lacking a robots.txt file point to a casual approach to configuration.
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 →