Docs

Import hostnames after a dry run.

The import flow validates rows before monitors are created, so teams can clean hostname lists before committing them.

Bulk SSL monitoringTroubleshooting

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
Hostname, optional port, SNI, label, and tags
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.

01

Accepted row shape

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

  • Put one public hostname on each row without https:// or a path.
  • Use tags to preserve client, environment, and responsible-team context.
  • Keep SNI values explicit when they differ from the connection hostname.
Sample CSV
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"
02

Dry-run output

The dry run returns row numbers, normalized endpoint fields, status, errors, accepted count, duplicate rows, invalid rows, and quota impact.

Common dry-run outcomes
OutcomeExampleWhat to do
Acceptedapp.example.comCommit when the hostname, port, SNI, label, and tags look correct.
Duplicateapp.example.com already existsRemove the row or update the existing monitor instead.
Invalidhttps://example.com/pathUse only the hostname, not scheme, path, or query string.
Over quotaRow would exceed 25 monitored hostnamesUpgrade, remove lower-risk rows, or split the import.
BlockedInternal-only hostnameUse a publicly reachable hostname for public monitoring.
03

Commit behavior

Only accepted rows are created on commit. Existing duplicates, invalid endpoints, and over-quota rows remain blocked.

04

Agency and client lists

Use tags for client names, environments, systems, or renewal contacts. Warnings and certificate events remain attached to each created monitor after import.

  • Give account teams a way to filter client certificate work.
  • Give operators enough context to find DNS, hosting, or renewal responsibility.
  • Keep warning history attached after the import becomes live monitoring.
Related3 pagesAgenciesSee client-domain import and tagging examples.Explore SSL monitoring for agencies
PricingPricingChoose 3, 25, or 100 monitored hostnames before commit.ToolRun SSL checkerCheck a representative hostname before importing the full list.
Validate before commit

Use dry run output to clean the hostname list.

Compare accepted rows, duplicates, malformed rows, and quota impact before monitors are created.

See bulk importView pricing