When you land on claroperupoc.vtexassets.com, you’re greeted with an error page — not a store, not a product listing. That’s because this is a subdomain of vtexassets.com, the asset delivery network used by VTEX commerce stores. The HTTP 400 error means the backend server is unavailable right now, so there’s nothing to evaluate as a shopper. The underlying infrastructure is solid: it runs on AWS CloudFront with a valid SSL certificate, and the domain isn’t flagged on any blacklists. That’s all consistent with a legitimate retailer’s behind-the-scenes setup. But until the site actually loads, you can’t verify what it sells, who runs it, or whether it’s safe to buy from. There’s no reason to suspect a scam — just a technical outage. If you came here expecting a store, try again later or contact the store’s support team if you know their name. For now, there’s not enough signal to call it fake, but also no reason to trust it with any personal data.
Not sure — double-check claroperupoc.vtexassets.com first
In plain English
This isn’t a working website — it’s an error page served from a VTEX asset domain. The technical backbone is legitimate (AWS CloudFront, valid SSL), but the site is currently broken. If you were trying to visit a store hosted here, you’ll need to wait for the backend to come back online. There’s no evidence of a scam, but also nothing to use yet.
Where the score comes from
The connection is encrypted with a valid certificate and modern TLS, which is standard for any legitimate service. The lack of browser-level protections like clickjacking blockers is not a concern for this type of infrastructure page.
This is a subdomain of vtexassets.com, a known VTEX asset hosting domain. WHOIS data is unavailable because subdomains aren’t registered independently, which is normal. The parent company (VTEX) is a real commercial entity, so ownership is effectively traceable.
No blacklist entries or Google Web Risk flags, which is good. The page returned an HTTP error when tested, so there’s no live content to evaluate, but the domain itself carries no known abuse history.
There is no about page, contact info, or social media presence on this subdomain. That’s normal for a CDN asset endpoint — it’s not meant to be a public-facing storefront. Transparency expectations don’t really apply here.
No privacy policy or terms of service are present. This is expected for an error page served from a content delivery network. No user data is being collected at this URL, so compliance gaps are not a practical risk.
Solid technical setup: AWS CloudFront with multiple IPs, proper name servers, a sitemap, and robots.txt. The fast load time and TLS 1.3 indicate real operational investment. The HTTP 400 error suggests a backend issue rather than a infrastructure weakness.
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 →