The Results Viewer is a separate application which can be used to view EnergyPlus results stored in one or more .eso files. It can be downloaded from the main Downloads > Software area of the DesignBuilder website. When installed the application allows you to view any results contained within EnergyPlus .eso and .htm results files. There are 3 ways to open .eso results files:

Multiple .eso and .htm files can be opened at a time. Use the combo box below the toolbar to select the current results set for plotting.

To show results for a particular interval use the Frequency drop list to select the interval.

Sorting the Reports can be a useful way to help find particular data and can be achieved by clicking on the column headers. For example to see data sorted by "Area" click on the Area header. This will collect together all data for each zone, HVAC component, Environment etc. in the list.

If you have more than 1 graph set up you can select the current graph simply by clicking on it. You will see the graph heating highlight in a different blue when selected as shown below.

You can access a range of options from the top bar menu, toolbar and right-click context menus. These are as follows:

Allows you to save the data as a comma separated values file for loading into a spreadsheet for further analysis.

If you have generated similar data for multiple frequencies then use this tool to use settings for the current frequency and display the same reports using a different frequency.

Allows you to change the title for the currently selected graph. To change the name of the current graph right-click on the graph and from the DesignBuilder Options, select the Rename graph title option. Enter the title for the graph in the dialog and press OK.

Checking this option displayed a cross hair which allows you to create a vertical and horizontal line when you click on a data point. It can be useful to check simultaneous values for a range of reports.

When you create graphs with Results Viewer, they are styled (e.g. Title Font, Background colour, etc) using a default styling template. You can change the styling defaults to your own preferences by using the right-hand context menu on the graph pane. The following options are currently available:

If you make some changes and want to revert back to the default styling at any time, select the Tools > Restore Graph Styling menu option.

Any styling changes made to the currently open session will be made permanent once the session has been saved.

If you wish to reuse your styling changes, you can save these to a styling template file and apply them to other sessions. Use the Tools> Template > Save option to save your styling template as a standalone file, ie outside of the session (note: the '.drt' file extension is used for styling template files). The Tools > Template > Load option can then be used to apply this style to another session.

You can load as many data sets as required to a single Results Viewer session by using the Open eso/Dataset menu or toolbar option. A list is maintained of all data sets currently opened in the drop list at the top of the window.

The Options dialog is accessed either from the toolbar

or from the Tools top menu option.

Select this option if you would like the session to be saved automatically when closing the Results Viewer.

Selecting this option causes the title of each graph to be displayed for each graph as shown in highlighted areas in the graph below.

To change the name of the current graph right-click on the graph and from the DesignBuilder Options, select the Rename graph title option. Enter the title for the graph in the dialog and press OK.

If you have more than one data set loaded then you should usually select this option to ensure that the data set name is included in the legend. This can help when comparing results for different simulations.

If you include the dataset name in the legend then do you want the folder name included too? If so check this option. This option is only usually used when the result sets are stored in files with the same name but in different folders.

In some cases you may find that too much data is displayed on the X-axis at one time and you need to focus on a section (time period) of the results graph. You can use the mouse to do this simply by dragging a time region of interest. This allows you to zoom in on data for particular days.

To return back to the original "un-zoomed" state, use the Undo zoom toolbar option.

It can take some time to load.eso files and to select results so DesignBuilder provides methods to save pre-processed results files and session files to speed loading and setting up reports the next time.

When the Results Viewer loads an .eso file it automatically generates a .drb file with exactly the same data but in a form that can be loaded much more quickly. If you need to view the results again in future you can open the drb file instead of the .eso file. The .drb file will have the same filename as the original .eso file (apart from the extension). It does not contain any display settings - just the data.

You can also save a session file which stores all of your display settings for a graphing session as well as the corresponding .drb file(s). Opening the session file will take you back to where you were before saving the session file. Session files provide a very useful way to package up all data and settings for a Results Viewer session in a small file size. They can be sent to colleagues for viewing.

You can configure DesignBuilder to save.eso files in various ways as described for the EnergyPlus tab of the Program options. If you plan to use the Results Viewer in favour of the inbuilt DesignBuilder results display then you might use one of the settings configurations below:

Axis Video Serveradds 1 Top ~upd~ - Inurl Indexframe Shtml

The Danger of Google Dorks: Understanding "inurl:indexFrame.shtml Axis"

In the world of cybersecurity, sometimes the most powerful tool is a simple search bar. You might have seen the string inurl:indexFrame.shtml axis video serveradds 1 top and wondered what it meant. This isn't just a random set of words; it’s a Google Dork, a specialized search query used to uncover vulnerable devices exposed to the public internet. What is this Google Dork?

The term "Google Dorking" (or Google Hacking) involves using advanced search operators to find specific information that isn't intended for public viewing.

This specific dork targets Axis Network Cameras and video servers. Here is how the components break down:

inurl:indexFrame.shtml: This tells Google to look for pages where the URL contains this specific filename. indexFrame.shtml is a common control or "Live View" page for older Axis IP cameras.

Axis: Filters results to ensure the brand associated with the page is Axis Communications.

video serveradds 1 top: These additional parameters help refine the search to specific server configurations or administrative headers often indexed by search crawlers. Why is this a Security Risk?

When a security professional or a hobbyist runs this search, they aren't just finding a website; they are finding live video feeds. Many of these cameras were installed with "plug-and-play" simplicity, meaning they often retain their default factory settings.

Default Passwords: Older models often used predictable default credentials (like root / pass), which attackers can try immediately once they find the login page.

Privacy Leaks: These cameras might be located in private offices, warehouses, or even homes. Unsecured feeds allow anyone with the link to watch real-time footage without the owner's knowledge.

