Enter a domain, URL, IP, email, or record and get a focused result without setup.
Domain Profile Viewer
We show registrar information, registration and expiration dates, nameservers, DNSSEC status, and contact details (when publicly available). Data is fetched from RDAP servers.
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at these companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Check live service health and documented failure responses before you integrate.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Key Features
We show registrar information, registration and expiration dates, nameservers, DNSSEC status, and contact details (when publicly available). Data is fetched from RDAP servers.
ICANN requires gTLD registries and registrars to provide RDAP, which became the definitive source for gTLD registration information on 28 January 2025. This transition applies to gTLDs; requirements for ccTLDs vary. DomScan uses RDAP where supported. Depending on the TLD and lookup, it may query WHOIS directly or use WHOIS when RDAP is unavailable. Records can omit fields or redact contact details, so treat them as published registration data, not independent proof of a person's identity.
Due to GDPR and privacy regulations, most domains now use redacted WHOIS/RDAP data. Contact information is typically only available for corporate registrations or specific TLDs.
Example request
GET /v1/profile?domain=example.com
Example response
{
"domain": "example.com",
"nameservers": ["a.iana-servers.net"]
}
Built on the same API
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently asked questions
We show registrar information, registration and expiration dates, nameservers, DNSSEC status, and contact details (when publicly available). Data is fetched from RDAP servers.
ICANN requires gTLD registries and registrars to provide RDAP, which became the definitive source for gTLD registration information on 28 January 2025. This transition applies to gTLDs; requirements for ccTLDs vary. DomScan uses RDAP where supported. Depending on the TLD and lookup, it may query WHOIS directly or use WHOIS when RDAP is unavailable. Records can omit fields or redact contact details, so treat them as published registration data, not independent proof of a person's identity.
Due to GDPR and privacy regulations, most domains now use redacted WHOIS/RDAP data. Contact information is typically only available for corporate registrations or specific TLDs.

