Security at Domain IP Lookup
The service is designed for public DNS resolution, not port scanning, internal-network probing, or origin discovery. These controls describe the protections implemented around that narrow use case.
Input validation
Domains are normalized and malformed values, IP literals, oversized labels, and unsupported inputs are rejected before resolution.
Public-address filtering
Resolved addresses are checked against private, loopback, link-local, and cloud-metadata ranges before they are returned.
DNS rebinding protection
The address returned by DNS is validated rather than trusting the hostname alone, including when a hostname changes between lookups.
Timeouts and retries
Resolver timeouts prevent requests from hanging indefinitely. Transient DNS failures are retried with bounded backoff, while permanent failures fail fast.
Rate limiting and job limits
Single requests and bulk job creation are rate-limited, and bulk caps limit resource use and help prevent abuse.
Data handling
Lookups do not require an account. Bulk job data is retained only as required by the job and export workflow described by the service.
Security boundaries
- Only public DNS resolution is performed; the service does not connect to returned addresses.
- A DNS answer can change after the lookup because of TTLs, failover, CDNs, or geographic routing.
- Rate limiting is process-local by default. Multi-instance deployments should use a shared store such as Redis.
- Deployment firewalls, TLS, and hosting availability remain operational responsibilities outside the lookup code.
Responsible disclosure
If you find a security issue in the service, contact the address listed on the Contact page with reproduction details. Please avoid sending secrets or personal data.