Business mail platform · Hostinger Email
Verifying addresses at Hostinger Email domains
Can you verify addresses at domains behind Hostinger Email?
Depends on the domainIt depends on the company. Domains behind Hostinger Email are probed like any other.
Check one address
Five checks a minute, no account needed. Nothing is sent to the address — we ask its mail server whether the mailbox exists, then disconnect.
Checking a whole list? The first 100 addresses are free, with results to download. No card.
By continuing you agree to our Terms and Privacy Policy.
Hostinger Email answers for the company's own mail rules, so the checker treats every domain on its own: it offers a random address first, and if that is accepted the domain is catch-all and results come back risky ("Accepts all addresses"). Otherwise your address gets a per-mailbox answer. It always checks the syntax, the domain's MX records, disposable domains and role addresses such as info@ first.
Mailbox existsMailbox not foundAccepts all addressesCompany domains whose MX records point at hostinger.com are hosted at Hostinger Email. Hostinger Email documents a catch-all option, and where an admin turns it on every address at the domain looks deliverable. Our checker probes each domain on its own: it offers a random address that can't exist first, and a domain that accepts it comes back risky as catch-all; otherwise your address gets a per-mailbox answer.
Live DNS snapshot: hostinger.com
Checked 26 October 2026, 07:04 UTCRead from DNS at the time shown and refreshed at most once a day. MX says where mail for hostinger.com goes; SPF and DMARC describe mail sent from it, not whether any one address exists.
- 1
aspmx.l.google.comGoogle Workspace - 5
alt1.aspmx.l.google.comGoogle Workspace - 5
alt2.aspmx.l.google.comGoogle Workspace - 10
aspmx2.googlemail.comGoogle Workspace - 10
aspmx3.googlemail.comGoogle Workspace
First MX host belongs to Google Workspace.
v=spf1 include:_spf.google.com include:amazonses.com include:_spf.hostedemail.com include:_spf.psm.knowbe4.com include:_spf.atlassian.net -allp=reject: meets the requirement and enforces it.
v=DMARC1; p=reject; sp=reject; rua=mailto:1dfdc22fb72e416c8609bbda0450f278@dmarc-reports.cloudflare.net;Look up any other domain with the MX lookup or the email provider lookup.
Hostinger Email at a glance
| Operated by | HOSTINGER INTERNATIONAL LIMITED, 61 Lordou Vironos str., 6023 Larnaca, Cyprus (default contracting entity outside listed countries)Source: Hostinger terms of service |
|---|---|
| MX hosts | mx1.hostinger.com (priority 5) and mx2.hostinger.com (priority 10)Source: Hostinger help: Hostinger Email MX records |
| Address rule | A catch-all sends mail for non-existent mailboxes to one chosen address; the destination must confirm via a link, and only one catch-all can exist per domainSource: Hostinger help: set up a catch-all |
Hostinger domains can be catch-all after a confirmation
Hostinger tells Hostinger Email customers to set `mx1.hostinger.com` and `mx2.hostinger.com`.
Hostinger documents a catch-all that forwards mail for non-existent mailboxes to one address, one per domain. Where it is on, a single-address check cannot confirm a person.
What our checker does behind Hostinger Email
SimpleVerifier doesn't skip or special-case Hostinger Email. For each company domain it offers a random address that can't exist, then your address, and disconnects without sending. If the random address is accepted, the domain is catch-all and its results come back risky with "Accepts all addresses". If it is rejected, your address gets a real answer for that mailbox.
Consumer mailboxes are a separate case; see the Gmail and Yahoo pages. Domains behind Hostinger Email are treated like any company domain.
Cleaning a list full of Hostinger Email domains
Split the list by domain, not by platform. Two companies on Hostinger Email can behave in opposite ways, so a catch-all result at one says nothing about the next. The bulk catch-all checker finds which domains in a list accept everything before you spend time on single addresses.
For catch-all domains, keep addresses with recent replies or sign-ups and send the rest in a small first batch, suppressing anything that hard-bounces. For per-mailbox domains, trust the verdict: invalid addresses will bounce, and valid ones were accepted by the company's own directory. Accept-all vs unknown results covers the difference.
Common questions
- Can you verify addresses at domains behind Hostinger Email?
- It depends on the company. Domains behind Hostinger Email are probed like any other. Hostinger Email answers for the company's own mail rules, so the checker treats every domain on its own: it offers a random address first, and if that is accepted the domain is catch-all and results come back risky ("Accepts all addresses"). Otherwise your address gets a per-mailbox answer. It always checks the syntax, the domain's MX records, disposable domains and role addresses such as info@ first.
- How do I know if a company uses Hostinger Email?
- Look up the domain's MX records. A first MX host ending in hostinger.com means mail goes through Hostinger Email. The email provider lookup and MX lookup tools show it for any domain.
- Are domains behind Hostinger Email catch-all?
- Some are and some aren't; it depends on how each company configured Hostinger Email. A verifier can tell by offering a random address that can't exist: if the domain accepts it, the domain is catch-all and single addresses there can't be confirmed.
- What is hostinger.com in an MX record?
- A domain whose MX is mx1.hostinger.com or mx2.hostinger.com uses Hostinger Email, per Hostinger's MX help.
Related tools
Another provider? See every mailbox provider and what our checker does at each.
Got a list with Hostinger Email addresses?
Sign in with Google and the first 100 addresses are checked free: valid, risky and invalid, with the reason for each row and a file to download. No card. After that, plans start at $9/mo for 2,500 emails a month.
By continuing you agree to our Terms and Privacy Policy.