For developers, operators, security teams, and investigators
Use the suite for troubleshooting, migration checks, infrastructure research, and security review.
DNS and Infrastructure
Map how a domain resolves and what supports it
Query current DNS evidence, assess important controls, compare public resolver answers, discover observed subdomains, and add IP context.
Start with resolution, then deepen the investigation
Query records first, add control checks for posture, compare resolvers for inconsistent answers, and inspect related hosts or IPs when needed.
Inputs
DomainDNS nameIP addressMAC address
Outcomes
DiscoverEnrichMonitorAssessProtectCompareVerify
Current answers, resolver comparisons, and observations are not interchangeable
Use DNS Lookup for records, DNS Security for control posture, DNS Propagation for configured resolver differences, and Subdomains for observed names.
DNS Lookup
Perform DNS lookups for any record type.
Choose this when: Choose this for current DNS record answers and authoritative context for a domain or host.
- Inputs
- Domain, DNS name
- Outcomes
- Discover, Enrich, Monitor
- Credits
- 1-3
SynchronousRESTMCPSDKInteractive tool
DNS Security Analysis
Analyze DNS security configuration including DNSSEC, SPF, DKIM, DMARC, and other security records.
Choose this when: Choose this to review DNSSEC and other DNS-related security controls with evidence and limitations.
- Inputs
- Domain, DNS name
- Outcomes
- Assess, Protect
- Credits
- 3
SynchronousRESTMCPSDK
DNS Resolver Comparison
Compare answers from the Cloudflare and Google public recursive resolvers. These are two global-anycast DoH providers, not geographic probes or authoritative nameservers.
Choose this when: Choose this to compare answers from configured public recursive resolvers. It is not a geographic proof of global propagation.
- Inputs
- Domain, DNS name
- Outcomes
- Compare, Verify
- Credits
- 0-2
SynchronousBulkRESTMCPSDK
Subdomain Finder
Discover subdomains for a domain using various enumeration techniques.
Choose this when: Choose this to gather observed public subdomain evidence. A missing name does not prove that no subdomain exists.
- Inputs
- Domain, DNS name
- Outcomes
- Discover, Assess
- Credits
- 4-5
SynchronousBulkRESTMCPSDKInteractive tool
IP Geolocation
Get geolocation data for an IP address including country, city, and ISP.
Choose this when: Choose this to add network, location, and ownership context to an IP address where public evidence is available.
- Inputs
- IP address, Domain
- Outcomes
- Enrich, Assess
- Credits
- 1
SynchronousRESTMCPSDKInteractive tool
MAC Address Lookup
Look up manufacturer information for a MAC address.
Choose this when: Choose this to map a MAC address prefix to published vendor-allocation evidence, not to identify a device owner.
- Inputs
- MAC address
- Outcomes
- Enrich, Verify
- Credits
- 0-1
SynchronousRESTMCPSDKInteractive tool
Workflows
Capture expected records, compare configured public resolver answers, then review security controls and remaining inconsistencies.
DNS migration review
Capture expected records, compare configured public resolver answers, then review security controls and remaining inconsistencies.
Infrastructure discovery
Start from a domain, gather current records and observed subdomains, then enrich the resulting IP addresses.
Explain differing DNS answers
Request A, AAAA, MX, NS, TXT, or other supported records, then compare configured resolver responses for the records that matter.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/dns?domain=example.com&type=A"Example Response
{
"domain": "example.com",
"record_type": "A",
"records": [{ "type": "A", "name": "example.com", "data": "93.184.216.34", "ttl": 300 }],
"status": "success"
}Query one host or assemble a repeatable investigation
Use synchronous endpoints for targeted questions, supported batch requests for lists, or the infrastructure-discovery and DNS-migration recipes for a documented path.
SynchronousBulkRESTMCPSDKInteractive tool
A DNS snapshot is time-bound evidence
Resolver caches, delegation, record TTLs, network failures, and source coverage can produce different or incomplete observations.
Related solutions
Review DNS posture before and after a change
Combine current records, security-control evidence, resolver comparisons, certificates, and email authentication into an operational review.
Keep portfolio decisions tied to current domain evidence
Combine profile, lifecycle, health, pricing, valuation, watchlist, and batch products into a repeatable portfolio review.
Assess email risk and sending-domain posture before you act
Combine address-level signals with domain-level mail authentication, compliance, DNS, and blacklist evidence.
Follow a domain into the public infrastructure around it
Start with one domain or host, collect current resolution evidence, and pivot through observed relationships that matter to the investigation.
Follow the domain from record to infrastructure
Begin with DNS Lookup, then add only the resolver, security, subdomain, or IP context the investigation needs.