Public website technology intelligence — one scan, one detailed report.
Website Technology

How to Detect AWS Services Used by a Website

Learn how to detect AWS services used by a website. Check DNS and HTTP headers for CloudFront, S3, Cognito, API Gateway, Amplify, and Route 53.

How to Detect AWS Services Used by a Website
How to Detect AWS Services Used by a Website

To detect AWS services used by a website, check the site’s public DNS records, then inspect the main page and the requests it makes in your browser. A cloudfront.net DNS target or an x-amz-cf-id response header can reveal CloudFront. An image loaded from an S3 hostname can reveal object storage. An API call to an execute-api hostname can reveal Amazon API Gateway. Each clue tells you something about the request you observed. docs.aws.amazon.com

The useful question is often more specific than “Does this website use AWS?” If you’re planning a migration, you need to know whether AWS serves the frontend, stores product images, handles login, routes API traffic, or manages DNS. Those services have different owners, settings, and migration steps. A website can use three of them and still host its main application somewhere else.

Start with the WebBuildFinder website technology checker for an overview, then verify individual findings with the checks below.

AWS Is More Than Hosting

Amazon Web Services offers separate products for content delivery, file storage, authentication, APIs, traffic distribution, application deployment, and DNS. Each can support a different part of the same website. A shop might use CloudFront for product photos, Cognito for customer login, and Route 53 for DNS, while its storefront runs on another platform. Saying “the shop uses AWS” is accurate in this example, but it leaves out which parts depend on AWS. docs.aws.amazon.com

Start with the URL or feature relevant to your work. If you’re taking over a product catalog, inspect the main page, a product image, and any catalog requests the browser makes. If you’re replacing an account portal, follow its normal public sign-in link and observe where it takes you. The homepage, asset host, and login service can each tell a different part of the story.

AWS servicePublic clue to look forWhere to checkAmazon CloudFrontcloudfront.net or x-amz-cf-idDNS and response headersAmazon S3bucket.s3.region.amazonaws.com patternAsset URLs in the Network panelAmazon CognitoAmazon Cognito domain in a normal login redirectSign-in request and redirect chainAmazon API Gatewayapi-id.execute-api.region.amazonaws.com patternFetch/XHR requestsElastic Load Balancingname-id.elb.region.amazonaws.com patternPublic DNS aliasesAWS Amplify HostingAn amplifyapp.com deploymentDefault deployment URL or verified custom-domain mappingAmazon Route 53awsdns nameserversAuthoritative NS records for the relevant zone

For browser checks, open DevTools → Network, enable Preserve log if you expect redirects, and reload. Use Doc for the main page, Img for images, and Fetch/XHR for API calls. For DNS, check the exact hostname being used. For example, dig +short www.example.com CNAME checks the www alias, while dig +short example.com NS checks the nameservers for the root domain. developer.chrome.com

CloudFront

Amazon CloudFront is AWS’s content delivery network. AWS assigns each distribution a hostname ending in cloudfront.net. A website can use that hostname directly or connect it to a custom domain. You may also see x-amz-cf-id in the response headers. AWS documents it as the identifier CloudFront sends for the request. docs.aws.amazon.com

To check whether CloudFront serves the page itself, select the main document request in DevTools and look for x-amz-cf-id under Response Headers. Then check a representative image or stylesheet separately. If the CloudFront header appears only on requests to media.example.com, record CloudFront for media delivery. If it appears on the main document, you have evidence that CloudFront serves the public page as well.

This difference matters during a redesign. Suppose pictures on the old site come through CloudFront and the new team plans to preserve their URLs. The media distribution may still be important even when the homepage moves to a different host. Conversely, if CloudFront serves the homepage, the header leaves the upstream application open. CloudFront can retrieve content from several types of origins. docs.aws.amazon.com

S3

Amazon Simple Storage Service, or S3, is commonly used to store images, documents, downloads, and static website files. A direct object request can have a hostname in the form bucket-name.s3.region.amazonaws.com. AWS also documents distinct regional website endpoints that can serve the index document for a bucket configured as a static website. These URL patterns tell you different things about how the storage is being used. Amazon S3

Open a public page, go to Network, and inspect a resource the site already loads, such as a product photo or brochure. If the request goes directly to an S3 hostname, record the type of file and the hostname that served it. If image requests use a branded domain and return CloudFront headers, report CloudFront for image delivery. S3 may be behind that distribution, but the CDN response alone leaves the origin unknown.

A useful handover note might read, “Product specification PDFs load from S3. The product pages themselves are served through the storefront platform.” That gives the new team a concrete dependency to check before moving files or changing links. For reports, the resource hostname and file type are usually enough. If a download URL includes a signature or other query parameters, omit them from shared notes.

Cognito

Amazon Cognito user pools can provide managed sign-in, sign-up, and password recovery. AWS lets a user pool use an Amazon Cognito domain or a custom domain. A site can therefore send visitors to a recognizable Cognito hostname, or it can present login under a branded name such as login.example.com. Amazon Cognito

To check, turn on Preserve log in the Network panel and click the website’s normal Sign in link. Watch the document requests and redirects. If the flow reaches a Cognito domain, that’s a useful signal about the identity service. An /oauth2/authorize path can help you recognize the stage of the flow, but the path is a standard OAuth convention. The destination hostname and its role in the redirect chain carry more weight when identifying Cognito. Amazon Cognito

