Skip to content
https://la7.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 10 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 66.71.163.97 does not match any cert SAN: host97-163-71-66.serverdedicati.aruba.it
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.la7.it/
200https://la7.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://la7.it/ https://www.la7.it/

Consistent

B
TLS Certificate Expiry & Recommendations
39 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

39
days left
0d 30d 60d 90d+

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
C
CDN & Delivery
Action
Assets on AWS CloudFront (host www.la7.it, 33 assets); document served directly from origin
REVIEW
Assets on AWS CloudFront (host www.la7.it, 33 assets); document served directly from origin
Warning::
Document not behind existing CDN (AWS CloudFront serves the assets)
The page's subresources are delivered by AWS CloudFront (www.la7.it, 33 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation d1d6aygaizfsos.cloudfront.net
Info::
Assets on AWS CloudFront: www.la7.it (assets: 33), cache Hit from cloudfront
Got: delegation d1d6aygaizfsos.cloudfront.net
Info::
Assets on AWS CloudFront: cdn-gl.imrworldwide.com (assets: 3), cache Hit from cloudfront
Got: delegation d2926jmvsihu4k.cloudfront.net
Info::
Assets on AWS CloudFront: components2.corriereobjects.it (assets: 3), cache Hit from cloudfront
Got: delegation d2licdfz31ol73.cloudfront.net
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin not attributed

Asset hosts on a CDN

  • www.la7.it — AWS CloudFront · assets: 33 · Cache Status: Hit from cloudfront
  • cdn-gl.imrworldwide.com — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront
  • components2.corriereobjects.it — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront

Other asset hosts

  • components2.rcsobjects.it — assets: 2 · below probe threshold
  • fundingchoicesmessages.google.com — assets: 2 · below probe threshold
  • securepubads.g.doubleclick.net — assets: 2 · below probe threshold
  • static.chartbeat.com — assets: 2 · below probe threshold
  • c2.taboola.com — assets: 1 · below probe threshold
  • cdn.permutive.app — assets: 1 · below probe threshold
  • cdn.taboola.com — assets: 1 · below probe threshold
  • imasdk.googleapis.com — assets: 1 · below probe threshold
  • js.tncid.app — assets: 1 · below probe threshold
  • micro.rubiconproject.com — assets: 1 · below probe threshold
  • nr-events.taboola.com — assets: 1 · below probe threshold
  • tg.la7.it — assets: 1 · below probe threshold
  • www.googletagmanager.com — 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.

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 57 ms lookup
PASS
1 A records, 57 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 66.71.163.97
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: master.iltrovatore.it, ns2.it.colt.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 57 ms
Got: 57 ms
A66.71.163.97
AAAA
CNAME
NSmaster.iltrovatore.it, ns2.it.colt.net
MX
0 la7-it.mail.protection.outlook.com
TXT
SPF v=spf1 ip4:82.112.222.12 ip4:82.112.222.9 ip4:82.112.222.10 ip4:82.112.222.20 in...
google-site-verification=0Rh4FXiquH8plmMout8te5nuWQ37x16afk7esz__BWE
tIIPzkuzDfeB+yoHo8kqfrp3EYfpQejTR0/U8M1dbWy1Qe/SwaD5NNKQcM0eskOPLGWx8yx4uV5kTr+a...
apple-domain-verification=ivyLvBz4lGimVuAa
i0J2JJNUr7RhTpg33VpR3oqxwr8Zza6R5ZtMQfZ1jGnfrqmiLoJ8UQWyMy0SN9Uwpqaz9bJcwJJ97cwO...
CAALookup not available with standard resolver
Resolved in 57 ms

Multiple A records provide failover if one server goes down.

