Bulk analysis eliminates repetitive DNS lookup work, but quality control and commercial judgment still decide whether 1,000 domains become opportunities.
Design the output before running a bulk scan
Choose columns that support a decision: domain, company, workspace, gateway, DMARC posture, confidence, evidence and next sales action. Add a collection timestamp and keep an explicit unknown state. A system that forces every account into a provider category will look complete while quietly introducing false positives.
A domain scan does not enrich a company with a decision maker. Treat technographic qualification and contact discovery as separate steps.
Clean the incoming domain set
Normalize domains to lowercase, remove surrounding whitespace, eliminate URLs and path components, and detect duplicates. Distinguish organizational domains from subdomains when the outreach account is the parent business. Preserve your CRM identifier separately from the domain that is scanned.
For large lists, split inputs into manageable batches supported by your plan and the current SecuTest UI. Do not assume an undocumented upload limit or claim that every 1,000-domain job completes in a fixed number of seconds.
Run the scanner and preserve scan boundaries
A user-owned list belongs in Scan Prospects. Track the originating batch so sales can find an account again and export the intended selection instead of merging unrelated campaigns. Keep raw MX, SPF and DMARC evidence in the exported record where supported, and do not overwrite a previous timestamp with a newer one without preserving the distinction.
Prioritize with explicit conditions
Build a review queue around service-specific conditions. Example: likely Microsoft 365 + p=none + account fits our region. Another queue could capture a recognized gateway where your team offers managed configuration and migration.
| Bucket | Next action |
|---|---|
| Strong detection and clear service fit | Research contact, prepare discovery question |
| Ambiguous workspace or gateway | Verify secondary evidence manually |
| Missing data or DNS error | Retry or exclude without inventing a result |
| Out-of-ICP account | Park even if the fingerprint is interesting |
Review exceptions, not every row
Inspect a random subset plus all uncertain and high-value accounts. False positives often appear around MX gateways, stale DKIM CNAMEs and SPF includes from tools unrelated to the inbound mail path. Improving these rules is worth more than shaving a few seconds off the process.
Turn the CSV into an experiment
Send a controlled group of accounts through the same sales motion. Compare meaningful reply rates and booked calls, not just the number of domains scanned. Record which signals correlated with conversations, then decide whether to scale. The cost of an inaccurate premise in outreach is reputational, not merely technical.
An exception queue makes bulk qualification reliable
Bulk processing should reduce repetitive checks, not eliminate oversight. Place failed DNS lookups, multiple contradictory provider signatures, unknown gateways and weak workspace inference into a separate review bucket. A salesperson should not have to evaluate all one thousand domains, but someone should review the cases where the classification could materially affect the message.
For recurring campaigns, keep a minimal audit record: input checksum, source list, batch identifier, scan timestamp, detector version, number of successful lookups, number of unresolved records and the final exported columns. This gives you a reproducible explanation when a contact asks why your team thought a particular technology was present. It also helps distinguish a real migration from two scans performed against different resolver states.
Turn infrastructure signals into a qualified prospect list.
Analyze domains you already know, or find new companies that match the technologies you target. Public DNS observations support discovery, not proof of an internal security weakness.