Questions · Updated 2026-09-23
How do I verify a sending domain on Hostinger?
To verify a sending domain on Hostinger, add each row from GET /domains/{id}/setup on the DNS records page, with @ for an apex host, then call POST /domains/{id}/verify. The clicks below are Hostinger's, as of September 2026.
To verify a sending domain on Hostinger, add each row from GET /domains/{id}/setup on the DNS records page, with @ for an apex host, then call POST /domains/{id}/verify. The clicks below are Hostinger's, as of September 2026. GET /domains/{id}/setup does not name Hostinger in provider_hints. The records are the same sheet either way.
The records to publish
POST /domains registers the name. GET /domains/{id}/setup returns one row per record, with record, host, type, value, priority, and required. A TXT row also has value_strings and value_bind. Paste those. The DKIM value is the one on the row. zone_file on that response is a BIND file of these rows, not the rest of the zone.
A new domain sends once the required rows resolve. Domains and DNS names them: the DKIM TXT, and the return-path MX and TXT. Root SPF and DMARC are recommended. A tracking CNAME is on the sheet only when tracking is available, and it never blocks verification. If the apex already has an SPF TXT, merge the sheet's value into that one record. A second SPF TXT on the same name invalidates both.
curl -sS -X GET https://api.agentisend.com/domains/9c8f8f0e-3d1a-4d3f-9a1e-2b7c1a0f5e42/setup \
-H "Authorization: Bearer $AGENTISEND_API_KEY"200
{
"commands": "string",
"deep_link": "string",
"detected": true,
"domain": "string",
"nameservers": [],
"provider": "string",
"provider_hints": "string",
"records": []
}Hostinger's dashboard, as of September 2026
How to Manage DNS Records at Hostinger (updated September 15, 2026) says: Hostinger dashboard, Domains in the left sidebar, DNS, then the domain. You land on the DNS records page. Add a record with type, name, content, TTL, and any other field that type requires, then click Add Record. The article says that if the domain's nameservers point somewhere else, you manage DNS on that platform instead.
How to manage TXT records says the type is TXT, the host is @ for the domain, and a subdomain's name (not the full name) for anything else. The value is what the email provider gives you, which here is the row's value or its value_strings. The article says the default TTL is 14400 seconds when you were not given another one, and to allow up to 24 hours.
How to manage MX records says: Domains, Manage, DNS / Nameservers, type MX. Name is @ for the domain or the subdomain name. Mail server is the provider's host. Priority is the provider's number, and a lower number is higher priority. Put the row's value in Mail server and the row's priority in Priority.
The manage-DNS article also documents Import of a BIND zone file, with Append adding records beside the ones already there and Replace deleting the current zone. Use Append with zone_file if you import. Replace would remove records that are not on the sheet.
Read it back
POST /domains/{id}/verify reports which required rows resolved. GET /domains/{id} is the sheet with each row's status.