Sample alert How it works Coverage PENTEST METHODOLOGY DOCS PRICING FAQ MCP CONTACT LOG IN SCAN MY APP →

How to discover forgotten web applications that you own

GUIDE / ASSET DISCOVERY

To discover forgotten web applications, build one list of every host that you own from several sources, then test which hosts answer. Use certificate logs, subdomain tools, your DNS zone, your hosting accounts, and your cloud accounts. Then decide for each host: decommission it, protect it, or monitor it.

This guide covers only domains and accounts that you own or have written permission to test. Do not run these commands against the domain of another person.

Why do forgotten apps matter?

A forgotten app still runs. It still has its own code, its own database connection, and its own keys. No one updates it, and no one reads its logs.

The risks are the same as for a live app, but nobody watches them:

  • Old code. The app holds bugs that you fixed in the main app.
  • Old data. A test app can hold a copy of real user data.
  • Old keys. A preview can hold a key that you replaced elsewhere.
  • Takeover. A DNS record can point to a resource that you deleted.

AI coding tools make the list longer. Each prompt session can create a project, a preview URL, and a database.

Where do I find my forgotten apps?

Use several sources. Each source finds apps that the others miss.

Source What it finds Needs access to the account
Certificate transparency logs Hosts that ever had a public certificate No
Subdomain tools Hosts in public data sets and DNS No
DNS zone Each name that you published Yes
Hosting platform lists Previews, projects, and old deployments Yes
Cloud account lists Servers, buckets, and managed apps Yes
Search engines Pages that a crawler indexed No
Code repositories Hostnames in code and config Yes

Start with the sources that need no access. Compare the result with the sources that need access. A host that is in the first group only is the most important find. Nobody owns it.

How do I search certificate transparency logs?

A certificate authority writes each public certificate to a public log. The logs show the host names in each certificate. This is certificate transparency, and RFC 6962 defines it. The site crt.sh lets you search these logs.

  1. Open a terminal.
  2. Run the command below. Replace example.com with your domain.
  3. Read the sorted list of names.
curl -s "https://crt.sh/?q=%25.example.com&output=json" \
  | jq -r '.[].name_value' | sort -u > ct-names.txt

The %25 is a URL-encoded % wildcard. It matches each subdomain. The name_value field can hold more than one name, separated by a newline. The sort -u command removes duplicates.

Look for names that you do not recognize. Look for words such as dev, test, staging, old, demo, and admin.

Note: A wildcard certificate, for example *.example.com, hides the real host names. A host with no public certificate does not appear. The log shows only that a certificate existed in the past. It does not show that the host is live now.

How do I enumerate subdomains with subfinder and amass?

Subdomain tools collect names from many public sources. subfinder and OWASP Amass are two open source examples.

  1. Install the tools. Use the instructions in each project.
  2. Run subfinder with passive sources only.
  3. Run Amass in passive mode.
  4. Combine the results with the certificate log names.
subfinder -d example.com -silent -o subfinder.txt
amass enum -passive -d example.com -o amass.txt
cat ct-names.txt subfinder.txt amass.txt \
  | sed 's/^\*\.//' | sort -u > all-names.txt

The sed command removes the *. prefix from wildcard names.

Passive mode reads public data. It does not send requests to your hosts. The active mode of Amass sends DNS queries, so use it only on your own domain.

How do I find which names are live?

A name in a list can be dead. Test each name. The tool httpx from the same vendor as subfinder does this.

httpx -l all-names.txt -status-code -title -silent > live.txt

Each line of the result shows a URL, a status code, and the page title. Sort the result into four groups:

  • 200 with a page. The app is live. Find its owner.
  • 301 or 302. Follow the redirect. It can lead to a login page or to another host.
  • 401 or 403. The host has some protection. Check how strong it is.
  • No answer. Check the DNS record. The next section explains why.

How do I review the DNS zone?

Your DNS zone is the most exact list. It holds each name that you published. Export it from your DNS provider. If you do not know which provider holds the zone, run this command:

