Pushy-prod-nlb2-93bf95f445442309.elb.us-west-2.amazonaws.com is not a typical website you'd visit. It's a hostname assigned to an Amazon Web Services load balancer, and our tests show it returns a 404 error and refuses HTTPS connections. There's no content, no contact information, and no evidence of a real business behind it. This URL looks like a backend service endpoint that was never meant for public consumption. If you came across it in an email or ad, treat it as a red flag. Legitimate infrastructure that serves customers always has proper TLS and a clear purpose. This one has neither. There are no pushy-prod-nlb2-93bf95f445442309.elb.us-west-2.amazonaws.com reviews because it's not a functioning service. The question 'is pushy-prod-nlb2-93bf95f445442309.elb.us-west-2.amazonaws.com a scam' is less relevant than simply recognizing that it's not a site worth engaging with.
No — pushy-prod-nlb2-93bf95f445442309.elb.us-west-2.amazonaws.com doesn't look safe
In plain English
This isn't a real website. It's an AWS load balancer endpoint that returns a 404 error and doesn't use HTTPS. There's no business identity, no content, and no way to contact anyone. It's not necessarily a scam, but there's nothing here to trust.
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
No HTTPS connection could be established, which is a critical gap for any public-facing service. Even a basic landing page should serve over TLS.
This is an AWS load balancer hostname, not a registered domain. There is no identifiable owner or business behind it, which is expected for a backend endpoint but not for a site you'd visit.
No blacklists and no malware flags, but the site has no web archive history and no external trust signals. It's essentially invisible.
No contact information, no about page, no social media presence. This is normal for a technical endpoint, but it means you have no way to reach anyone running it.
No privacy policy or terms of service. For a backend service that doesn't collect user data, this is irrelevant, but it confirms the site isn't intended for consumers.
DNS resolves to multiple IPs, but the site itself returns a 404 error and doesn't respond to secure connections. No email or security headers are configured.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.