This domain is a CDN subdomain, likely used to serve static files for a website builder platform. But right now it doesn’t work — visitors get an Access Denied error from AWS. That alone makes it impossible to assess as a legitimate service. Most CDN endpoints either serve content or redirect properly; this one does neither. Without a working page, there’s no way to know what it was meant to host or whether it’s trustworthy. If you encountered this link somewhere, it’s probably a dead end. For any practical purpose, it’s not a site you can engage with, and the lack of any web archive history suggests it’s either very new or was never properly set up. There’s no evidence of malicious intent either, but a broken site offers nothing to trust. Skip it and look for the actual service behind it.
No — lirp.cdn-website.com doesn't look safe
In plain English
This site isn't actually working — it returns a 404 error and has no history anywhere. Without content or any sign of real use, there's nothing to trust here. I'd steer clear until it shows signs of being a functional website.
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 site uses a valid SSL certificate and is served over a modern TLS connection through AWS CloudFront. No blacklist or malware flags. This is a solid setup for any online service.
This is a subdomain, so the lack of separate WHOIS registration is normal. The parent domain likely has its own registration. No additional ownership signals are available, which is typical for a CDN endpoint.
The site returns a 404 error and has no history in the Wayback Machine. A functional website should serve content; this one doesn't. There's no evidence of established use or longevity.
No contact information, about page, or social media presence. For a CDN subdomain these are not required, but their absence reinforces that this isn't a standalone consumer site.
Legal pages like a privacy policy are not expected for a content delivery endpoint. Nothing here suggests a compliance issue for this type of service.
DNS resolves and the site is hosted on AWS with CloudFront, but the HTTP 404 error indicates a serious configuration problem. A working site should return a valid page.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.