VirusTotal
1 / 91 engine detections
Open reportmail1.libero.it is a blocklisted domain detected by PhishDestroy on 2026-09-16. Risk: critical (71/100). Registrar: Reevo s.p.a. Status: Last known active. Hosting: Italiaonline S.p.A. VirusTotal: 1/91 engines flag it. Do not enter credentials or connect a wallet.
“302 Found”
1 / 91 engine detections
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
mail1.libero.it is a mail-named host under the libero.it domain that PhishDestroy added to its blocklist on 2026-09-16. It has not been assigned a specific scheme type, and no impersonated brand or targeted audience has been established beyond what the hostname suggests. As of 2026-10-19 the site was alive and answering visitors with a redirect rather than serving a page of its own.
The page title is simply "302 Found", a standard HTTP response that forwards the browser elsewhere. The title therefore reveals nothing about the final destination, and no login form or wallet prompt has been documented. The risk to watch for is a mail-named address passing visitors on to a page that asks for credentials. Anyone who lands on a sign-in screen after following this host should treat the request for a username and password with caution.
Independent support for the listing is thin. On 2026-10-03, one of 91 VirusTotal engines (URLQuery) flagged the host, and the other 90 returned no detection. PhishDestroy is the only blocklist carrying it. A single vendor hit is weak evidence, so readers should treat this as a precautionary listing rather than a confirmed phishing operation.
The host resolves to 213.209.0.20 on the Italiaonline S.p.A. network in Italy, and the domain is registered through Reevo s.p.a. Its certificate is an organization-validated certificate from Sectigo. That level of validation requires the certificate authority to verify a named organization, which is more vetting than a typical throwaway phishing host receives. Taken together, the Italian hosting, the registrar and the validated certificate point to an established operator rather than freshly built scam infrastructure.
If you followed a link through this host and then entered your mail password, change it from a bookmarked or typed address and turn on two-factor authentication. Check your account for forwarding rules or sessions you do not recognize. Defenders should log and review traffic to this host, especially where it leads to credential pages. Given the single detection, they should weigh blocking against the likelihood of a false positive and report confirmed misuse to the network operator.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 90f9189b-b0e3-4eb0-addb-53b752c29b5b |
|---|---|
| Final url | https://mail1.libero.it/appsuite/ |
| Status | 200 |
| Redirected | same-domain |
| History | [
{
"url": "https://mail1.libero.it/",
"status": 302
},
{
"url": "http://mail1.libero.it/appsuite/",
"status": 307
},
{
"url": "https://mail1.libero.it/appsuite/",
"status": 200
}
] |
| DOM structure hash | 8d2c8fb5fe129c36cd8d698cafe8f2f0e03852897f972fd97482f08e39213725 |
| Document hash | 6c4c9bd88b4cdc180c447261200579d771d50c7de369b3a18bc6a42fae9dbf24 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "mail1.libero.it",
"type": "A",
"value": "213.209.0.20"
}
] |
| Dnssec valid | false |
| Ip | 213.209.0.20 |
| Registration record | {
"registrar": "IOL-REG",
"created": "1999-06-03T00:00:00Z",
"updated": "2026-06-19T00:51:22Z",
"expires": "2027-06-03T00:00:00Z",
"nameservers": [
"ns1.italiaonline.it",
"ns2.iol.it"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 56,
"malicious": 0,
"suspicious": 0,
"undetected": 36
} |
|---|---|
| Reputation | 0 |
| Popularity | {
"Cisco Umbrella": 136324
} |
| First seen | 2023-09-28T20:04:06Z |
| DNS records | [
{
"ttl": 21600,
"type": "A",
"value": "213.209.0.20"
}
] |
| Dns at | 2026-10-14T13:22:44Z |
| Jarm | 29d29d00000000000041d41d00041da2ef8628b895cf67790015cc09f2affc |
| Certificate | {
"san": [
"*.libero.it",
"libero.it"
],
"issuer": "Sectigo Limited / Sectigo Public Server Authentication CA OV R36",
"serial": "f910591b0ca71b086ec4cda05d0de89f",
"sha256": "616f7e8014a268eb4c479d36b9ef00a218014dea965d8c4d54504b398ec3d77e",
"subject": "*.libero.it",
"valid_to": "2027-01-08T23:59:59Z",
"valid_from": "2026-06-24T00:00:00Z"
} |
| Registration record | {
"dnssec": "no"
} |
No. PhishDestroy classifies mail1.libero.it as a blocklisted domain (risk: critical, 71/100); it was first detected on 2026-09-16. VirusTotal: 1/91 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on mail1.libero.it. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
ns2.iol.itLocation describes the IP network.
616f7e8014a268eb4c479d36b9ef00a218014dea965d8c4d54504b398ec3d77elibero.itSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of mail1.libero.it · checked Sep 23, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
redirected
http_redirect
Reachable
No threat flag
View source1/91 engine detections
View sourcemail1.libero.it
View source1 community report
CategorySEXTORTION
16pQ54sHsqQrUR2nYQsf2r7g93nwc37k2j
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
mail1.libero.it
“16pQ54sHsqQrUR2nYQsf2r7g93nwc37k2j”
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
mail1.libero.it)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.