Why this matters

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 Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 31ms across 3 resolvers (spread 53ms)
PASS
Mean 31ms across 3 resolvers (spread 53ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 40ms
Got: 40ms via 1.1.1.1:53
Info::
Google: 54ms
Got: 54ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 178 ms total
PASS
1 redirect(s), 178 ms total
Info::
Single redirect
Got: https://la7.it → https://www.la7.it/ (301)
Info::
WWW normalization redirect

https://la7.it

92 ms · HTTP/1.1

301

https://www.la7.it/

85 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://la7.it30192 msHTTP/1.1
2https://www.la7.it/20085 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 63 URLs
PASS
robots.txt present, sitemap with 63 URLs
Info::
robots.txt is present
Got: 3358 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 63 entries
Info::
Sitemap index with 63 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3358 B Sitemaps referenced 4 User-agents *, Yandex, GPTBot, anthropic-ai, SemrushBot, SemrushBot-BA, SemrushBot-SI, SemrushBot-CT, SemrushBot-BM, PetalBot, CCBot, Google-Extended, SemrushBot-SWA, AmazonAdBot Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: PetalBot
Disallow: /

User-agent: Yandex
Disallow: / # prohibits crawling for the entire site

User-agent: GPTBot
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: SemrushBot
Disallow: /

User-agent: SemrushBot-BA
Disallow: /

User-agent: SemrushBot-SI
Disallow: /

User-agent: SemrushBot-SWA
Disallow: /

User-agent: SemrushBot-CT
Disallow: /

User-agent: SemrushBot-BM
Disallow: /

User-agent: AmazonAdBot
Allow: /

User-agent: *
Crawl-delay: 10
# CSS, JS, Images
Allow: /misc/*.css$
Allow: /misc/*.css?
Allow: /misc/*.js$
Allow: /misc/*.js?
Allow: /misc/*.gif
Allow: /misc/*.jpg
Allow: /misc/*.jpeg
Allow: /misc/*.png
Allow: /modules/*.css$
Allow: /modules/*.css?
Allow: /modules/*.js$
Allow: /modules/*.js?
Allow: /modules/*.gif
Allow: /modules/*.jpg
Allow: /modules/*.jpeg
Allow: /modules/*.png
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/
Disallow: /laria-che-tira/video/palermo-spunta-i-libro-mastro-delle-tangenti-02-11-2015-166244
Disallow: /embedded/la7?w=640&h=360&tid=player&content=385606
Disallow: /*?query=
Disallow: /*?op=cerca&query=
Disallow: /*?page=
Disallow: /*?qstring=
Disallow: /piazzapulita/video/il-caso-armellini-tra-evasione-ed-edilizia-a-pezzi-04-02-2014-125985
Disallow: */ricerca*

Sitemap: https://www.la7.it/sites/default/files/sitemap-xml/sitemap_index.xml
Sitemap: https://www.la7.it/sites/default/files/sitemap-xml/sitemap_index-la7d.xml
Sitemap: https://www.la7.it/sites/default/files/sitemap-xml/sitemap_index-la7cinema.xml
Sitemap: https://www.la7.it/La7/feed

sitemap.xml 200 OK
Type Sitemap Index URLs 63 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
la7.it — via RETELIT-REG, 25 years, 8 months old, hosted on ARUBAENTERPRISE-ASN - Aruba S.p.A., IT
PASS
la7.it — via RETELIT-REG, 25 years, 8 months old, hosted on ARUBAENTERPRISE-ASN - Aruba S.p.A., IT
Info::
Domain registered until Jun 24, 2027 (9 months remaining)
Info::
Registrar: RETELIT-REG
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: ARUBAENTERPRISE-ASN - Aruba S.p.A., IT
Got: AS213224
Domain expiry

276 days

June 24, 2027

SSL certificate

39 days

Issued by Let's Encrypt

Domain age

25 years, 8 months

Registered May 4, 2001

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ARUBAENTERPRISE-ASN - Aruba S.p.A., IT

ASN AS213224

66.71.163.97

Registrar

RETELIT-REG

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RETELIT-REG
Created May 4, 2001 (25 years, 8 months ago)
Expires June 24, 2027 (9 months)
Last Updated June 30, 2026
Name Servers ns2.it.colt.net, master.iltrovatore.it
Registrant La7 S.p.A.
Hosting
IP Address 66.71.163.97
ASN AS213224 (ARUBAENTERPRISE-ASN - Aruba S.p.A., IT)
Provider ARUBAENTERPRISE-ASN - Aruba S.p.A., IT
Data source: whois (0.9s)

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.

Why this matters

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

A+
HTTP Probe Timing
Total 146 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
55 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
29 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
33 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
147 ms
Total Time Total request time from DNS lookup through full response.
147 ms

Connection waterfall

DNS Lookup 55 ms TCP Connect 29 ms TLS Handshake 33 ms Server Processing 29 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback