Skip to main content

Hostinger

Hostinger DNS via a single personal API token. A good fit for domains already using Hostinger nameservers.

Prerequisites​

  • A Hostinger account with the zone managed under Hostinger DNS (the domain uses Hostinger nameservers).
  • The domain must resolve publicly — DNS-01 needs the zone to exist in public DNS so the CA can query the challenge TXT.

Create the API token​

  1. Log in to hPanel.
  2. Account menu → API (or Account Information → API tokens) → create a token.
  3. Copy the token — it is shown once. The token has account-wide DNS access; rotate on a schedule.

Add the credential​

  1. Settings → DNS Credentials → New → Hostinger.
  2. Name: hostinger-example-prod.
  3. API token: paste.
  4. Test (with a domain) → Save.

Config fields​

FieldRequiredPurpose
api_tokenyesHostinger personal API token.

Propagation​

Hostinger propagates quickly; default settings work.

Troubleshooting​

"Unauthorized" — token rejected​

The token is wrong, revoked, or the zone isn't managed by Hostinger DNS (domain uses external nameservers).

"Zone not found"​

The domain isn't in this account's Hostinger DNS, or still uses another provider's nameservers. Point the domain at Hostinger DNS first.

See also​