Skip to content
https://mediaset.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
9 PASS 8 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/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 52.85.47.17 does not match any cert SAN: server-52-85-47-17.lhr86.r.cloudfront.net
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.
Info::
PTR for 52.85.47.41 does not match any cert SAN: server-52-85-47-41.lhr86.r.cloudfront.net
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.
Info::
PTR for 52.85.47.18 does not match any cert SAN: server-52-85-47-18.lhr86.r.cloudfront.net
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.
Info::
PTR for 52.85.47.73 does not match any cert SAN: server-52-85-47-73.lhr86.r.cloudfront.net
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.
Info::
PTR lookup failed for 2600:9000:2038:cc00:11:46b:8e00:93a1: lookup 2600:9000:2038:cc00:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:2038:de00:11:46b:8e00:93a1: lookup 2600:9000:2038:de00:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:2038:600:11:46b:8e00:93a1: lookup 2600:9000:2038:600:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:2038:a200:11:46b:8e00:93a1: lookup 2600:9000:2038:a200:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:2038:0:11:46b:8e00:93a1: lookup 2600:9000:2038:0:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:2038:8200:11:46b:8e00:93a1: lookup 2600:9000:2038:8200:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:2038:d200:11:46b:8e00:93a1: lookup 2600:9000:2038:d200:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:9000:2038:ae00:11:46b:8e00:93a1: lookup 2600:9000:2038:ae00:11:46b:8e00:93a1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Redirect Chain
2 redirect(s), 279 ms total
REVIEW
2 redirect(s), 279 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://mediaset.it
Info::
Cross-domain redirect detected

https://mediaset.it

84 ms · HTTP/1.1

302

https://www.mediaset.it/

122 ms · HTTP/1.1

302

https://mediasetinfinity.mediaset.it/

72 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mediaset.it30284 msHTTP/1.1Apache
2https://www.mediaset.it/302122 msHTTP/1.1Apache
3https://mediasetinfinity.mediaset.it/20072 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 30 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 30 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *

Disallow: /res/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
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
4 A records, 113 ms lookup
PASS
4 A records, 113 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 52.85.47.17, 52.85.47.41, 52.85.47.18, 52.85.47.73
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:2038:cc00:11:46b:8e00:93a1, 2600:9000:2038:de00:11:46b:8e00:93a1, 2600:9000:2038:600:11:46b:8e00:93a1, 2600:9000:2038:a200:11:46b:8e00:93a1, 2600:9000:2038:0:11:46b:8e00:93a1, 2600:9000:2038:8200:11:46b:8e00:93a1, 2600:9000:2038:d200:11:46b:8e00:93a1, 2600:9000:2038:ae00:11:46b:8e00:93a1
Info::
2 nameserver(s) configured
Got: ns2.f5clouddns.com, ns1.f5clouddns.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 113 ms
Got: 113 ms
A52.85.47.17, 52.85.47.41, 52.85.47.18, 52.85.47.73
AAAA2600:9000:2038:cc00:11:46b:8e00:93a1, 2600:9000:2038:de00:11:46b:8e00:93a1, 2600:9000:2038:600:11:46b:8e00:93a1, 2600:9000:2038:a200:11:46b:8e00:93a1, 2600:9000:2038:0:11:46b:8e00:93a1, 2600:9000:2038:8200:11:46b:8e00:93a1, 2600:9000:2038:d200:11:46b:8e00:93a1, 2600:9000:2038:ae00:11:46b:8e00:93a1
CNAME—
NSns2.f5clouddns.com, ns1.f5clouddns.com
MX
10 mediaset-it.mail.protection.outlook.com
TXT
figma-domain-verification=9866fdc7c7b33632d64c014ed30fe174fd08f206066a6ecdb01c74...
uber-domain-verification=cc0d2de2-112d-492f-8237-10450d942658
bpdg8t86w3ztnj39hpzpfgcxjtgppcg5
MS=ms82821479
anthropic-domain-verification-fkskm2=1q2CdtPS4iBdQ8sG986zGp1oZ
Va87krLg2CV0TkUUCB5wHzXKOpzaUxDJtxj8mIx+UnCQKIvgZd9NiyAXJB2XycjzG/LSO8jQl5pOAKZA...
amazon-business-verification=289a3a789c08cc2a520a352d16b72c3e7fa044045af96a7af21...
openai-domain-verification=dv-PEqMtbxl7Fh1QMtEO8Ta0B6I
c5d005d6898f5e86daae35c7846c7717d968c44b4023498953
4j6jflhhqyhnmxwyqn27344jkwr0r1rq
successfactors-site-verification=ZGJmMGMzYmY3ZjQxY2JiN2I4ZDFkNDhkNzM0NTRkZWUyNmM...
SPF v=spf1 a mx ip4:91.211.156.0/22 ip4:62.77.43.84 a:a6-176.smtp-out.eu-west-1.amaz...
google-site-verification=OT3chdaqXGNu-hi1SwwSYDLa24Jnqae7MtxJEbNPsTw
MS=ms48460700
parallels-domain-verification=0339fa6b93c34437a6415eb967c55177f110441ea8a2427fae...
CgNDkOfvYnRK/dsYTno7MZr/klpi0wH7nCrqtmsgZePMITpoRzt5dL6i9FjAjhTZOaZ0E+evVXfL5f6P...
5f825fcb7510c3ef10a989c9ef97f5a1c01d10063da5be97bf
52B0-39E4-2420-08A4-099E-6782-4DAA-EA8D
jjxdxd2yzw1lq0q7j69bn2vfcxhmcvct
ZOOM_verify_vanCOQ-jRJOvCnu94PazJw
atlassian-domain-verification=AC02pZVGDmPAfv3Sr1YydTvNsV3mJHOgqF8Q4GFroGA8gzGHi4...
apple-domain-verification=JjdSCEBqaMOtM5av
urggj3cha6cau00dahism9uua9
CAALookup not available with standard resolver
Resolved in 113 ms
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 27ms across 3 resolvers (spread 12ms)
PASS
Mean 27ms across 3 resolvers (spread 12ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Quad9: 31ms
Got: 31ms via 9.9.9.9:53
Info::
Cloudflare: 32ms
Got: 32ms via 1.1.1.1:53
A+
IPv6 Readiness
IPv6 reachable (26 ms)
PASS
IPv6 reachable (26 ms)
Info::
IPv6 is configured and reachable at 2600:9000:2038:cc00:11:46b:8e00:93a1, 2600:9000:2038:de00:11:46b:8e00:93a1, 2600:9000:2038:600:11:46b:8e00:93a1, 2600:9000:2038:a200:11:46b:8e00:93a1, 2600:9000:2038:0:11:46b:8e00:93a1, 2600:9000:2038:8200:11:46b:8e00:93a1, 2600:9000:2038:d200:11:46b:8e00:93a1, 2600:9000:2038:ae00:11:46b:8e00:93a1
Got: 26 ms connect
IPv6 Ready
AAAA Records 2600:9000:2038:cc00:11:46b:8e00:93a1, 2600:9000:2038:de00:11:46b:8e00:93a1, 2600:9000:2038:600:11:46b:8e00:93a1, 2600:9000:2038:a200:11:46b:8e00:93a1, 2600:9000:2038:0:11:46b:8e00:93a1, 2600:9000:2038:8200:11:46b:8e00:93a1, 2600:9000:2038:d200:11:46b:8e00:93a1, 2600:9000:2038:ae00:11:46b:8e00:93a1 Connection Reachable (26 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.mediaset.it/
200https://mediaset.it/

Preferred variant: non-www

HTTP → HTTPS

301http://mediaset.it/ → https://mediaset.it/

Consistent

A+
Domain Intelligence
mediaset.it — via REGISTER-REG, 30 years, 9 months old
PASS
mediaset.it — via REGISTER-REG, 30 years, 9 months old
Info::
Domain registered until Dec 1, 2026 (4 months remaining)
Info::
Registrar: REGISTER-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.
Domain expiry

142 days

December 1, 2026

SSL certificate

130 days

Issued by Amazon

Domain age

30 years, 9 months

Registered February 27, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2600:9000:2038:de00:11:46b:8e00:93a1

Registrar

REGISTER-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 REGISTER-REG
Created February 27, 1996 (30 years, 9 months ago)
Expires December 1, 2026 (4 months)
Last Updated December 17, 2025
Name Servers ns1.f5clouddns.com, ns2.f5clouddns.com
Registrant Mediaset S.p.A.
Hosting
IP Address 2600:9000:2038:de00:11:46b:8e00:93a1
Data source: whois (0.6s)

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 126 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
44 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
26 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
29 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
126 ms
Total Time Total request time from DNS lookup through full response.
127 ms

Connection waterfall

DNS Lookup 44 ms TCP Connect 26 ms TLS Handshake 29 ms Server Processing 28 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: LHR86-P3)
Got: x-amz-cf-id: FarSRyuOVJnid9z6_IRnAsfvCI2SChS1pB9xIXnzx_XyM52JcocdIQ==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: FarSRyuOVJnid9z6_IRnAsfvCI2SChS1pB9xIXnzx_XyM52JcocdIQ==
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=7, x-cache=Hit from cloudfront
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback