DPULSE report storage database
Report storage Database is a database designed for the permanent storage of reports generated after each DPULSE scan.
DPULSE generates a report and puts it in a separate folder. This is a common way to interact with a report. However, in cases where you need to store your reports for a long time or move them at once to another device - report storage data may be a better alternative.
So, report storage database is a simple .db file which is located in DPULSE root directory with report_storage.db name. DPULSE generates this file when DPULSE is first launched if report_storage.db file was not found in the root directory, so users don't need to worry about it's manual creation.
Report storage DB consists of several fields, which you can see on the picture below:
Lets describe these fields in more detailed way:
- id - integer value that displays the number of reports generated and the order in which they are generated
- report_file_extension - string which shows main report file extension, in current DPULSE version this value could be xlsx, pdf or html
- report_content - BLOB or HTML data which contains main report file's copy
- comment - string which shows comment to your cases, which you can enter before each scan
- target - string which shows domain which you've scanned
- creation_date - string which shows when your report was generated (YYYYMMDD format)
- dorks_results - text array which contains a copy of Google Dorking results (if this mode was selected before scan)
- robots_text - text array which contains a copy of robots.txt file from scanned domain
- sitemap_text - text array which contains all sitemap.xml links file from scanned domain
- sitemap_file - text array which contains a copy of sitemap.xml file from scanned domain
First of all, after each scan you can see several messages which indicate that your report was successfully saved in report storage database:
Also, you have separate menu item in DPULSE CLI to work with DB which named "Report storage DB manager". Here you can see DB content and recreate report from DB:
