{"id":27306320,"url":"https://github.com/compcode1/nmap-tracert","last_synced_at":"2025-04-12T03:59:29.978Z","repository":{"id":286162392,"uuid":"960524689","full_name":"Compcode1/nmap-tracert","owner":"Compcode1","description":"Tracert works by sending packets with increasing TTL values, allowing us to discover each hop along the path to a target. We will use this behavior to analyze a real-world path and draw conclusions about the route's structure.","archived":false,"fork":false,"pushed_at":"2025-04-04T17:05:18.000Z","size":25,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-04-12T03:59:25.840Z","etag":null,"topics":["nmap","tracert"],"latest_commit_sha":null,"homepage":"","language":"Jupyter Notebook","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Compcode1.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-04-04T15:27:27.000Z","updated_at":"2025-04-04T17:05:41.000Z","dependencies_parsed_at":"2025-04-04T18:22:34.756Z","dependency_job_id":"32a01729-7c1d-4281-856b-29fbe96ba622","html_url":"https://github.com/Compcode1/nmap-tracert","commit_stats":null,"previous_names":["compcode1/nmap-tracert"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Compcode1%2Fnmap-tracert","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Compcode1%2Fnmap-tracert/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Compcode1%2Fnmap-tracert/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Compcode1%2Fnmap-tracert/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Compcode1","download_url":"https://codeload.github.com/Compcode1/nmap-tracert/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248514197,"owners_count":21116900,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["nmap","tracert"],"created_at":"2025-04-12T03:59:29.248Z","updated_at":"2025-04-12T03:59:29.962Z","avatar_url":"https://github.com/Compcode1.png","language":"Jupyter Notebook","readme":" The goal of this project was to use the Windows tracert command to:\n\nVisualize the network path (hops) from a local system to google.com\n\nObserve how TTL (Time To Live) expiration reveals intermediate routers\n\nIdentify latency spikes, timeouts, and potential firewalls or filtering\n\nUnderstand how network segmentation or hardened infrastructure impacts visibility\n\n**What Was Discovered:**\n\nHop 1 (Local Router) did not respond to ICMP-based traceroute, confirming that TTL-expired ICMP Echo Requests are filtered — a common default in consumer and ISP routers. However, a follow-up Nmap TCP-based traceroute confirmed that the router was functional and simply applying protocol-specific filtering, an important real-world security behavior.\n\nHops 2–6 responded reliably, though occasional jitter (e.g., Hop 5) suggested normal queuing behavior rather than performance issues. These hops reflect the ISP backbone infrastructure and regional peering points.\n\nHop 7 returned only one of three probes, suggesting ICMP rate-limiting or packet filtering, likely marking a firewall inspection point or hardened router.\n\nHops 8–10 were stable and responsive, consistent with Google’s internal edge network — indicating well-optimized cloud infrastructure.\n\nHop 11 was the final destination, a Google edge server in San Francisco, confirming Anycast routing and a clean path with low latency and no packet loss.\n\nKey Takeaways:\nTTL-based tools like tracert can expose a great deal about network structure, latency patterns, and filtering behaviors — even when IP hostnames are unavailable.\n\nDifferent tools (ICMP vs. TCP traceroute) reveal different visibility levels, which is critical for security analysis and infrastructure testing.\n\nIPv6 routing is widely adopted (as seen in this project), and its format, compression, and allocation are worth understanding for modern network analysis.\n\nConcepts like jitter, rate-limiting, and backbone routing emerged naturally from the data, providing rich insight into how real-world internet routing behaves.\n\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcompcode1%2Fnmap-tracert","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcompcode1%2Fnmap-tracert","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcompcode1%2Fnmap-tracert/lists"}