Submit a list of domains and get each one's public registration record back as a row - who the registrar is, when it was created, last updated and expires, the status codes protecting it, and the nameservers it points at. Eight columns, one stable shape, measured from real exports.
It is the one field people come looking for, and the reason it is blank has nothing to do with the scraper.
In all four exports behind this page - eight rows across two domains - registrant came back empty. That is not a gap we are papering over: it is what public WHOIS returns for almost every generic top-level domain today.
When GDPR came into force, ICANN adopted a Temporary Specification for gTLD Registration Data requiring registrars to redact the personal fields from public registration records - registrant name, organisation, email and postal address. Fields that are not personal data still appear, which is exactly the split our exports show: registrar, dates, status codes and nameservers all arrive populated, and the registrant does not.
So this page does not promise registrant details, and it will not suggest a way around the redaction. If you have a legitimate, documented need for the non-public data, the route is ICANN's Registration Data Request Service, not a scraper. What this service does give you is the other seven columns, and they are the ones that answer most real questions: who runs the domain, how old it is, when it lapses, whether it is locked, and where its DNS lives.
A domain is the entire input. There are no filters to configure.
Submit the registrable domain itself - stripe.com, github.com - rather than a full URL or a subdomain, since a registration record exists at that level.
Measured from 4 real exports covering 8 rows and 2 domains, all four runs identical. Names are copied byte-for-byte from the header row. Example values below are real cells from those runs.
stripe.com, github.com. Present on every row.SafeNames Ltd. for stripe.com, MarkMonitor Inc. for github.com. Both are corporate registrars, which is itself a signal.YYYY-MM-DD - 1995-09-12 and 2007-10-09. This is the domain's original registration, not when its current owner acquired it.2025-10-01, 2024-09-07. Moves on renewal, nameserver changes and contact edits.2027-09-11, 2026-10-09. The column to watch if you track lapsing domains.client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited. See the note below on what these mean.NS-1087.AWSDNS-07.ORG, NS-1882.AWSDNS-43.CO.UK, …. Reveals the DNS provider, and often the hosting stack behind it.Seven of eight columns carried real values on every row; the eighth is redacted by policy. The schema is unusually stable for this catalogue - one shape, the same eight columns in the same order, identical across four separate runs and between the JSON and the spreadsheet. The sample is deliberately not expressed as a percentage: two domains tells you the shape of an export reliably and nothing about coverage across unusual TLDs. Run a slice of your own list on the free tier, especially if it includes country-code domains, which vary far more in what their registries publish.
Each of these came out of reading the exports rather than a reference - there isn't one for this service, which is itself the fourth note.
created, updated and expires all arrive as YYYY-MM-DD in every row we hold, with no time component and no timezone. That is the friendliest format WHOIS data comes in, and it means a date comparison works without a custom parser. Note that created is the domain's original registration - stripe.com reads 1995-09-12, long before the company existed.
The values are EPP status codes: client transfer prohibited means the registrar has set a transfer lock, server delete prohibited means the registry has. They are protections against hijacking, so a long list is a well-secured domain rather than a problem. Split on the comma and test for membership - do not string-match the whole field, because the set differs per domain: six codes on stripe.com, three on github.com.
One field, several hosts, joined with a comma and returned in capitals - DNS1.P08.NSONE.NET, DNS2.P08.NSONE.NET, …. Split on the comma and lower-case before comparing, or the same nameserver will look like two different values. Count varies: four on one of our domains, eight on the other, and github.com's list mixes two providers, which is a real deployment detail rather than an error.
Several services in this catalogue quote a per-request batch size because their references publish one. This service has no endpoint documentation we can point at, so we do not quote a number - and you should treat any number you see elsewhere with the same suspicion. Start with a modest batch on the free tier and scale from what you observe.
Registration data answers questions about a domain that its website will not tell you.
expires across a list of domains turns renewal from a calendar risk into a sorted column. Add registrar and you can see how fragmented a portfolio has become - the usual finding on an inherited estate is three or four registrars nobody remembers choosing.
created gives you a domain's age, which is one of the more honest signals available about an organisation you have not dealt with before. A corporate registrar and a long lock list point one way; a domain registered last month points another.
nameservers names the DNS provider outright, and often implies the hosting stack behind it. Run it across a sector and you get a picture of what that market has standardised on - drawn from the domains themselves rather than from vendor case studies.
No subscription, no minimum, no per-seat licence. Your first 500 rows are on us - after that, pay-as-you-go.
Every new account, one-time. No credit card required. Worth spending some on the odd corners of your list - country-code domains especially, since registries differ in how much they publish.
Roughly $2 per 1,000 domains, one row per domain - exact to budget, because a domain whose record is sparse still returns exactly one row.
Volume pricing, SLAs, dedicated workers and bespoke onboarding for teams re-checking a large domain portfolio on a schedule. Tell us your numbers and we'll quote.
LIVESCRAPER10 at checkout.This tells you who registered it. These two tell you what it runs and who is behind it.
What the site is built with - CMS, ecommerce platform, analytics, CDN and web server. Registration data and technology stack together describe a domain far better than either alone.
Firmographics from the same input - name, industry, headcount, founded year, revenue, address and socials. The organisation behind the domain, rather than the registration behind it.
Domain registration data is published on purpose, and the part that was personal has already been removed before we ever see it.
WHOIS exists because the domain name system needs a public record of who is responsible for a domain. Registrar, dates, status codes and nameservers are administrative facts about an internet resource - not personal data - and they are published by design.
The personal half of that record is already gone by the time a public query reaches it. ICANN's post-GDPR policy requires registrars to redact registrant name, organisation, email and postal address from public WHOIS, which is why registrant is empty in every row we hold. We do not attempt to defeat that, and you should be wary of any service that claims to. Where there is a genuine, documented need - trademark enforcement, security research, law enforcement - ICANN operates a request service for exactly that purpose.
One honest caveat: on a small personal domain, a registrar name and a registration date can still narrow things down about an individual, and country-code registries make their own rules about what to publish. Treat unusual TLDs with the same care you would give any other record about a person. On our side: publicly available sources only, nothing behind a login, no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
domain, registrar, created, updated, expires, status, nameservers and registrant. In our runs the first seven carried real values on every row and the eighth was redacted. One shape, the same order in every run and in both the JSON and the spreadsheet.YYYY-MM-DD, with no time component - 1995-09-12, 2027-09-11. That holds for created, updated and expires in every row we hold, so date comparisons work without a custom parser.1995-09-12, long before the company existed, because the domain was registered by someone else and acquired later. Treat created as the age of the domain, not the age of the business behind it.client transfer prohibited means the registrar has set a transfer lock; server delete prohibited means the registry has. They protect against hijacking, so a long list indicates a well-secured domain rather than a problem. Split the field on the comma and test for membership - the set varies, six codes on one of our domains and three on the other.Paste your domains and get the registrar, the dates, the lock status and the nameservers for each one. Your first 500 rows are free - enough to check the odd corners of your portfolio before you commit.
Every domain name carries a public registration record: who the accredited registrar is, when the domain was first registered, when the record last changed, when it expires, which protective status codes are set on it, and which nameservers it delegates to. Reading that one domain at a time is a chore; reading it across a portfolio, a supplier list or a competitive set is where it becomes useful. This service does that in bulk - submit domains, get one row each.
The export carries eight columns and, unusually for this catalogue, has exactly one shape: the same eight names in the same order across four separate runs, and no disagreement between the JSON and the spreadsheet versions of the same file. Seven of them carried real values on every row we hold. The dates arrive as clean ISO YYYY-MM-DD with no time component, which means a comparison works without a custom parser. The status field is a comma-joined list of EPP status codes - transfer locks, delete locks and update locks set by the registrar or the registry - so it should be split and tested for membership rather than string-matched, since the set varies per domain. The nameservers field is likewise comma-joined and returned in capitals, and it names the DNS provider outright, which often implies the hosting stack behind it.
The eighth column is the one worth explaining rather than reporting. Registrant came back empty in all eight rows, and that is a policy outcome rather than a scraping failure. When GDPR came into force, ICANN adopted a Temporary Specification for gTLD Registration Data requiring registrars to redact the personal fields - registrant name, organisation, email and postal address - from public WHOIS, while fields that are not personal data continue to be published. That is precisely the split the exports show. This page therefore does not promise registrant details and will not suggest a way around the redaction; where there is a genuine documented need, such as trademark enforcement or security research, ICANN operates a request service for exactly that. One further point for whoever writes the importer: this service has no published endpoint reference, so no per-request batch limit is documented and this page deliberately quotes none.
The uses that remain are the ones most people actually want. Expiry dates across a list turn renewal from a calendar risk into a sorted column, and registrar names reveal how fragmented an inherited portfolio has become. Creation dates give an honest signal about how established an unfamiliar organisation is - though note that the date is the domain's original registration and not when its current owner acquired it, which is why stripe.com reads 1995-09-12. Nameservers mapped across a sector show what that market has standardised on, drawn from the domains themselves. On the legal side this is a public administrative register whose personal half has already been removed before any query reaches it; the caveat worth keeping in mind is that on a small personal domain a registrar and a date can still narrow things down, and country-code registries set their own publication rules. Publicly available sources only, nothing behind a login, no third-party trackers on the data layer, and exports auto-delete after 30 days. Your first 500 rows are free and need no credit card.