Connect a domain

Get a domain serving a Hostinger website over HTTPS. The one rule that matters most: records that already work — email (MX), SPF, DKIM and verification TXT records — must survive every DNS change.

Calling the operations

• Read the inputSchema that search returns before the first call of each operation. If a name below is rejected as unknown, search for what the step does (e.g. "dns records").
• Batch reads with multi-execute; values pass between steps as $steps.<i>.<path>. Batches chain operations from one server only — the Hostinger Connector runs hosting, agency-hosting, domains and dns as separate servers. When search cannot find an operation, ask the user to enable that product group in the Connector.
• Every write here changes what the public sees. State the change and get a yes before each one.

1. Gather the facts (read-only)

• Website. hosting_websites_list with domain (Shared and Cloud; substring match, so take the exact entry) and agency-hosting_websites_list-plan with domain (Agency). Keep username and order_id, or details.uid and details.ipv4. When the domain has no website yet, find the site the user means — often a *.hostingersite.com one — or the order to create it on (hosting_orders_list, agency-hosting_orders_list).
• Registration. domains_portfolio_get succeeds only for domains registered at Hostinger; its name_servers show who runs DNS. Hostinger's own nameservers end in dns-parking.com.
• Live DNS, to know what must be kept: