Hostinger contact form not working, step by step

A contact form on a Hostinger site, built in the website builder or running on WordPress, has two jobs. It shows the visitor a page, and it hands the message to something that sends mail. The page can succeed while the hand-off fails. A mail function that the host refuses, a recipient address typed wrong, or a sending domain without its mail records can all leave the visitor with a thank you and the owner with nothing. Nothing in the browser separates these, so a visitor who sees a sent message assumes it was received and moves on.

• Does the form show a success message, an error or nothing after you press Send?
• Does the notification arrive at the address the form names, not an old mailbox?
• Does a test submission show up in the form's own log, if your setup keeps one?
• Does the sending domain have the mail records your host gave you, with no typo?

This is the failure that is hardest to see from inside. The form posts the message to the site, the site passes it to a mail step, and the visitor sees a success message as soon as the post returns. If the mail step fails after that point, nothing on the visitor's screen changes. Look for three causes in turn: a recipient address that is not yours, a message that went to spam because the sending domain lacks its records, or a mail step the host blocks.

Where the trace sits matters. If your builder or plugin keeps a log of submissions, a log entry with no email points at mail delivery. No log entry, while the page says sent, points at the form posting somewhere else. Test with an address you own, then with a personal address at a different provider, so you do not mistake a provider's spam filter for a broken form.

When a visitor presses Send and nothing happens, the browser has usually stopped the submit before it left the page. The common reason is a required field that is hidden or sits off screen, which blocks the submit and points at a spot the visitor cannot see. A script that failed to load, a CAPTCHA the visitor could not pass, or a cookie banner covering the button can do the same. From the visitor's side the form is broken. From yours it looks fine, because your own fields are visible and already filled in.

Run the same three checks in the same order each time, so you change one thing at a time. First, submit with every field empty and see whether a message appears under a field, or nothing at all. Second, submit a valid message from a phone, then from a laptop. Third, read the mail destination in the form's settings and send to an address you control. A message under a hidden field points at the form. A message that reaches the log but not the inbox points at mail. Nothing at all, on both devices, points at a script or a blocker.

Then run the visitors. They submit the form in browsers that are not yours, with no saved fields and no cookies from your own visits. The report keeps the step and a screenshot for each visitor, so you can see which of the three failures a stranger hits. Compare that with your own three checks, and with the form's log, before you decide what to change.

Contact forms on a Hostinger site tend to break again after changes that have nothing to do with the form: a theme or plugin update, a new domain record, or a change to the host's mail settings. Rerun the same visitors after each of them. You see the success message, the error text and the step where each visitor stopped, so the next silent failure shows up before a customer finds it.