Loading
Loading
The endpoint, and step-by-step guides for the lookups you run most.
Explore the complete API reference with detailed request parameters, response fields, error codes, and code examples: visit API Reference.
You've got a domain and need to know who's behind it, when it was registered, and when it expires: the first question in almost every abuse investigation and due-diligence check. One GET returns the full parsed record plus the raw text. This is also the fastest way to use the service as a WHOIS lookup API inside an enrichment pipeline: one input field, one structured result.
Threat feeds, message logs, and user reports hand you full URLs, not clean domains. Skip the pre-parsing step: pass the URL (URL-encoded) straight into the same parameter and the API extracts the domain before running the live lookup, one less place for a normalization bug to hide.
Before shortlisting a name for a project or flagging a typo-squat that doesn't exist yet, check whether the domain is registered at all. An unregistered domain returns a normal response with the registration flag set to no and most fields omitted, no error-handling branch required, and the successful lookup is the only thing you're charged for. When availability is the whole job, checking many candidate names with TLD suggestions, the Domain Availability API is the purpose-built path.
Response walkthrough: domain_registered returns "no" and the contact, registrar, and date fields are omitted.
Production WHOIS pipelines fail in two predictable places: redacted contacts and exotic extensions. Privacy-protected domains still return a 200, the record is parsed as published, so redacted contact fields come back exactly as the registry and registrar return them, with the registrar's own contact details included when available; route those to a manual queue rather than treating the instruction text as a usable email address. Unsupported extensions return a 403 and malformed input a 400; neither consumes credits, so retry logic stays simple.