dig +short NS example.com

The answer shows the name servers. They show the provider.

  1. Export the zone file, or list the records with the API of the provider.
  2. Mark each A, AAAA, and CNAME record.
  3. Compare each name with your list of live apps.
  4. Find each name that has no owner.

How do I find a dangling CNAME?

A CNAME record points one name to another name. If the target is a service resource that you deleted, the record is dangling. An attacker can sometimes create a new resource with the same name on that service. Then the attacker serves content on your subdomain. This is a subdomain takeover. The OWASP Web Security Testing Guide describes the test.

Use this procedure for each subdomain that has a CNAME:

  1. Get the CNAME target.
  2. Resolve the target.
  3. Request the page.
  4. Read the error text.
dig +short CNAME shop.example.com
dig +short shop.example.com
curl -sI https://shop.example.com | head -5

If the CNAME target does not resolve (the NXDOMAIN status), the record is dangling. If the target resolves but the service shows an error such as “no such app” or “site not found”, the record can also be dangling. Each provider uses its own error text. The community project can-i-take-over-xyz keeps a list of which services allow a takeover.

The fix is to delete the DNS record. It takes one minute.

Warning: Delete the DNS record before you delete the resource. If you delete the resource first, the record is dangling until you remove it.

How do I find old preview deployments?

Hosting platforms create a URL for each branch or each prompt. These URLs stay live. A platform list shows them, but the DNS zone does not.

Platform Where to look Related guide
Vercel Deployments, filter Preview; vercel ls Vercel previews
Netlify Site Deploys list; netlify sites:list Netlify safety
Lovable Project list and Share setting Public Lovable project
Replit Your list of apps and Deployments Replit database public

On Vercel, these commands list your projects and domains:

vercel projects ls
vercel domains ls
vercel ls

On Netlify, this command lists your sites:

netlify sites:list

For each preview, ask three questions. Is it public? Does it use a production database? Does it hold a live key? The Vercel preview guide shows how to turn on Deployment Protection. The Lovable guide shows how to check the visibility of a project and how to replace keys.

Sign in to each free account that you ever used for a test. A forgotten account can hold old projects.

How do I list apps in my cloud accounts?

A cloud account can hold apps that no DNS record names. Use the command line tool of each cloud. Use a read-only role.

AWS

aws ec2 describe-instances \
  --query 'Reservations[].Instances[].[InstanceId,State.Name,PublicDnsName]' --output table
aws elbv2 describe-load-balancers --query 'LoadBalancers[].[LoadBalancerName,DNSName]' --output table
aws cloudfront list-distributions \
  --query 'DistributionList.Items[].[Id,DomainName,Aliases.Items]' --output json
aws s3api list-buckets --query 'Buckets[].Name' --output text
aws amplify list-apps --query 'apps[].[name,defaultDomain]' --output table
aws route53 list-hosted-zones --query 'HostedZones[].[Id,Name]' --output table

Run the Regional commands for each Region that you use. CloudFront and Route 53 are global.

Google Cloud

gcloud projects list
gcloud run services list --project PROJECT_ID
gcloud app services list --project PROJECT_ID
gcloud compute instances list --project PROJECT_ID
gcloud dns managed-zones list --project PROJECT_ID

Run the commands for each project in the first list.

Azure

az webapp list --query "[].{name:name,host:defaultHostName,state:state}" -o table
az staticwebapp list --query "[].{name:name,host:defaultHostname}" -o table
az network dns zone list -o table

Check each subscription. Use az account list to see them.

A server that runs and has a public address is a live host, even if no DNS name points to it. A bucket that serves a website is also a live host. For each result, find the owner and the purpose. If you find neither, mark the item for the decision step.

What about old staging sites and admin panels?

Teams name staging sites in a predictable way, and attackers know the names. Check the names in your list for words such as staging, stage, dev, uat, qa, admin, internal, and old.

