Can I validate an import before creating monitors?

Yes. Bulk import includes a dry-run step that reports accepted, duplicate, invalid, and quota-blocked rows before the commit step creates monitors.

Bulk SSL monitoring

Turn a hostname spreadsheet into checked monitors.

Client and production hostnames often start in a spreadsheet. Domain Trust Watch validates rows before anything is created.

View plans by monitored hostname count Import docs

Bulk dry-run

Spreadsheet rows checked first

Ready to commit

Bulk import previews quota impact, duplicates, invalid rows, and accepted hostnames before creating monitors.

Accepted118 hostnames

Duplicates9 skipped

Invalid3 rows need review

Bulk import

Dry-run hostname lists before creating monitors.

The import screen previews accepted rows, duplicates, row-level errors, and quota impact before anything is committed.

Accepted118hostnames ready

Duplicates9already monitored

Invalid3needs row review

Import rows

api.client-a.comacceptedtag: client-a

checkout.client-b.comduplicatemonitor exists

bad hostinvalidhostname parse failed

Commit summary

Quota impact+118 monitorsteam plan available

Labelsclient, systemapplied on create

OwnerCertificate Deskworkspace default

Dry run before creation

Every import can be validated before monitors are created. The dry run reports accepted rows, malformed rows, duplicates, blocked rows, and plan quota impact.

Clean hostname lists before they become noisy monitors.
Spot duplicate client or environment rows before commit.
Understand whether 3, 25, or 100 monitored hostnames fits the list.

Example dry-run output

Row	Hostname	Status	Reason
1	app.example.com	Accepted	Creates one monitor on port 443.
2	api.example.com,443,api.example.com,API,prod platform	Accepted	SNI, label, and tags preserved.
3	app.example.com	Duplicate	Already present in the import or workspace.
4	https://bad.example.com/path	Invalid	Use hostnames without scheme or path.
5	legacy.example.com	Over quota	Plan limit reached before this row can be created.

CSV and pasted hostnames

Imports support hostname, optional port, optional SNI hostname, optional label, and optional tags. CSV upload and pasted rows use the same validation model.

Sample import rows

hostname,port,sni_hostname,label,tags
app.example.com,443,,Production app,"prod,platform"
checkout.example.com,443,checkout.example.com,Checkout,"prod,revenue"
client-a.example.net,443,,Client A portal,"client-a,agency"

Client and ownership tags

Tags can represent clients, systems, environments, certificate vendors, or renewal contacts. Agencies can bring a spreadsheet into a shared workspace without losing row-level context.

Filter by client when an account team needs a renewal update.
Filter by environment when production endpoints need faster alerts.
Filter by responsible team when work moves after a handoff.

FAQ2 answers

Can I validate an import before creating monitors?
Yes. Bulk import includes a dry-run step that reports accepted, duplicate, invalid, and quota-blocked rows before the commit step creates monitors.
What fields can an import include?
An import row can include hostname, optional port, optional SNI hostname, optional label, and optional tags.

Validate the list

Know which rows will create monitors before you commit.

Use pricing to pick the right monitored hostname count, then use import docs when you are ready to prepare the file.

Compare plans Read import docs