History Checker helps analyze domain history before purchase, screen drop lists and reduce risks when building a PBN. This guide contains only what you need to run the first check and interpret the result.
Historical snapshots, topics, languages, redirects, sharp content changes, empty or suspicious periods.
Casino, adult, crypto, pharma, doorway, hacked content and your own forbidden words.
Current or historical NS/DNS signals. The external check may take additional time.
Available DMCA-related signals for domains that pass the base archive analysis.
The final status does not replace a backlink and SEO metrics audit. It reveals historical domain risks that may be invisible on the current website.
Completed results can be written to Google Sheets in batches or exported as CSV and HTML. Reports include the domain, final status, risk score, language, topic, snapshot count, DNS, DMCA and a concise explanation.
History Checker uses a dedicated Google service account. The client can access only spreadsheets that you explicitly share with that service account email.
Open Google Cloud Console and create a separate project for History Checker. This makes access and key rotation easier to manage.
Open Google Cloud Console ↗In the selected project, open APIs & Services → Library, find Google Sheets API and click Enable.
Enable Sheets API ↗Go to IAM & Admin → Service Accounts → Create service account. Use a name such as history-checker. Broad Google Cloud roles are not required for one shared spreadsheet.
Open the account and select Keys → Add key → Create new key → JSON → Create. Google downloads the JSON only when the key is created.
Open the JSON and copy client_email. In the target Google Sheet, click Share, add this email and choose Editor. The spreadsheet does not need to be public.
Open API → Google Sheets API → Upload JSON and select the file. The client copies credentials into its local profile, so the original can be moved to secure storage.
Open Settings → Google Sheets Pipeline. Paste the Sheet ID, set a name and column mapping, then click Save table.
The spreadsheet should appear in the active list. Run one or two test domains. A completed row is written after all enabled checks for the domain finish.
client_email from JSON and grant Editor access.OFFICIAL GUIDES: SERVICE ACCOUNT ↗ JSON KEY ↗ SHARE ACCESS ↗
History Checker does not create open, free accounts. Your account is created automatically only after the first payment has been confirmed by the payment provider.
Choose a plan, enter your email and complete payment. Once the payment is credited, we create the cabinet account, activate the selected plan and send the access token, cabinet link and desktop client link to that email. There is no separate registration form and no social sign-in.
Each account can consume queue capacity, worker time, API quota, storage and support resources. Delaying account creation until a confirmed payment prevents disposable and automated registrations from occupying those resources, so capacity remains available for active customers and infrastructure costs stay predictable.
The API creates jobs, submits domain lists and returns queue status and base Web Archive analysis results. An access token is provided with an active plan.
DNS, DMCA, local blacklist and Google Sheets write-back are coordinated by the desktop client. Windows 10 and 11 are currently supported; macOS and Linux support is planned.
Yes. It is designed for batch screening of expired and dropped domains before an auction or registration.
Yes. Topic history, spam signals, redirects, DNS and DMCA help remove risky domains before evaluating SEO metrics.
CHECK means the domain passed the automated filters and can move to manual verification. It is not a command to buy and not a 100% guarantee: no critical automated stop signal was found, so the domain is ready for the next stage of your review.
History Checker filters are strong, but Web Archive can have incomplete, missing or incorrectly preserved snapshots. The service also does not evaluate SEO metrics, backlink profile, indexation, penalty history or auction price. Review key snapshots and your SEO metrics before buying.
CHECK means review manually; BUY means low automated risk and stable signals; SKIP or BAD means a material risk was found, such as spam history, blacklist, unsafe redirects or DNS signals. Every status is a filtering outcome, not financial advice.
The external DNS service can queue newly requested domains. The desktop client resubmits pending domains in batches of up to ten until a result appears. The primary archive analysis is not restarted.
Yes. A provider-cached result returns quickly. A domain not yet cached can receive a temporary pending status and is then checked again by the client.
Review key Web Archive snapshots, topic changes, redirects, language, backlinks, indexation, organic traffic, SEO metrics and domain reputation. For drop domains, also check auction terms and possible trademark conflicts.
Upload a drop list, receive a clear risk score and build a cleaner final pool for SEO projects.