Then search your repositories for hostnames. This command lists each subdomain in the Git history:

git grep -h -oE "[a-z0-9.-]+\.example\.com" $(git rev-list --all) | sort -u

For each staging site, check if it uses the production database, a real payment key, or real email. If it does, treat it as a production system. The source map checker and the environment exposure checker show if a host exposes its code or its variables.

How do I use search engines to find more?

A search engine shows pages that a crawler found. Use these queries on your own domain:

  • site:example.com -www lists hosts other than the main site.
  • site:example.com inurl:staging finds staging pages.
  • site:example.com intitle:"index of" finds open file listings.

Open each result in a private window to see the live state.

How do I decide what to do with each app?

Put every host in one table. Use one row for each host. Write the owner, the purpose, the data it can reach, and the last deploy date. Then choose one of three actions.

Action Use it when Steps
Decommission No one needs the app Delete the DNS record, then the resource, then the keys it used
Protect The app is needed but is open Add a login, remove real data, replace old keys
Monitor The app is needed and is protected Keep it in the list and test it on a schedule

Follow these steps for each host:

  1. Find the owner. Ask the team. If no person owns it, assign one.
  2. Find the data. Check which database, storage, and keys it uses.
  3. Choose the action from the table.
  4. Do the action.
  5. Test from outside to make sure that the result is right.

When you decommission an app, do the steps in this order. First delete the DNS record. Then delete the hosting resource. Then replace each key that the app held, even if you think no one read it. Then delete the database or storage that only this app used.

If you cannot find an owner and the app holds real data, stop its public access first. Ask questions after that.

How do I test the apps that I keep?

A host that you keep needs a test from outside. A scan shows what a stranger sees. In VibeEval, add the host as a target. The scan scope setting can include subdomains of the registered host. Choose the profile and read the options in the scan guide. Read each result in the findings guide.

Only add hosts that you own. The targets documentation states that VibeEval is for systems that you own or have written permission to test.

The vibe code scanner tests an AI-built app. The website vulnerability scanner tests any site from its URL. For a view that stays current, read about security monitoring.

How do I keep the list current?

A list that you build once is old in a month. Add these habits.

  1. Put each new project in a shared list on the first day.
  2. Give each preview and test app an end date.
  3. Delete the DNS record when you delete a project.
  4. Repeat the certificate log search every month.
  5. Review the cloud account lists each quarter.

The pillar guide on secure AI-generated SaaS shows how to place this work in the full life of an app. If you manage the site for a small business, the checklist for SMB web apps covers ownership of domains and vendor accounts.

When should I get help?

Get help from a security engineer if one of these is true:

  • You find a host that you do not know and it holds real user data.
  • A dangling record was live for a long time and the old resource held sensitive content.
  • You find content on your subdomain that you did not publish.
  • Your cloud account holds servers that you do not recognize.
  • You must tell users or a regulator.

Keep the lists, the command output, and the times.

Common questions

What is a forgotten web application?
It is an app that is still online but that no person maintains. Examples are an old staging site, a test app from a past project, or a preview deployment. It still answers requests, so an attacker can still reach it.
Can I use these tools on any domain?
No. Use them only on domains that you own or have written permission to test. Passive sources such as crt.sh only read public records, but the DNS and HTTP checks send requests to the hosts.
Is a certificate transparency log complete?
No. A wildcard certificate hides the names of its hosts. An app that has no certificate, or that uses a private certificate authority, does not appear. Use more than one source.
What is a dangling CNAME?
It is a DNS record that points to a service resource that no longer exists. If another person can claim that resource name, they can serve content on your subdomain. This is a subdomain takeover.
How often must I repeat this work?
Repeat it after each project ends and at least every quarter. AI tools create new previews and test apps fast, so the list changes fast.

Test what you found

A VibeEval scan tests a deployed URL from outside. Add each live app that you find as a target and read the findings by severity.

14-day free trial · Cancel anytime

SCAN YOUR APPS →