Tidal Analyze Web
Now that you have discovered your FQDNs for your specified Discovery Plan, the next step is to rapidly capture what technologies are in use, on which networks and with what DNS configuration.
Tidal Analyze Web will fingerprint the technology on both your internet sites and intranet applications behind your firewall in seconds, without needing to install agents. Whether you have one or one million end points, Tidal Tools will centralize the data gathered in our platform for you to analyze.
Simplify your application centric discovery with Tidal Analyze Web.
Gathering your domains and URLs
Simply save a list of URLs or FQDNs in a text file and use that as input.
Or use the discovery command to scan your network and DNS to gather a list of relevant domains.
Analyzing FQDNs and URLs
Now that we have our relevant domains and URLs in my_urls.txt, we can analyze them with:
tidal analyze web my_urls.txt --upload
tidal discover
my_plan.yml | tidal analyze web --upload
--upload
flag, continue on and then
checkout the Uploading to your account section below.Uploading to Tidal API
After recieving the results of Tidal Analyze Web, you may or may not be connected to the internet.
If you are so, you can import it to your Tidal account with the following flag:
tidal analyze web my_urls.txt --upload
If you aren’t connected to the internet, you also have the option to save the results in a JSON file to import at a later time. This can be done with the following steps:
-
Run this command to run the analysis and save the results to the file analyze_output.json:
tidal analyze web my_urls.txt --type json > analyze_output.json
- Copy the file, analyze_output.json and install Tidal Tools, on a computer with internet access.
- Login to Tidal Tools with
tidal login
-
Run this command to upload your previously generated data to your Tidal Migrations account:
tidal analyze web --upload-file analyze_output.json
Accessing your domains in the Tidal API
Once you have imported the results to the Tidal API, your domains will appear on the right hand side navigation bar under
Assess > URLs.
Troubleshooting
It looks like the server did not respond for 10 seconds
If you got this error message you can try to increase the waiting time using the
--timeout
flag and the amount of seconds (default is 10
). For example,
--timeout 30
sets the time waiting for the server to respond to 30 seconds.