Submit company domains and get ZoomInfo's record for each one - the company name and website, industry, headcount, revenue band, phone, location and ticker. That is what the export declares. What our own runs actually returned is a different story, and it is on this page rather than hidden.
This is the most important thing on the page, and putting it after a feature grid would be dishonest.
We hold five real exports of this service. Four of them returned a single row in which company_name and zoominfo_url were empty and status read, word for word: “blocked (ZoomInfo is paid/protected - needs residential proxy + account)”. The fifth returned no rows at all. Not one company field has ever arrived.
Those runs also show two different schemas, and the difference is the whole story. The four blocked runs use a four-column envelope - domain, company_name, zoominfo_url, status - which is a wrapper for reporting the outcome rather than a company record. The earliest run carries a completely different, fourteen-column header: query, company, website, phone, employees, revenue, industry, founded, address, city, state, country, ticker and logo. That run has a header and nothing underneath it.
So the fourteen columns in the data dictionary below are what an export declares, and none of them has been observed holding a value. The reason is not mysterious and our own status column names it: ZoomInfo is a paid platform that gates its data behind an account. We publish the column names because the header declares them, we report the blocked status because that is what we received, and we are not going to describe results we have not seen.
A company domain is the entire input. There are no filters to configure.
status column first.Submit the registrable company domain - stripe.com rather than a full URL or a subdomain. Start with a handful: status will tell you what you are getting back before you spend on a large batch.
These names are copied byte-for-byte from an export header. That header appeared with no rows beneath it, so every description below says what the column is for, not what we have watched it hold.
Fourteen names, no values. This header came from a run that produced no rows, and every other run we hold returned a four-column status envelope instead - domain, company_name, zoominfo_url and status - with the two data fields empty and the status reporting a block. So there are no fill rates on this page, no example values, and no claims about formats: not whether employees is a number or a band, not what founded looks like, not how often ticker is populated. Your one-time 500 free rows are the first real test, and on this service that is genuinely the advice rather than a formality.
Because every export we hold is blocked or empty, these are open questions rather than findings - and they are the ones worth answering before you build anything.
It is the column that tells you which of the two shapes you received. A four-column row with an empty company_name is a report about the request, not a company with a missing name. Branch on status first, and only then look for data fields - otherwise a blocked run will quietly populate your database with blank companies.
The runs we hold contain a four-column envelope and a fourteen-column company header, and they share no field names at all - the envelope calls the domain domain while the wide header calls it query. An importer that assumes one shape will fail on the other. Read by column name, tolerate the absence of every data field, and key on whichever domain column is present.
ZoomInfo sells access to its database and puts it behind an account. Our own status column says as much. That is a structural fact about the target rather than a transient outage, so treat any plan that depends on this service as unproven until your own run says otherwise - and budget for the possibility that it stays that way.
Sibling services quote a per-request batch size because their references publish one. This service has no endpoint documentation we can point at, so we quote no number - and you should treat any number you see elsewhere with the same suspicion. Start with a handful of domains, read the status column, and scale only from what you observe.
These are the jobs this shape of data supports. Whether it arrives for your domains is the question your free rows answer.
Headcount, revenue band and industry are the three fields that decide whether a signup goes to self-serve or to sales. Resolving them from the email domain alone is the difference between a routing rule and a manual triage queue.
Most CRMs accumulate accounts with a domain and little else. A domain-keyed lookup is the cheapest way to backfill industry, location and size across a book of business without asking anyone to retype it.
Run a sector's domains and group by industry, headcount and country, and you get a map of that market's shape. Worth pairing with a source you have verified yourself, given what our runs returned.
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. On this service they are not a trial so much as the experiment: five runs in our hands returned no company data, and the free tier is how you find out what happens for your domains before you spend anything.
Roughly $2 per 1,000 domains, one row per domain - exact to budget, because a blocked lookup still returns exactly one row and is billed like any other.
Volume pricing, SLAs, dedicated workers and bespoke onboarding for teams enriching a large domain list on a schedule. Tell us your numbers and we'll quote.
LIVESCRAPER10 at checkout.Given what our runs returned here, these two are the honest recommendation for domain-keyed company data.
Twenty firmographic columns from the same input - name, industry token, headcount, founded year, revenue, address and socials - with its columns measured from real exports rather than declared by an empty header.
A different angle on the same domain: what the site is built with - CMS, ecommerce platform, analytics, CDN and server. Technographics often qualify an account as well as firmographics do.
This page sits differently from most of the catalogue, and the difference is worth stating rather than glossing.
ZoomInfo is a commercial B2B data provider. Its database is a product it sells, and access is behind a paid account - our own status column says exactly that. This is not a public register like WHOIS or an open map like OpenStreetMap, and we are not going to describe it as one. We have never retrieved company data from it, and the sibling assurance that appears elsewhere in this catalogue - that nothing sits behind a login - is deliberately absent here, because we cannot make it.
Two consequences follow. ZoomInfo's terms of use are an agreement between you and ZoomInfo, so satisfy yourself that your intended use is compatible with them before running a large job. And the declared schema includes a phone number and a company address: business contact details are still regulated in most jurisdictions, so B2B marketing rules and a defensible retention period apply to anything you do keep.
If what you actually need is domain-keyed firmographics, Company Insights answers the same question from sources whose columns we have measured. On our side: no third-party trackers on the data layer, your exports auto-delete after 30 days, we do not keep a copy of your results, and we do not build a database out of them.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
status reading blocked (ZoomInfo is paid/protected - needs residential proxy + account), and the fifth returned no rows at all. We publish the column names because an export header declares them, and we describe every one as declared rather than confirmed.domain, company_name, zoominfo_url and status - which reports the outcome of the request. The earliest run carries a fourteen-column company header instead, with no rows beneath it. They share no field names, so an importer needs to tolerate either.query, company, website, phone, employees, revenue, industry, founded, address, city, state, country, ticker and logo. What lands in them is exactly what an empty export cannot tell you, so we make no claim about formats - not whether employees is an exact number or a band, nor what founded looks like.status column, and scale from what you actually observe.Paste a handful of company domains and read the status column. Your first 500 rows are free and need no card - on a service where five runs in our hands returned no company data, that is exactly how to evaluate it.
A company domain is the most reliable key in B2B data. It arrives with every signup, sits on every CRM record, and unlike a company name it does not come in six spellings. Resolving that domain to a company record - industry, headcount, revenue, location, phone - is what turns a list of email domains into something a routing rule or a territory model can act on. This service is pointed at ZoomInfo for that purpose: submit domains, get one row each.
What an export declares is fourteen columns: the submitted query echoed back, the company name and website, a phone number, headcount, revenue, industry, founding year, street address, city, state, country, stock ticker and a logo link. Those names are copied byte-for-byte from a real export header, which is the only reason this page can list them at all.
What our runs returned is different, and it is stated here rather than buried. Five real exports sit behind this page. Four of them came back with a single row in which the company fields were empty and a status column read, word for word, that the request was blocked because ZoomInfo is paid and protected and needs a residential proxy and an account. The fifth returned no rows whatsoever. Not one company field has ever been observed holding a value. Those runs also reveal two entirely separate schemas: a four-column status envelope - domain, company name, ZoomInfo URL and status - that reports the outcome of a request, and the fourteen-column company header that appeared with nothing underneath it. The two share no field names at all, the envelope calling the domain "domain" where the wide header calls it "query", so an importer has to tolerate either and should branch on status before it looks for data fields. Everything on this page is therefore described as declared rather than confirmed: no fill rates, no example values, and no claims about formats, including whether headcount arrives as an exact number or a band.
The reason is not mysterious, and it shapes how this page should be read. ZoomInfo is a commercial B2B data provider whose database is a product it sells and whose access sits behind a paid account - our own status string names that directly. This is not a public register like WHOIS or an open map like OpenStreetMap, and the assurance that appears elsewhere in this catalogue, that nothing sits behind a login, is deliberately absent here because we cannot make it. Two things follow: ZoomInfo's terms of use are an agreement between you and ZoomInfo, so satisfy yourself that your intended use is compatible before running a large job; and the declared schema includes a phone number and a company address, so B2B marketing rules and a defensible retention period apply to whatever you keep. If domain-keyed firmographics are what you actually need, Company Insights answers the same question with columns measured from real exports rather than declared by an empty header. No third-party trackers run on the data layer, exports auto-delete after 30 days, and your first 500 rows are free - on this service in particular, spend them before you spend anything else.