Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN (document or assets)FIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/1 IPs match cert SANREVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations61 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 40 ms lookupPASS
| A | 178.104.113.107 |
| AAAA | — |
| CNAME | — |
| NS | dara.ns.cloudflare.com, clint.ns.cloudflare.com |
| MX | 10 mx.ambulatoriofacile.it |
| TXT | facebook-domain-verification=rutmmmgob838vamjg5x4vq55763m41 SPF v=spf1 include:_spf.aruba.it -all actalis-dcv=cuuq9ekacia62nj0av4oda7p25 resend-domain-verification=3a7307828621ee7288b5f78fc902256f google-site-verification=d62Flb0qcHjCbEYRqA0f9GLmGkSN4UT8cHhnGVj8S8o |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 28ms across 3 resolvers (spread 10ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://ambulatoriofacile.it
126 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ambulatoriofacile.it | 200 | 126 ms | HTTP/1.1 |
A+Crawlabilityrobots.txt present, sitemap with 181 URLsPASS
# Ambulatorio Facile - robots.txt
# https://ambulatoriofacile.it
#
# Strategia: apertura voluta ai crawler AI. Vogliamo essere letti e citati
# da motori generativi e assistenti, quindi nessun bot AI e' bloccato.
#
# ATTENZIONE, regola dello standard: un crawler che trova un gruppo
# corrispondente al proprio nome IGNORA COMPLETAMENTE il gruppo "*".
# Percio' ogni gruppo esplicito qui sotto deve RIPETERE i propri Disallow:
# senza, i bot elencati striscerebbero anche /api/.
#
# /_next/ resta APERTO di proposito: contiene CSS e JS del sito (/_next/static)
# e le immagini ottimizzate (/_next/image), da cui passano tutte le foto del blog.
# Se fosse bloccato, Googlebot e gli agenti che renderizzano la pagina non
# vedrebbero il layout e le immagini non entrerebbero in Google Immagini.
# Sono file pubblici per definizione: niente da proteggere.
#
# Mappa curata del sito per gli agenti AI: https://ambulatoriofacile.it/llms.txt
User-agent: *
Allow: /
Disallow: /api/
Disallow: /404
# Crawler AI: addestramento, retrieval e citazioni.
# OAI-SearchBot alimenta le citazioni di ChatGPT Search ed e' distinto da
# GPTBot (addestramento) e da ChatGPT-User (navigazione su richiesta utente).
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Google-Extended
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: Claude-SearchBot
User-agent: anthropic-ai
User-agent: Applebot
User-agent: Applebot-Extended
User-agent: CCBot
User-agent: meta-externalagent
User-agent: Meta-ExternalFetcher
User-agent: Amazonbot
User-agent: DuckAssistBot
User-agent: cohere-ai
User-agent: YouBot
User-agent: Diffbot
User-agent: Timpibot
User-agent: Bytespider
Allow: /
Disallow: /api/
Disallow: /404
# Sitemaps
Sitemap: https://ambulatoriofacile.it/sitemap.xml
# Host
Host: https://ambulatoriofacile.it
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use a permanent redirect (301 or 308) instead of a temporary one
ADomain Intelligenceambulatoriofacile.it — via ARUBA-REG, 2 years, 9 months old, hosted on HetznerPASS
75 days
January 23, 2027
61 days
Issued by Let's Encrypt
2 years, 9 months
Registered January 23, 2024
Status unknown
Protects against DNS spoofing
Hetzner
ASN AS24940
178.104.113.107
ARUBA-REG
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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