Enter company websites and get one row per site with the emails, phone numbers, social profiles, company name and address the company publishes on its own website, each with the page it was found on; checks contact, legal notice (Impressum) and about pages in many languages; only company websites, robots.txt respected. Not affiliated with the websites checked
Domain & Website Background Check
Enter domains or website addresses and get one row per domain: registrar, registration and expiry dates, domain age, status, name servers, the registrant organisation when the registry publishes it, whether the website still opens, and where it redirects (live, parked or for sale, redirected to another domain, error, unreachable). Covers 1,200+ domain endings including .cn, .de, .jp, .io and .hk. Data from the registries' public RDAP and whois services; not an official product of any registry
Overview
Find out who is behind a website and whether it is still in use. Give a list of domains or website addresses and get one row per domain: the registrar, when the domain was registered and when it expires, how old it is, its status and name servers, the organisation that registered it when the registry publishes it, and what happens when you open the site today: it works, it now redirects to another company, it is a parked or for-sale page, or it no longer answers.
Registration data and website status usually live in two different tools. Here they come back in one row, so a list of company websites can be cleaned in one pass: drop the dead and parked ones, follow the ones that moved to their new domain, and spot domains registered only weeks ago. The final domain after redirects can go straight into a contact-details lookup.
Over 1,200 domain endings are covered, including country endings that many whois tools miss, such as .cn, .de, .jp, .io, .hk, .ru and .eu.
Data notes
- Registration data comes from the public RDAP and whois services that domain registries publish and anyone can query for free. This app provides a lookup and organising service: it finds the right registry for each domain, queries it and turns the answer into the same columns for every ending, ready for programs and AI. The fee covers servers, network and maintenance, is charged per domain looked up, and is not a charge for the data. This app is not an official product of any registry and is not affiliated with them; the registries' own records prevail.
- Registries publish different amounts: .de and .eu give no registration or expiry dates, and most registries hide registrant details. The registrant organisation is filled only when published (common for .cn, .jp, .hk and company-owned domains). Personal names, email addresses and phone numbers are never returned.
- Dates are calendar dates (YYYY-MM-DD). Domain age and days to expiry are counted from the day of the check.
- The website check opens the homepage once, follows redirects and respects robots.txt; it does not log in or get past human checks. A site that blocks automated visitors shows as refused, which usually means it is running. Reachability is checked from a US data center at that moment: a site unreachable from there may still work elsewhere.
- Parked means the domain's name servers belong to a parking service, it sends visitors to a domain marketplace, or the page says the domain is for sale; the reason is given in the website note.
What the results look like
| Input | Registrar | Registered on | Expires on | Domain age (days) | Registrant organisation | Website state | Final domain |
|---|---|---|---|---|---|---|---|
| https://www.apify.com/store | Amazon Registrar, Inc. | 2009-06-02 | 2035-06-02 | 6375 | live | apify.com | |
| baidu.cn | 互联网域名系统北京市工程研究中心有限公司 | 2003-03-17 | 2029-03-17 | 8644 | 北京百度网讯科技有限公司 | robots_disallowed | baidu.cn |
| mozilla.com | MarkMonitor Inc. | 1994-10-18 | 2027-10-17 | 11716 | redirected_away | firefox.com |
Use cases
- Clean a lead list: remove domains whose site is unreachable, parked or for sale, and replace the ones that redirect with their final domain before looking up contact details.
- Check a supplier, merchant or partner: a domain registered a few weeks ago, about to expire, or parked is a warning sign worth a second look.
- Watch a set of domains: sort by days to expiry to see which registrations are about to lapse, or rerun regularly to see sites go dark or move.
- Research a market: see which competitor domains still run their own site and which now point to an acquirer.
Scope and boundaries
Up to 200 domains per run; a full web address is reduced to its domain. Registration data comes from each registry's public RDAP service, or whois where a registry has no RDAP; some registries publish little (for example .eu has no dates) and most hide registrant details, so the organisation is filled only when published, and personal names, emails and phones are never returned. The website check opens the homepage once from a US data center, follows redirects and respects robots.txt. Billed per domain whose registration lookup was answered (registered or not registered); lookups that failed, were rate-limited, unsupported endings and invalid inputs get a row but are not billed. The fee is a service fee for looking up and organising, not a charge for the data
- Good for
- Cleaning a list of company websites before outreach: drop domains that no longer open, are parked or for sale, or now redirect to another company, and get the real website (final_domain) to pass to a contact-details tool
- Checking whether a supplier, merchant or partner website is trustworthy: how old the domain is, when it expires, who registered it when public, and whether its name servers belong to a parking service
- Monitoring a portfolio of domains for upcoming expiry (days_to_expiry) or status changes
- Do not use for
- You need the domain owner's personal name, email or phone: these are never returned
- You need website traffic, technology stack or SEO metrics: use a traffic or SEO tool
- You need China ICP filing (备案) data: not covered
- You mainly want to find available names to register: possible (not_registered), but it is not built for name suggestions
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1Every input gets exactly one row. `status`: ok, not_registered, unsupported_tld, rate_limited, lookup_failed, invalid_input; only ok and not_registered are billed (`billed_domains` = 1)
- 2rate_limited and lookup_failed can be retried later; unsupported_tld means no public RDAP or whois source exists for that ending
- 3`site_state`: live, redirected_away, parked, refused (site answered but blocked automated access), http_error, unreachable, no_dns, robots_disallowed. `unreachable` describes the view from a US data center at that moment, not proof the site is gone
- 4Repeated domains are looked up once; the extra rows copy the result and are not billed
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- Domains or websites
domainsRequiredarray<string>Domain names or website addresses, up to 200, e.g. example.com, https://www.example.co.uk/about. A full address is reduced to its registrable domain (www.shop.example.co.uk → example.co.uk); internationalised names are accepted.Itemsup to 200 items - Check the website
check_websiteOptionalbooleanAlso open the homepage once to see whether it works and where it redirects. Turn off when you only need registration data (faster).Defaulttrue
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Input
inputstringThe domain or address as you entered itExamplehttps://www.apify.com/store - Domain
domainstringRegistrable domain checked, lower-case; internationalised names in punycode (xn--...). Empty for invalid inputExampleapify.com - Lookup status
statusstringRegistration lookup result: ok (data found), not_registered (registry has no record), unsupported_tld (no public RDAP or whois for this ending), rate_limited / lookup_failed (try again later), invalid_input. Only ok and not_registered are billedExampleok - Status note
status_textstringPlain-language explanation of the lookup statusExampleRegistration data found
Sample data
Generated from output.schema. Fields without a sample value use structural placeholders.
{
"input": "https://www.apify.com/store",
"domain": "apify.com",
"status": "ok",
"status_text": "Registration data found",
"registrar": "Amazon Registrar, Inc.",
"registered_at": "2009-06-02",
"expires_at": "2035-06-02",
"updated_at": "2026-05-16",
"domain_age_days": 6375,
"days_to_expiry": 3121,
"domain_status": "[\"client transfer prohibited\"]",
"domain_status_text": "client transfer prohibited",
"nameservers": "[\"ns-1225.awsdns-25.org\",\"ns-449.awsdns-56.com\"]",
"nameservers_text": "ns-1225.awsdns-25.org / ns-449.awsdns-56.com",
"registrant_org": "北京百度网讯科技有限公司",
"registration_source": "RDAP rdap.verisign.com",
"site_state": "live",
"site_state_text": "Opens normally (HTTP 200)",
"http_status": 200,
"final_url": "https://www.octoparse.com/",
"final_domain": "octoparse.com",
"redirect_chain": "[{\"url\":\"https://octoparse.com/\",\"status\":302},{\"url\":\"https://www.octoparse.com/\",\"status\":200}]",
"redirect_text": "https://octoparse.com/ (302) → https://www.octoparse.com/ (200)",
"page_title": "AI Web Scraping Tool & Web Data Platform",
"checked_from": "Los Angeles, US (data center)",
"billed_domains": 1
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=MagicData/domain-background-check",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)
detail.access.mcp.composeHint
Pricing
Metered by summing the output field billed_domains. Failed runs are not charged.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.