If you've landed on ftdr-prod.my.connect.aws, you're looking at an Amazon Connect service page — not a third-party website. Amazon Connect is Amazon's cloud-based contact center, and this subdomain handles session management for agents. The security signals are excellent: strong encryption, modern protections, and no threats detected. For a backend service, missing things like a privacy policy or contact page are perfectly normal because Amazon's own policies cover the underlying platform. The key thing to check is whether you're supposed to be here. If you're an Amazon Connect agent, this is part of the legitimate workflow. If you reached this URL by accident or from a suspicious link, verify the domain ends in ".aws" — that's a strong indicator of Amazon ownership. Overall, there's no reason to treat this as a scam; it's infrastructure, not a storefront.
In plain English
This is a legitimate Amazon Connect service endpoint, not a standalone website. It's safe to use if you're an authorized Amazon Connect user. The security and infrastructure are rock-solid, and the lack of typical business pages is normal for a backend service of this kind.
Where the score comes from
Excellent security setup: a valid certificate with modern TLS, strong browser protections against clickjacking and content sniffing, and no malware or phishing flags. This is exactly what you'd expect from a major cloud provider's infrastructure.
The domain lives under Amazon's own namespace (aws), so the ownership is clear even though a standard WHOIS lookup isn't possible. For a service endpoint like this, that's as good as it gets.
No blacklists or Google Web Risk flags. The lack of a web archive history is normal for a dynamic service page rather than a traditional website. No negative signals found.
There's no contact page, about page, or social media links — but this is a backend login endpoint, not a public-facing business. Users would go through Amazon's established support channels instead.
No separate privacy policy or terms of service on this subdomain, but that's expected for a service component of a larger platform. Amazon's own legal agreements cover the underlying AWS service.
Solid DNS setup with four name servers, fast page load, and the right security headers in place. No email handling is fine for a service that doesn't send mail.
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 →