Bulk-adding domains
Corrections: support@domainvane.com
Paste a list of hostnames into Domainvane. Each entry is validated on its own. You get one result per entry, and invalid entries are not saved.
This is an account feature. The public page at /tools/bulk-ssl-checker explains the paste and links to signup. It does not check a list of hosts. The public checker accepts one hostname on port 443 per request.
What you can paste
Separate hostnames with newlines, commas, or spaces. A mix of those separators in one paste is fine.
Examples that parse as hostnames:
client-a.example
www.client-a.example, client-b.example
https://www.client-c.example/pricinghttps://www.client-c.example/pricing is stored as www.client-c.example on port 443. The scheme and the path are stripped. The name is lowercased. An internationalized name is stored as punycode.
Result for each entry
| Result | Meaning |
|---|---|
added | Saved on this account. The dashboard shows it as pending until the first check finishes. |
duplicate | This account already monitors that hostname and port, or the same name appeared earlier in this paste. No second row is created. |
invalid | Empty, contains spaces, contains characters that are not valid in a DNS hostname, is a bare IP address, or has an over-long label. Nothing is saved for that entry. |
limit | Saving it would pass the plan cap. Nothing is saved for that entry. |
The paste keeps going through the list. It stops adding once the cap is reached and marks every remaining entry that would have been new as limit. Entries that are invalid or duplicate are still reported as invalid or duplicate. They do not consume a slot.
Plan caps
| Plan | Hostnames |
|---|---|
| Free | 3 |
| Solo | 25 |
| Agency | 150 |
| Agency+ | 750 |
The cap is applied inside the save, on the server, for a single add and for a paste. A rejected add does not leave a partial row behind.
Paused hostnames count toward the cap. Pausing a name stops checks and alerts for it. It does not open a slot for a new name. Delete a hostname to free a slot.
If a downgrade or a cancellation leaves you over the new cap, existing hostnames are not deleted. The newest names over the cap are paused, and further adds return limit until the total, paused names included, is back under the cap. Moving up to a larger plan does not unpause those names for you.
What gets checked after a successful add
Each added hostname is a target on port 443. The scheduler checks the TLS certificate and, separately, domain expiry over RDAP. Common gTLDs that have an HTTPS RDAP base are in scope. A TLD without one, or a record with no usable expiry, shows unknown. Domainvane does not fill that in from WHOIS.
A name that resolves only to a non-public address is not connected to.
RDAP limits, in short
- Supported case: an expiration event comes back from RDAP, with provenance registry or registrar.
- unknown: unsupported TLD, no HTTPS RDAP base, missing expiry, or ambiguous data. The date is left blank on purpose.
- error: the lookup timed out, was rate-limited, or the response was malformed. That is not a guessed date.
Dashboard alert state for a domain-expiry date is calculated only when Domainvane has a date. An unknown row does not produce a "30 days left" state because there is no day count. Email alerts are delivered to external inboxes, including Gmail. Inbox placement is not guaranteed for every provider (Outlook and Yahoo have not been tested). Webhooks are included on paid plans. See alerts and webhooks.
A practical paste
- Export the hostnames you actually serve (one per line is the least surprising format).
- Drop scheme, path, and port yourself if you want to see the stored name before you paste. Domainvane will strip scheme and path if you leave them.
- Remove bare IPs and names you do not have permission to monitor.
- Paste. Read the per-entry results before you close the page.
- If you see
limit, the cap was hit. Delete or upgrade, then paste the remainder. Remember that paused rows still occupy the cap. - On the dashboard, pending rows are waiting for the first check. The first check is not instant for every row; the scheduler works through due targets in batches.
There is no public API and there are no API keys in this version, so a paste in the account UI is the bulk import. A script cannot call a documented write API to add names.