Skip to content
https://raicultura.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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.
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 301-redirects to HTTPS

www / non-www

200https://www.raicultura.it/
200https://raicultura.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

148
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
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, 80 ms lookup
PASS
1 A records, 80 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 212.162.68.90
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: dnsso1.interbusiness.it, ns2.rai.it, dnsso3.interbusiness.it, ns.rai.it, dnsso2.interbusiness.it, dnsso4.interbusiness.it
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 80 ms
Got: 80 ms
A212.162.68.90
AAAA
CNAME
NSdnsso1.interbusiness.it, ns2.rai.it, dnsso3.interbusiness.it, ns.rai.it, dnsso2.interbusiness.it, dnsso4.interbusiness.it
MX
TXT
_j6z6qd81dssht229qgu6n37jix3p83q
_o63f82c970vakhyv07aeh10mab9ghir
CAALookup not available with standard resolver
Resolved in 80 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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Reverse DNS
1/1 IPs match cert SAN
PASS
1/1 IPs match cert SAN
Info::
PTR for 212.162.68.90 matches certificate SAN: raiplaysound.it
A+
Multi-Resolver DNS Speed
Mean 41ms across 3 resolvers (spread 38ms)
PASS
Mean 41ms across 3 resolvers (spread 38ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 52ms
Got: 52ms via 8.8.8.8:53
Info::
Quad9: 55ms
Got: 55ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 128 ms total
PASS
1 redirect(s), 128 ms total
Info::
Single redirect
Got: https://raicultura.it → https://www.raicultura.it/ (301)
Info::
WWW normalization redirect

https://raicultura.it

114 ms · HTTP/1.0

301

https://www.raicultura.it/

14 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://raicultura.it301114 msHTTP/1.0BigIP
2https://www.raicultura.it/20014 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 75 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 75 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /


Sitemap: https://www.raicultura.it/sitemap.xml


A+
Domain Intelligence
raicultura.it — via DOTNICE-REG, 7 years, 8 months old, hosted on RAI-AS - RAI RadioTelevisione Italiana SPA, IT
PASS
raicultura.it — via DOTNICE-REG, 7 years, 8 months old, hosted on RAI-AS - RAI RadioTelevisione Italiana SPA, IT
Info::
Domain registered until Jan 3, 2027 (4 months remaining)
Info::
Registrar: DOTNICE-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: RAI-AS - RAI RadioTelevisione Italiana SPA, IT
Got: AS8234
Domain expiry

139 days

January 3, 2027

SSL certificate

148 days

Issued by DigiCert Inc

Domain age

7 years, 8 months

Registered January 16, 2019

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

RAI-AS - RAI RadioTelevisione Italiana SPA, IT

ASN AS8234

212.162.68.90

Registrar

DOTNICE-REG

Unlocked 6 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 DOTNICE-REG
Created January 16, 2019 (7 years, 8 months ago)
Expires January 3, 2027 (4 months)
Last Updated January 19, 2026
Name Servers ns.rai.it, ns2.rai.it, dnsso1.interbusiness.it, dnsso2.interbusiness.it, dnsso3.interbusiness.it, dnsso4.interbusiness.it
Registrant RAI Radiotelevisione Italiana S.p.A.
Hosting
IP Address 212.162.68.90
ASN AS8234 (RAI-AS - RAI RadioTelevisione Italiana SPA, IT)
Provider RAI-AS - RAI RadioTelevisione Italiana SPA, IT
Data source: whois (0.7s)

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

Connection waterfall

DNS Lookup 56 ms TCP Connect 37 ms TLS Handshake 39 ms Server Processing 37 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