Rename 'aquila.it' to 'laquila.it'#2747
Conversation
|
Good catch. Although it appears that both LAquila.it and Aquila.it exist in the most recent version of the registry’s publication These do not appear to be controlled by NIC.IT and are highly likely in the hands of someone other than the registry. The ones controlled by the registry usually resolves to something look like this: Additionally, there are three more entries in the .it section which show similar indicator (privately-controlled nameservers) in WHOIS, suggesting they might also not be controlled by the registry. aquila.itSpam websites:
trentinosudtirol.itvaldaosta.italtoadige.it |
|
I sent an email to the NIC.IT contact (cc'd @simon-friedberger and @dnsguru ) |

This PR requests the removal of aquila.it from the Public Suffix List, as it does not represent a valid public suffix for administrative subdomains in Italy and replace it with laquila.it.
https://www.comune.laquila.it/
The domain aquila.it is not the administrative suffix under which municipal or provincial subdomains are delegated. Its inclusion in the PSL therefore misrepresents the real domain hierarchy.
A WHOIS lookup further confirms the mismatch between administrative use and domain ownership:
$ whois laquila.it
Domain: laquila.it
Status: UNASSIGNABLE
This indicates that laquila.it is reserved and not registrable, consistent with its role as an institutional domain.
$ whois aquila.it
Domain: aquila.it
Status: ok
Created: 2012-11-30
Registrant:
Organization: Puglia.com Srls
Admin / Technical Contact:
Domain Profit Srl
Registrar:
Algorithmedia S.r.l.
This shows that aquila.it is a privately registered domain, owned and operated by commercial entities, and not delegated by any public authority.
While investigating certificate issuance patterns, we observed thousands of TLS certificates issued for arbitrary subdomains of aquila.it, many of which resemble phishing or impersonation attempts (for example comune.aquila.it):
https://crt.sh/?q=comune.aquila.it
At the time of writing, aquila.it resolves using a wildcard configuration, responding to essentially any subdomain with the same IP address.