Last updated: September 13, 2026
Thank you for choosing 1000 Bulk Domain Checker (“the Extension”). We respect your privacy and are committed to protecting it. This Privacy Policy outlines our practices regarding data collection, usage, storage, and disclosures when you use our Chrome Extension.
1. Summary (Single Purpose)
1000 Bulk Domain Checker is designed with a single primary purpose: to help users quickly and accurately verify the availability and registration status of multiple domain names in bulk (up to 1,000 domains) using the official Registration Data Access Protocol (RDAP), and to export the collected results into clean CSV reports.
2. Information We Collect
We do NOT collect, store, transmit, or sell any personally identifiable information (PII).
Specifically:
- No Personal Data: We do not collect your name, email address, IP address, browsing history, location, or credentials.
- No Analytics or Trackers: We do not include tracking scripts, telemetry, Google Analytics, or third-party advertising SDKs in the Extension.
- No Remote Servers: We do not operate any external backend or server that captures or logs the domain names you submit or check.
3. How Data is Processed
When you input domain names into the Extension:
- Local Queue Management: The list of domain names you enter or upload via text/CSV is processed exclusively inside your local browser instance.
- Authoritative RDAP Queries: To verify domain status, the Extension fetches IANA’s public registry map (
https://data.iana.org/rdap/dns.json) and queries the designated authoritative RDAP server for each Top-Level Domain (TLD) directly from your client browser. - No Intermediary Logging: The domain queries travel directly between your browser and the official public registry servers (such as Verisign, PIR, Nominet, or ccTLD registries) to fetch public DNS/RDAP availability status. No third-party intermediary sees or stores your search queries.
4. Local Storage and Data Retention
The Extension utilizes Chrome’s local storage APIs (chrome.storage.local):
- Local Persistence: Your domain check queue, current progress, settings (concurrency and rate delay), and RDAP status results are saved strictly inside your browser’s local storage.
- Why it is stored: This ensures your batch progress is preserved if you accidentally close the popup or restart your browser.
- Data Deletion: You have complete control over your data. Clicking the “Hapus” / “Clear” button in the extension interface immediately wipes all cached domains, jobs, and results from your local browser storage. Uninstalling the Extension will also permanently delete all stored local data.
5. Chrome Permissions Justifications
The Extension requests the following permissions strictly to provide its core features:
| Permission | Purpose & Justification |
|---|---|
storage | Used to locally persist domain queues, progress, and verification results in chrome.storage.local so batch jobs can be resumed without data loss. |
unlimitedStorage | Required to allow caching of large batches (up to 1,000+ domains) with detailed HTTP response codes, timestamps, and status messages without encountering browser storage quota limitations. |
alarms | Used to run periodic lifecycle checks (chrome.alarms) so the Manifest V3 background service worker can resume and continue long-running domain validation batches if the worker is suspended during idle intervals. |
downloads | Used to facilitate downloading the generated CSV file containing validation results directly to your local downloads directory. |
host_permissions (https://*/*) | Required because domain availability queries are sent directly to authoritative RDAP servers for hundreds of different TLDs and ccTLDs globally. These registry hostnames are dynamically resolved from IANA’s root bootstrap list and cannot be pre-defined statically. |
6. Third-Party Disclosures & Data Sharing
We do not sell, trade, rent, or transfer any user data or queried domain lists to outside parties.
- We do not share data with data brokers.
- We do not use user data for targeted advertising or credit evaluation.
- All network requests are strictly direct communication between your browser and public RDAP directory services.
7. Limited Use Compliance
Our use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
8. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated revision date.
9. Contact Us
If you have any questions, feedback, or concerns regarding this Privacy Policy or the Extension, please feel free to reach out via our support channel:
- Email: javier@technolati.com