Echo IP Counter

About Echo IP Counter

Echo IP Counter is a small public web application from ASE Team. It exists to demonstrate a reachable HTTPS service, a live visitor dashboard, and a simple server-side analytics flow. The page is intentionally focused on one task: showing which public IP addresses have reached this URL and how often the main page has been loaded.

The dashboard counts unique visitor IP addresses, total page hits, visits seen during the last hour, returning IPs, and the most active IP address. The visitor table lists the first time an IP was seen, the most recent time it loaded the page, the last requested path, and the most recent user agent string reported by the browser or client.

This root URL is the canonical public page for the demo. It is designed to be understandable without logging in, opening a separate document, or relying on client-side rendering. The live controls remain available above this section, while this text gives search engines, Microsoft Copilot, and human visitors a stable description of what the page does.

Data Handling and Privacy

Echo IP Counter stores a compact record for each IP address that loads the main page. The stored fields are the IP address, first seen time, last seen time, hit count, last path, and latest user agent. The app does not ask for names, email addresses, passwords, payment details, or account information.

The reset control clears the current visitor table and removes the stored visit history from the demo database. The CSV export returns the same visitor fields shown in the table so the data can be reviewed outside the browser. Because IP addresses can be sensitive, this temporary page should be treated as a public demonstration rather than a long-term production analytics product.

Technical Details

The service runs on an AWS-hosted Ubuntu server behind Nginx. Nginx terminates HTTPS for echo.ase-team.com and forwards requests to a lightweight Python application on localhost. The application uses SQLite for persistence and renders the main HTML page from the server, so the primary title, description, headings, and documentation are present in the initial response.

The dashboard avoids counting its own background API polling as page visits. Only main page loads are counted as visitor hits. API responses are used for live refresh, reset, and CSV export, while the root page remains the stable indexable URL.