Device Hijacking: Beyond just watching, attackers may attempt to gain "system-level access" to the internal network the camera is connected to, potentially using the camera as a bridge to other sensitive systems. How to Secure Your Axis Devices inurl indexframe shtml axis video serveradds 1 top

If you own or manage IP cameras, you can protect them by following the AXIS OS Hardening Guide and these essential steps: AXIS Camera Station 5 - User manual

The text you provided is a known Google Dork, a specific search string used by security researchers (and sometimes malicious actors) to find publicly accessible Axis Video Servers and cameras on the internet. Breakdown of the Query:

inurl:indexframe.shtml: Searches for websites that have this specific filename in their URL, which is a common component of the Axis web interface.

"axis video server": Limits results to pages containing this exact phrase, identifying the hardware type.

adds 1 top: This appears to be a fragment sometimes found in the HTML source or metadata of specific older firmware versions of these devices. Purpose and Risk

Researchers use these strings to identify vulnerable IoT devices that have not been properly secured with passwords or firewalls. If you own an Axis device, it is highly recommended to: Change default passwords immediately. Update the firmware to the latest version.

Use a VPN or firewall to restrict access to the device rather than exposing it directly to the public web. Are you trying to secure your own Axis device, or

Подключаемся к камерам наблюдения - Habr

inurl:"ViewerFrame? Mode= intitle:Axis 2400 video server. inurl:/view.shtml. intitle:"Live View / — AXIS" | inurl:view/view.shtml^

Cameras-Long.txt - inurl: ViewerFrame?Mode= intitle: Live View The Danger of Google Dorks: Understanding "inurl:indexFrame

The query you provided is a Google Dork (an advanced search string) historically used to locate publicly accessible, unencrypted live feeds of Axis network security cameras on the internet. 🛡️ Why You Should Not Use These Strings

Unauthorized Access: Using these strings to view or manipulate private security cameras without permission may constitute a breach of privacy or computer crime laws (such as the CFAA in the US).

Cybersecurity Risk: Engaging in this type of scanning often places your own IP address on network logs and exposes you to insecure direct connections.

Obsolete Technology: Many of these strings refer to legacy .shtml pathways or outdated Active-X frames that have since been patched or discontinued by Axis Communications in favor of more secure technologies. 💡 How to Secure Your Axis Devices

If you own Axis devices and want to ensure they are not exposed to the public internet via Google dorking, follow these best practices:

Update Firmware: Regularly check for and install the latest firmware updates from the official Axis Communications Support Page.

Change Default Passwords: Never leave your admin or root credentials as the default manufacturer settings.

Disable Unused Protocols: Turn off server-side include scripts, anonymous viewing, and legacy web interfaces if they are not needed.

Use Secure Remote Access: Utilize AXIS Secure Remote Access rather than port-forwarding your cameras directly to the public web. AXIS P1368-E Network Camera

It is important to clarify from the outset: the search query inurl:indexframe.shtml "axis video server" (or variations like adding 1 top) is not a "hack," a backdoor, or an exploit in the traditional sense. Instead, it is a Google dork used to locate web-based management interfaces for AXIS Network Video Servers and older AXIS camera models. Proof of Concept (What an attacker sees) An

This article will break down exactly what this search means, why these interfaces appear in search engines, the security implications, how to find them (for ethical purposes), and how to secure your own devices.

Proof of Concept (What an attacker sees)

An attacker searching for this dork will likely encounter:

Live Feeds: A webpage with a frame containing a live video stream from a CCTV camera.
System Info: Text overlay or sidebars displaying:
- Server Date/Time
- Device Name (e.g., "Axis 240Q Video Server")
- Firmware Version (useful for finding known exploits)
Controls: Pan/Tilt/Zoom (PTZ) controls may be active if the attached camera supports it.

6. Ethical / Legal Note

Scanning for such devices without authorization is illegal in most jurisdictions.
If you’re a defender, use this footprint to find your own exposed cameras, or those of clients during authorized pentests.

Part 7: Why “Adds 1 Top” Persists in Hacker Forums

The extra text adds 1 top is likely a misinterpreted command from automated tools. In some older scraper scripts (e.g., Googler or PyGoogle command-line tools), arguments like --top 1 or --num 1 limit results. Someone likely typed adds 1 top as a comment or alias and others copied it blindly, thinking it was part of the dork.

It is functionally useless. The working dork is simply:

inurl:indexframe.shtml "axis video server"

Adding 1 top does nothing in Google; it only confuses new users.

Security Implications

Privacy Violation: Unauthorized viewing of private premises, sensitive industrial areas, or residential interiors.
Operational Security (OPSEC): Attackers can study security camera angles, blind spots, and guard patrol routes.
Botnet Recruitment: Axis devices are frequently targeted by malware (such as Mirai) due to default or weak credentials on the embedded Linux OS.

Part 4: Security Implications

Finding these devices is not illegal if you simply stumble upon them passively. However, interacting without authorization (e.g., attempting default logins, changing settings, viewing private video) violates laws such as the Computer Fraud and Abuse Act (CFAA) in the US and similar laws worldwide.

Risks for the Finder

Criminal charges – Even accessing a login page without permission is legally gray; attempting to log in is clearly illegal.
Honeypots – Security researchers and law enforcement sometimes monitor dorks to catch unauthorized access attempts.

5. Current State (2026)

Most modern Axis cameras no longer use indexframe.shtml.

Newer interfaces use .cgi, .asp, or JavaScript SPA.
Many Axis devices now require HTTPS and disable default unauthenticated access.
However, older models are still online, often in industrial sites, small businesses, or homes.

Shodan shows thousands of results for indexframe.shtml as of 2026, many in countries like USA, Brazil, India, Germany.