Skip to content
https://www.alessandrorosina.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 94.23.64.40 does not match any cert SAN: cluster011.ovh.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.
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
TLS Certificate Expiry & Recommendations
47 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

47
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 Bunny CDN (host cdn.iubenda.com, 6 assets); document served directly from origin (OVH)
REVIEW
Assets on Bunny CDN (host cdn.iubenda.com, 6 assets); document served directly from origin (OVH)
Warning::
Document not behind existing CDN (Bunny CDN serves the assets)
The page's subresources are delivered by Bunny CDN (cdn.iubenda.com, 6 assets), but the HTML document itself comes straight from the origin (OVH). 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 cdn-iubenda.b-cdn.net
Info::
Assets on Bunny CDN: cdn.iubenda.com (assets: 6)
Got: delegation cdn-iubenda.b-cdn.net
Warning: Assets on a CDN, document is not: Bunny CDN
Document origin OVH

Asset hosts on a CDN

  • cdn.iubenda.com — Bunny CDN · assets: 6

Other asset hosts

  • cdn-images.mailchimp.com — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 2 · below probe threshold
  • cs.iubenda.com — assets: 1 · below probe threshold
  • platform.twitter.com — assets: 1 · below probe threshold
  • platform.x.com — assets: 1 · below probe threshold
  • stats.wp.com — assets: 1 · below probe threshold
  • www.google.com — assets: 1 · below probe threshold
  • www.gstatic.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.
A
DNS Records
1 A records, 54 ms lookup
PASS
1 A records, 54 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 94.23.64.40
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: alessandrorosina.it
Info::
2 nameserver(s) configured
Got: dns111.ovh.net, ns111.ovh.net
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 54 ms
Got: 54 ms
A94.23.64.40
AAAA—
CNAMEalessandrorosina.it
NSdns111.ovh.net, ns111.ovh.net
MX
1 mx1.ovh.net
5 mx2.ovh.net
100 mxb.ovh.net
TXT
SPF v=spf1 include:mx.ovh.com ~all
google-site-verification=0GxtMQSFmSYbk0jzTBQLxmP8RNCREgIX9DhYyGdVVYw
CAALookup not available with standard resolver
Resolved in 54 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 CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A
Multi-Resolver DNS Speed
Mean 42ms across 3 resolvers (spread 51ms)
PASS
Mean 42ms across 3 resolvers (spread 51ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 37ms
Got: 37ms via 1.1.1.1:53
Info::
Quad9: 71ms
Got: 71ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.alessandrorosina.it

https://www.alessandrorosina.it

401 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.alessandrorosina.it200401 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 16 URLs
PASS
robots.txt present, sitemap with 16 URLs
Info::
robots.txt is present
Got: 0 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 16 entries
Info::
Sitemap index with 16 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 0 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
sitemap.xml 200 OK
Type Sitemap Index URLs 16 entries Valid XML Yes
Child Sitemaps:
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: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.alessandrorosina.it/
301https://alessandrorosina.it/

Preferred variant: www

HTTP → HTTPS

301http://www.alessandrorosina.it/ → https://www.alessandrorosina.it/

Consistent

A+
Domain Intelligence
alessandrorosina.it — via OVH-REG, 11 years, 10 months old, hosted on OVH
PASS
alessandrorosina.it — via OVH-REG, 11 years, 10 months old, hosted on OVH
Info::
Domain registered until Feb 16, 2027 (3 months remaining)
Info::
Registrar: OVH-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: OVH
Got: AS16276
Domain expiry

99 days

February 16, 2027

SSL certificate

47 days

Issued by Let's Encrypt

Domain age

11 years, 10 months

Registered February 16, 2015

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

94.23.64.40

Registrar

OVH-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 OVH-REG
Created February 16, 2015 (11 years, 10 months ago)
Expires February 16, 2027 (3 months)
Last Updated March 4, 2026
Name Servers dns111.ovh.net, ns111.ovh.net
Registrant hidden
Hosting
IP Address 94.23.64.40
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
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 510 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
70 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
20 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
26 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
490 ms
Total Time Total request time from DNS lookup through full response.
510 ms

Connection waterfall

DNS Lookup 70 ms TCP Connect 20 ms TLS Handshake 26 ms Server Processing 374 ms Content Transfer 20 ms
A+
Health Check Endpoint
Health endpoint at https://www.alessandrorosina.it/health (HTTP 200)
PASS
Health endpoint at https://www.alessandrorosina.it/health (HTTP 200)
Info::
Public health endpoint at https://www.alessandrorosina.it/health
Got: https://www.alessandrorosina.it/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback