Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
FHTTP Probe TimingActionTotal 13167 ms — DNS, TCP, TLS, TTFB, content transfer breakdownFIX
Connection waterfall
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 & Recommendations67 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
CCDN & DeliveryActionAssets on AWS CloudFront (host cdn.matomo.cloud, 3 assets); document served directly from originREVIEW
Asset hosts on a CDN
- cdn.matomo.cloud — AWS CloudFront · assets: 3 · Cache Status: Error from cloudfront
Other asset hosts
- static.addtoany.com — assets: 2 · below probe threshold
- widget-accessibilita.vercel.app — assets: 1 · below probe threshold
The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 46 ms lookupPASS
| A | 80.88.84.43 |
| AAAA | — |
| CNAME | — |
| NS | dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz, dns3.arubadns.net |
| MX | 1 ordinemedicilatina-it.mail.protection.outlook.com |
| TXT | google-site-verification=sOdfqbYOknvV48tJwiMEcPRdaxGZ_Bn-d5VOJqxPMcI google-site-verification=clqLLhCu75JhMtMpejnVP9fsEVmyG9MMBo0Zff-BcaI SPF v=spf1 a mx ip4:62.149.142.43/32 include:_spf.aruba.it include:_spf.elasticemail... MS=ms46187941 |
| 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
AMulti-Resolver DNS SpeedMean 29ms across 3 resolvers (spread 65ms)PASS
A+Redirect ChainNo redirect data availablePASS
A+Crawlabilityrobots.txt present, sitemap with 46 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /wp-content/uploads/
Disallow: /ecografia-sbagliata-nasce-bimbo-focomelico-ginecologo-salvato-dalla-prescrizione/
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
- https://ordinemedicilatina.it/wp-sitemap...
ADomain Intelligenceordinemedicilatina.it — via ARUBA-REG, 24 years, 9 months old, hosted on ARUBA-ASN - Aruba S.p.A., ITPASS
42 days
December 21, 2026
67 days
Issued by Let's Encrypt
24 years, 9 months
Registered June 10, 2002
Status unknown
Protects against DNS spoofing
ARUBA-ASN - Aruba S.p.A., IT
ASN AS31034
80.88.84.43
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