| Libero | |
|---|---|
| Domains | libero.it, inwind.it, iol.it, blu.it |
| Mail routing | smtp-in.libero.it in September 2026. The legacy inwind.it, iol.it and blu.it domains each publish smtp-in followed by their own name, and all four names resolved to one address when we checked. |
| What we can resolve | We resolve some mailboxes here |
How Libero answers a probe
What the server does when we open a connection and ask about one address.
- Unknown recipients return a 550 under normal conditions.
- Service outages have affected the platform on more than one occasion, and during an outage everything comes back as a temporary failure regardless of the address.
- The legacy domains from earlier Italian internet brands route to the same infrastructure.
- Latency to the platform is high enough that timeout handling matters on a large batch.
The part that catches people out
What we do about it
We score every 4xx as unknown, which matters more here than at a stable provider. If Libero is having a bad day, the report shows lower coverage and says so rather than converting an outage into deletions.
Sending to Libero mailboxes
Verification is one step. These are the things that decide whether the message lands.
- Italian consumer lists concentrate heavily on Libero and Gmail, with Virgilio and Alice making up much of the rest.
- Consent documentation matters under Italian implementations of EU rules.
- If bounce rates on an Italian segment spike suddenly, check whether Libero is up before rebuilding the list.
The last week of January 2023
Libero and Virgilio mail went dark for roughly five days in late January 2023. Users couldn't log in, and mail sent to them queued or failed with temporary errors. Say you had run a 12,000-row Italian list that week, with 3,500 rows on libero.it. A tool that reads "no answer" as "no mailbox" would have marked all 3,500 invalid. You'd have removed close to a third of your Italian audience, and by the following week those mailboxes were receiving again.
Scored properly, that run shows 3,500 unknowns and a coverage figure that drops off a cliff for one provider only. That shape is the clue you're looking for. Real list decay is spread across domains. A sudden hole in one operator's rows means the operator is having a bad day, and the right response is to wait and run those rows again.
Virgilio belongs in the same group
Italiaonline runs both brands, which is why they failed together. The DNS shows a shared naming scheme: on September 19, 2026, libero.it returned smtp-in.libero.it, and inwind.it, iol.it, blu.it and virgilio.it each returned smtp-in followed by their own domain name. Those hostnames differ and the company doesn't. If your reports treat Virgilio as a separate provider, a platform incident will look like two unrelated problems.
Before a large Italian run, do a thirty-second health check. Search the news for the provider's name plus the word down, and look at your own delivery log for libero.it over the last hour. If deferrals are piling up, postpone the verification. You lose nothing by waiting, since unknowns aren't billed, but you save yourself a results file that's one third question marks and a client asking what went wrong.
Questions people ask
Why does Libero coverage change between runs?
Because the platform's availability changes. During an incident the servers return temporary failures for everything, which we report as unknown rather than turning into invalid verdicts.
What are inwind.it and iol.it?
Older Italian internet brands whose mail was folded into Libero. The addresses still work and route to the same servers.
Should Italian lists be verified differently?
Verify them when the provider is healthy, and treat a sudden collapse in coverage as a provider signal rather than a list signal.