Consolidate evidence
Normalize supported DNS zone files, CSV exports, JSON/JSONL host results and hostname lists.
Browser-local reconnaissance workspace
Know what you own.
See what changed.
Merge DNS and discovered-host exports into an evidence-backed asset inventory. Compare two snapshots, review changes, and download your findings—without uploading your files.
◉ Browser-local files◉ No account◉ Evidence-based reports
Private workspace
Compare asset evidence
Use exports for systems you own or are authorized to assess. Files are parsed in your browser; this page makes no live DNS requests.
LOCAL WORKSPACE
No login · No uploads · No background scanningWhen set, out-of-scope names are excluded with a warning. Leave blank to compare mixed inventories.
SNAPSHOT A · BASELINE
Before
Older zone export or discovery results.
- No files selected
SNAPSHOT B · CURRENT
After
Current exports to consolidate and compare.
- No files selected
Supports a documented BIND-style zone subset, normalized CSV, JSON/JSONL host objects and one-hostname-per-line TXT. Maximum 5 MB/file, 30,000 records/file. Supported formats and limits.
recon.ph
Technical asset comparison report
Comparison results
What changed?
Baseline hosts0
Current hosts0
Added hosts0
Removed hosts0
Record changes0
| Change | Hostname | Type | Value | Evidence |
|---|
| Change | Hostname | Type | Value | Evidence |
|---|
Import notes and limitations
A new or missing record reflects differences in supplied evidence, not a confirmed security issue or proof of current internet exposure. Check collection time and source coverage before acting.
How it works
From scattered exports to a usable record.
Reconnaissance starts with a defensible inventory. Compare like-for-like snapshots and retain the inputs that explain each finding.
Compare snapshots
Identify new, removed and changed hosts or DNS records, with source provenance and explicit limitations.
Export and verify
Download an inventory, change report or snapshot JSON for repeatable analysis.
Guides
Interpret the evidence.
How to export a Cloudflare DNS zone for asset review
Export DNS records from Cloudflare's dashboard or authorized API, preserve the original zone file, and compare two snapshots in Recon.ph.
Read guide ↗How to export a GoDaddy DNS zone file
Download a GoDaddy-managed DNS zone, identify its BIND records, and compare a baseline with a later export without changing DNS.
Read guide ↗Collect DNS evidence on Linux, macOS and Windows
Use dig on Linux or macOS and Resolve-DnsName on Windows to collect scoped public DNS answers and produce a Recon.ph-compatible CSV.
Read guide ↗Export DNS evidence from Azure DNS and Amazon Route 53
Export an Azure DNS zone file or Route 53 record-set JSON, understand format differences, and prepare a supported Recon.ph CSV input.
Read guide ↗How to review a DNS zone export before import
Prepare a BIND-style DNS export for asset comparison: understand origin, relative names, record values and import limitations.
Read guide ↗Worked example: compare two DNS snapshots
Reproduce a before-and-after DNS comparison, interpret two host changes and four record changes, and avoid false security conclusions.
Read guide ↗REPEATABLE INVESTIGATION
Make the next comparison easier.
Download example exports and a reusable inventory template; understand every normalization and matching decision.