Some sites use Cognito and then send the visitor to another identity provider. If you see Cognito followed by a Google sign-in page, record the sequence as observed. The Cognito step can be part of how the site handles identity even when another provider supplies the login screen. You can document that from the public redirect without entering credentials or recording cookies, authorization codes, or signed URLs. Amazon Cognito

API Gateway

Amazon API Gateway can expose an application’s API through an AWS-managed endpoint. AWS documents the default REST API hostname pattern as api-id.execute-api.region.amazonaws.com. You can find it in the Fetch/XHR view when a public page makes a request during normal use. Amazon API Gateway

For example, a property website might render its main page on one hosting platform and call API Gateway when a visitor changes the price filter. Open the listing page, select Fetch/XHR, and use the filter once. If the request goes to an execute-api hostname, you can attribute API Gateway to the listing filter request. The URL leaves the application code, compute service, and data store behind that API unverified.

API Gateway also supports custom domains, and teams can disable the generated endpoint. A request to api.example.com may therefore use API Gateway without displaying execute-api in the browser. When the public response has no clear product signal, document the branded API hostname and leave the provider open. If you maintain the project, use the deployment configuration to verify how the custom domain is mapped. Amazon API Gateway

Elastic Load Balancer

AWS Elastic Load Balancing distributes incoming traffic to backend targets. Application Load Balancers and Network Load Balancers both receive AWS DNS names with a pattern like name-id.elb.region.amazonaws.com. If the public CNAME chain for app.example.com points to an elb hostname, that’s evidence an AWS load balancer sits in the request path for that application. Elastic Load Balancing

The hostname pattern alone may leave the load balancer type open because both products can use the same general structure. It also leaves the underlying target open. If your task is to figure out where a redirect is configured, a public DNS result can tell you there’s a load balancer to check. The listeners, routing rules, and target configuration are where the site owner can verify which component handles the request.

You may encounter this setup when the homepage uses a managed website platform and an application subdomain points to AWS. Report the load balancer for the application hostname. That keeps the public website and the customer application from being lumped together during migration planning.

Amplify

AWS Amplify Hosting assigns deployments an amplifyapp.com address. A default URL can include a branch name and an application identifier before the service domain. Amplify also lets you connect a custom domain, so the production site may display only its branded hostname in the address bar. AWS Amplify Hosting

Look for a deployment URL that you can tie to the project you’re reviewing. A client may provide an Amplify preview link, a public project page may link to a demo, or the active deployment dashboard may show the mapping for the custom domain. If the only Amplify evidence you can verify is for a preview, report it for the preview. A team can host a staging build and the production site on different platforms.

If you see CloudFront headers on the production site, those headers identify a delivery service. Look for Amplify-specific evidence before assigning the deployment to Amplify Hosting. The distinction matters if you’re taking over builds, environment variables, or release settings. Access to the active deployment project can tell you where those settings are managed. AWS Amplify Hosting

Route 53

Amazon Route 53 handles DNS and also offers domain registration. A public DNS lookup can reveal authoritative nameservers with awsdns in their names. AWS documents names such as ns-2048.awsdns-64.com as examples of the format. When that pattern appears in the authoritative NS records, you have evidence for Route 53 DNS for the zone you checked. Amazon Route 53

This finding is useful when a client asks where to add a verification record, point a new subdomain, or update a DNS entry for a migration. Start with the zone that controls the record. A subdomain can be delegated separately, so check its nameservers if its configuration appears to differ from the root domain.

After checking NS records, look at the A, AAAA, or CNAME records for the hostname that serves the website. A domain can use Route 53 for DNS, another company for registration, and a separate provider for web hosting. For a more detailed walkthrough of those checks, see How to Find Where a Website Is Hosted.

What Cannot Be Confirmed Publicly

Public evidence gives you a view of the services involved in requests your browser can see. It usually leaves the database, deployment pipeline, account ownership, network layout, and permissions unknown. An API Gateway hostname identifies the gateway used by the request. The response may leave you with no reliable way to determine whether the integration uses Lambda, a load balancer, or another upstream service. The same applies to CloudFront and the origin it retrieves content from. Amazon API Gateway

Regional identifiers also need context. If an execute-api hostname includes us-east-1, that identifies the region in the API’s public hostname. It leaves open where documents are stored, where other services run, or where a customer’s data is processed. If your work depends on those details, verify them in the site owner’s deployment records. Amazon API Gateway

A reproducible audit finding includes the URL, the signal, and the feature it applies to. For example, “The public product filter calls an Amazon API Gateway endpoint. Product PDFs load from S3. Route 53 provides authoritative DNS for the root domain.” That tells the next person exactly which dependencies to verify before changing the site. If the application host is still unclear, record it as unverified and request the relevant infrastructure or deployment configuration as part of the handover.

To start your own check, enter the website URL into the WebBuildFinder website technology checker. Then inspect the main document, the particular assets or features you care about, and the public DNS records for the relevant hostnames.

Need help with your website stack?

Share your current site or a reference build and tell us what you want to create or improve.

Discuss your project