Skip to content
https://www.studiovarotto.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 89.46.109.48 does not match any cert SAN: webx1377.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.
Info::
PTR lookup failed for 2a00:6d40:4:1::c295:48: lookup 2a00:6d40:4:1::c295:48: 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
TLS Certificate Expiry & Recommendations
72 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

72
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 Cloudflare (host static.coinpaprika.com, 10 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host static.coinpaprika.com, 10 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (static.coinpaprika.com, 10 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: cf-ray: a5189c85fbb2d0b4-CDG
Info::
Assets on Cloudflare: static.coinpaprika.com (assets: 10), cache HIT
Got: cf-ray: a5189c85fbb2d0b4-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • static.coinpaprika.com — Cloudflare · assets: 10 · Cache Status: HIT

Other asset hosts

  • fonts.googleapis.com — assets: 2 · below probe threshold
  • static.medicitalia.it — assets: 1 · below probe threshold
  • www.psicologi-italia.it — 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: 89.46.109.48
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a00:6d40:4:1::c295:48
Info::
No NS records found
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: 57 ms
Got: 57 ms
A89.46.109.48
AAAA2a00:6d40:4:1::c295:48
CNAME—
NS—
MX—
TXT—
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

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
Multi-Resolver DNS Speed
Mean 59ms across 3 resolvers (spread 31ms)
PASS
Mean 59ms across 3 resolvers (spread 31ms)
Info::
Google: 48ms
Got: 48ms via 8.8.8.8:53
Info::
Quad9: 50ms
Got: 50ms via 9.9.9.9:53
Info::
Cloudflare: 79ms
Got: 79ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 888 ms total
PASS
1 redirect(s), 888 ms total
Info::
Single redirect
Got: https://www.studiovarotto.com → https://www.studiovarotto.com/home/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.studiovarotto.com
Info::
Redirect overhead: 888 ms total
Got: 888 ms

https://www.studiovarotto.com

338 ms · HTTP/1.1

302

https://www.studiovarotto.com/home/

550 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.studiovarotto.com302338 msHTTP/1.1aruba-proxy
2https://www.studiovarotto.com/home/200550 msHTTP/1.1aruba-proxy

See the visual redirect chain in the HTTP Probe tab →

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

A+
IPv6 Readiness
IPv6 reachable (34 ms)
PASS
IPv6 reachable (34 ms)
Info::
IPv6 is configured and reachable at 2a00:6d40:4:1::c295:48
Got: 34 ms connect
IPv6 Ready
AAAA Records 2a00:6d40:4:1::c295:48 Connection Reachable (34 ms)
A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 144 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
Sitemap index with 9 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 144 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /alessandra/wp-admin/
Allow: /alessandra/wp-admin/admin-ajax.php

Sitemap: https://www.studiovarotto.com/wp-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 9 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.studiovarotto.com/
301https://studiovarotto.com/

Preferred variant: www

HTTP → HTTPS

301http://www.studiovarotto.com/ → https://www.studiovarotto.com/

Consistent

A+
Domain Intelligence
studiovarotto.com — via Tucows Domains Inc., 14 years, 6 months old
PASS
studiovarotto.com — via Tucows Domains Inc., 14 years, 6 months old
Info::
Domain registered until Jun 19, 2027 (7 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Tucows Domains Inc.
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

223 days

June 19, 2027

SSL certificate

72 days

Issued by Actalis S.p.A.

Domain age

14 years, 6 months

Registered June 19, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a00:6d40:4:1::c295:48

Registrar

Tucows Domains Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created June 19, 2012 (14 years, 6 months ago)
Expires June 19, 2027 (7 months)
Last Updated June 11, 2026
Name Servers dns.technorail.com, dns2.technorail.com, dns3.arubadns.net, dns4.arubadns.cz
DNSSEC Not enabled
Hosting
IP Address 2a00:6d40:4:1::c295:48
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 444 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
53 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.
47 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
445 ms
Total Time Total request time from DNS lookup through full response.
445 ms

Connection waterfall

DNS Lookup 53 ms TCP Connect 37 ms TLS Handshake 47 ms Server Processing 308 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