Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations62 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 147 ms lookupPASS
| A | 104.21.76.85, 172.67.191.151 |
| AAAA | 2606:4700:3031::ac43:bf97, 2606:4700:3033::6815:4c55 |
| CNAME | — |
| NS | lennox.ns.cloudflare.com, tani.ns.cloudflare.com |
| MX | 10 mail.villagesitaly.com |
| TXT | SPF v=spf1 mx ip6:2a01:4f8:1c1b:e048::1 -all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 7ms across 3 resolvers (spread 6ms)PASS
A+Redirect Chain0 redirect(s), 47 ms totalPASS
https://villagesitaly.com
47 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://villagesitaly.com | 301 | 47 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 30 URLsPASS
# robots.txt — villagesitaly.com
# Gestito da: Rank Math SEO + DGM Access
User-agent: *
Allow: /
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-login.php
# ASSET DI RENDERING SEMPRE CRAWLABILI (2026-07-09): la regola Allow piu' LUNGA vince sia sul
# Disallow /*?* (che altrimenti blocca i CSS/JS versionati ?ver=...) sia su /wp-includes/.
# Senza queste righe Googlebot renderizza le pagine SENZA stili -> qualita' percepita a picco.
Allow: /wp-content/themes/
Allow: /wp-content/plugins/
Allow: /wp-content/uploads/
Allow: /wp-includes/css/
Allow: /wp-includes/js/
Disallow: /xmlrpc.php
# FEED: NON bloccati di proposito (30/07/2026). Rispondono 410 Gone via
# mu-plugins/vi-feed-cleanup.php (tranne /feed/ e /it/feed/, che restano ma sono noindex).
# Un Disallow qui impedirebbe a Google di SCARICARE l'URL, quindi di vedere il 410:
# resterebbero in elenco per sempre come "bloccati da robots". Il 410 li elimina davvero.
Disallow: /wp-json/
Allow: /wp-admin/admin-ajax.php
# Tutte le query string (?s=, ?regione=, ?provincia=, ?tema=, ?rb=, ?viam_click=, ?p=, ecc.):
# nessun contenuto reale del sito vive dietro un parametro — borghi, regioni, province, temi
# sono tutti path puliti. Un blocco unico chiude ogni variante presente E futura, invece di
# rincorrere parametro per parametro (vedi il caso /contact/?rb= dimenticato il 04/07/2026).
Disallow: /*?*
# Pagine autore — contenuto AI, no valore SEO
Disallow: /author/
# Sicurezza — file sensibili e endpoint di attacco
Disallow: /.env
Disallow: /.git/
Disallow: /backend/
Disallow: /api/
Sitemap: https://www.villagesitaly.com/sitemap_index.xml
# === AI crawlers ===
# ChatGPT-User e PerplexityBot (ricerca live degli utenti) INTENZIONALMENTE consentiti
# (rientrano nelle regole di User-agent: *) → il sito può essere citato in ChatGPT/Perplexity.
# I bot di training restano bloccati.
User-agent: GPTBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: Omgilibot
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: YouBot
Disallow: /
User-agent: Diffbot
Disallow: /
User-agent: img2dataset
Disallow: /
# === SEO scraper aggressivi — bloccati ===
User-agent: MJ12bot
Disallow: /
User-agent: DotBot
Disallow: /
User-agent: BLEXBot
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: Proximic
Disallow: /
# === Exploit / vulnerability scanner — bloccati ===
User-agent: Nikto
Disallow: /
User-agent: sqlmap
Disallow: /
User-agent: zgrab
Disallow: /
User-agent: Nuclei
Disallow: /
- https://www.villagesitaly.com/post-sitem...
- https://www.villagesitaly.com/page-sitem...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/borgo-site...
- https://www.villagesitaly.com/vfa_prodot...
- https://www.villagesitaly.com/category-s...
- https://www.villagesitaly.com/regione-si...
- https://www.villagesitaly.com/provincia-...
- https://www.villagesitaly.com/provincia-...
- https://www.villagesitaly.com/tema-sitem...
- https://www.villagesitaly.com/interesse-...
A+Domain Intelligencevillagesitaly.com — via Register SPA, 8 months oldPASS
118 days
February 16, 2027
62 days
Issued by Let's Encrypt
8 months
Registered February 16, 2026
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3033::6815:4c55
Register SPA
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice
AHTTP Probe TimingTotal 763 ms — DNS, TCP, TLS, TTFB, content transfer breakdownPASS
Connection waterfall
ACDN & DeliveryDocument and assets on CloudflarePASS
Asset hosts on a CDN
- www.villagesitaly.com — Cloudflare · assets: 66 · Cache Status: HIT
- media.villagesitaly.com — Cloudflare · assets: 36 · Cache Status: DYNAMIC
Other asset hosts
- connect.facebook.net — assets: 1 · below probe threshold
- www.googletagmanager.com — assets: 1 · below probe threshold