TL;DR Short answer: IP2WHOIS ETL tools turn domain names into structured WHOIS records, such as registrar, creation and expiry dates, status and name servers, for security, brand protection and enrichment. Airbyte has an IP2Whois connector for loading records into a warehouse, and Python SDKs suit bulk lookups. Two changes matter before you build: ICANN replaced WHOIS with RDAP for generic domains in January 2025, and most registrant contact details have been redacted since GDPR. Eight IP2WHOIS ETL tools compared:
Airbyte IP2WHOIS Python SDK WhoisXML API RDAP clients python-whois dlt n8n Make The IP2WHOIS constraint: every lookup spends one query from a monthly quota, so the number of domains multiplied by how often you refresh them decides which plan you need. IP2WHOIS ETL tools move domain registration data from the IP2WHOIS API, run by IP2Location, into a warehouse, database or spreadsheet. Teams use it to spot newly registered look-alike domains, track expiry dates for their own portfolio, enrich security logs and CRM records with registrar data, and investigate infrastructure. For broader enrichment approaches, see our guide to data enrichment tools .
Every IP2WHOIS ETL tool reads the same REST API, authenticated with an API key. The main data is:
Domain details: domain name, domain ID, status codes and DNSSEC information. Dates: creation, last update and expiry dates, with the domain's age in days. Registrar: the registrar's name, IANA ID and URL. Contacts: registrant, administrative, technical and billing contacts, where not redacted for privacy. Name servers: the domain's authoritative name servers. Hosted domains: through the separate Hosted Domain API, the domains hosted on a given IP address. How have WHOIS and RDAP changed? Two changes shape what any WHOIS pipeline returns today. First, since GDPR took effect in 2018, registrars redact most personal contact details, so registrant names, emails and phone numbers are usually replaced with privacy placeholders. Second, ICANN retired WHOIS for generic top-level domains on 28 January 2025, making the Registration Data Access Protocol, RDAP, the authoritative source. RDAP returns structured JSON over HTTPS, while many country-code domains still rely on WHOIS. Providers such as IP2WHOIS smooth over these differences by returning one consistent JSON format whatever the registry uses.
How do the IP2WHOIS ETL tools compare? Tool Approach Best for Volume Cost Airbyte Pre-built IP2Whois connector WHOIS records next to other data in a warehouse One domain per source Free self-hosted Core; paid Cloud plans IP2WHOIS SDK Official Python client Scripted lookups of many domains Limited by your plan's quota IP2WHOIS free tier or paid plan WhoisXML API Commercial domain-data APIs Bulk, historical and reverse WHOIS High, with bulk endpoints Paid plans RDAP clients Direct registry lookups Authoritative data for generic domains Subject to each registry's limits Free python-whois WHOIS protocol library Lightweight lookups without an API key Low, servers may throttle Free, open source dlt Python REST API source Loading API results into a warehouse Limited by your plan's quota Free, open source n8n HTTP Request node Enriching new domains as they arrive Low to medium Free self-hosted; paid cloud Make HTTP module in scenarios No-code enrichment into sheets or apps Low Operations-based, free tier
Which IP2WHOIS ETL tools should you consider? Eight IP2WHOIS ETL tools, from a pre-built connector to direct registry lookups:
1. Airbyte Airbyte is the open-source data connectivity platform for AI and analytics, and among IP2WHOIS ETL tools it is the one with a pre-built connector. Its IP2Whois source retrieves the WHOIS record for a domain you configure, with your API key, and loads it into the destination you choose with full refresh syncs. For more ELT options, see our guide to ELT tools .
Each source covers one domain, so Airbyte suits tracking a small portfolio, such as your own domains and their expiry dates, alongside security or business data from 700+ other connectors. For large lists of domains, a script or a bulk provider is a better fit. Airbyte runs in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core.
Pros Cons Pre-built connector One domain per source configuration WHOIS data next to security and business data Full refresh only Cloud, Flex or self-hosted Core Not built for bulk lookups of many domains
2. IP2WHOIS Python SDK IP2Location publishes an official Python SDK for IP2WHOIS that wraps the domain WHOIS and hosted domain APIs. Looping it over a list of domains and writing results to a database is the simplest way to enrich many domains at once, within your plan's monthly quota. For more code-first options, see our guide to Python ETL tools .
Pros Cons Official client from the provider You write scheduling and storage Handles many domains in a loop Quota limits bulk volume Same consistent JSON format Requires Python skills
3. WhoisXML API WhoisXML API is a commercial domain intelligence provider with WHOIS lookups plus bulk lookups, historical WHOIS records, reverse WHOIS by registrant, and newly registered domain feeds. It suits security and brand protection teams that need volume and history rather than one lookup at a time.
Pros Cons Bulk, historical and reverse WHOIS Paid plans for meaningful volume Newly registered domain feeds More than you need for small portfolios Built for security use cases Another vendor to manage
4. RDAP clients Since ICANN made RDAP authoritative for generic domains in January 2025, you can query registries directly with RDAP clients such as the open-source whoisit library for Python, using IANA's bootstrap files to find the right server. RDAP returns structured JSON without an API key, though each registry sets its own rate limits and many country-code domains still use WHOIS.
Pros Cons Authoritative, structured JSON Coverage gaps for some country-code domains No API key or subscription Each registry has its own rate limits Free and standards-based Responses vary between registries
5. python-whois python-whois is an open-source library that queries WHOIS servers directly and parses the text responses into fields. It works without an API key and suits lightweight lookups, but WHOIS text formats differ between registries and servers may throttle repeated queries.
Pros Cons No API key needed Parsing varies between registries Free and open source Servers throttle repeated queries Quick for one-off lookups Less useful for generic domains since RDAP
6. dlt dlt is an open-source Python library for loading data. Its REST API source can call IP2WHOIS for each domain in a list and load the JSON into DuckDB, BigQuery, Snowflake or Postgres with schema inference, which suits Python teams that want a scheduled warehouse pipeline. For other API pipelines, see our guide to REST API ETL tools .
Pros Cons Schema inference from nested JSON You write and schedule the pipeline Loads to many destinations Requires Python skills Free and open source Quota budgeting is yours to manage
7. n8n n8n is one of the self-hostable IP2WHOIS ETL tools: its HTTP Request node looks up domains as they appear, for example from a security alert or a new sign-up, and writes the registrar and dates to a database or ticket. It suits event-driven enrichment rather than bulk loads.
Pros Cons Event-driven enrichment You run and maintain it if self-hosted Self-hosting option Not built for bulk backfills Hundreds of destination integrations Quota tracking is yours to add
8. Make Make is the no-code option among IP2WHOIS ETL tools: it calls the API through its HTTP module, parses the record and routes expiry dates or registrar details to Google Sheets, Airtable or a CRM. For spreadsheet workflows, see our guide to Google Sheets ETL tools .
Pros Cons No-code and quick to set up Operations-based pricing adds up Easy routing to many apps Not designed for warehouse loading Free tier to start Complex scenarios become hard to maintain
What should you check before syncing IP2WHOIS data? Whichever IP2WHOIS ETL tools you choose, check these first:
Query budget: multiply domains by refreshes per month and compare it with your plan's monthly quota; most WHOIS data changes rarely, so monthly refreshes are often enough.Redaction: expect registrant contact fields to be redacted, and design analysis around registrar, dates, status and name servers instead.RDAP versus WHOIS: for generic domains RDAP is now authoritative, so check how your provider sources records and compare against RDAP when accuracy matters.Personal data: contact details that are not redacted are still personal data, so store them only with a lawful purpose and appropriate retention.Dates and time zones: normalise creation and expiry dates to UTC before building expiry alerts.History: WHOIS lookups return the current record only, so keep your own snapshots if you need to track changes over time.How do you start pulling IP2WHOIS data with Airbyte? If you decide to test Airbyte, setting up an IP2WHOIS pipeline takes three steps.
Step 1: Set up IP2Whois as a source Sign up at IP2WHOIS and copy your API key. In Airbyte, open Sources, choose New source, select IP2Whois and enter the API key and the domain you want to track.
Step 2: Set up a destination Pick where the WHOIS records should land, such as BigQuery, Snowflake, Postgres or another database. For warehouse options, see our guide to cloud data warehouses .
Step 3: Configure the connection Schedule syncs to match how often you need fresh records, such as weekly for expiry monitoring. The process is the same whether you start with Airbyte Cloud or run self-hosted Airbyte Core .
Which IP2WHOIS ETL tool should you choose? Choosing between IP2WHOIS ETL tools comes down to volume and purpose. For monitoring a handful of your own domains next to other data, use Airbyte. For enriching lists of domains, the IP2WHOIS SDK or dlt works within your quota, and WhoisXML API covers bulk and historical needs. For authoritative records on generic domains without a subscription, query RDAP directly. For security logs that need domain context, see our guide to AWS CloudTrail ETL tools .
Load WHOIS records with Airbyte Sync IP2WHOIS domain records into the same warehouse as your security and business data with Airbyte, in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core.
Try Airbyte Cloud free for 14 days or talk to our team .
Frequently Asked Questions (FAQs) 1. What are the best IP2WHOIS ETL tools? Airbyte has a pre-built IP2Whois connector for loading records into a warehouse, and the IP2WHOIS Python SDK or dlt suit lookups of many domains. WhoisXML API covers bulk and historical WHOIS, RDAP clients query registries directly, and n8n or Make suit event-driven enrichment.
2. Is IP2WHOIS free? IP2WHOIS has a free plan with a monthly quota of WHOIS lookups, and paid plans for higher volumes. Check its pricing page for current limits before sizing a pipeline.
3. Why are WHOIS contact details redacted? Since GDPR took effect in 2018, registrars redact most personal contact details in public WHOIS and RDAP records. Registrar, dates, status and name servers usually remain available.
4. What is RDAP and does it replace WHOIS? RDAP, the Registration Data Access Protocol, returns registration data as structured JSON over HTTPS. ICANN made it the authoritative source for generic top-level domains on 28 January 2025, replacing WHOIS, though many country-code domains still use WHOIS.
5. Does Airbyte support bulk WHOIS lookups? Airbyte's IP2Whois source looks up one configured domain per source, so it suits small portfolios. For large lists of domains, use the IP2WHOIS SDK, dlt or a bulk provider such as WhoisXML API.
Suggested reads Data Enrichment Tools
Web Scraping Tools
REST API ETL Tools
Data Ingestion Tools
.webp)