Skip to content
https://capri-world.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 9 REVIEW 1 FIX
D
Multi-Resolver DNS Speed
Action
Mean 305ms across 3 resolvers (spread 689ms)
FIX
Mean 305ms across 3 resolvers (spread 689ms)
Info::
Quad9: 58ms
Got: 58ms via 9.9.9.9:53
Info::
Google: 112ms
Got: 112ms via 8.8.8.8:53
Info::
Cloudflare: 747ms
Got: 747ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 689ms (min 58ms / max 747ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
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 93.42.238.68 does not match any cert SAN: host-68.pointel.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
TLS Certificate Expiry & Recommendations
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 3 assets); document served directly from origin
REVIEW
Assets on Bunny CDN (host cdn.iubenda.com, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (Bunny CDN serves the assets)
The page's subresources are delivered by Bunny CDN (cdn.iubenda.com, 3 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 cdn-iubenda.b-cdn.net
Info::
Assets on Bunny CDN: cdn.iubenda.com (assets: 3)
Got: delegation cdn-iubenda.b-cdn.net
Warning: Assets on a CDN, document is not: Bunny CDN
Document origin not attributed

Asset hosts on a CDN

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

Other asset hosts

  • img.youtube.com — assets: 10 · Google
  • cs.iubenda.com — assets: 2 · below probe threshold
  • fonts.googleapis.com — assets: 2 · below probe threshold
  • www.capri-world.com — assets: 1 · below probe threshold
  • www.youtube.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: connection error, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 113 ms lookup
PASS
1 A records, 113 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 93.42.238.68
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.pointel.it, ns3.pointel.it, ns2.pointel.it
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 113 ms
Got: 113 ms
A93.42.238.68
AAAA—
CNAME—
NSns1.pointel.it, ns3.pointel.it, ns2.pointel.it
MX
0
TXT
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 113 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://capri-world.com

https://capri-world.com

141 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://capri-world.com200141 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 17 URLs
PASS
robots.txt present, sitemap with 17 URLs
Info::
robots.txt is present
Got: 163 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 17 entries
Info::
Sitemap index with 17 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 163 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php


Sitemap: https://capri-world.com/sitemap.xml

Sitemap: https://capri-world.com/sitemap.rss
sitemap.xml 200 OK
Type Sitemap Index URLs 17 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: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.capri-world.com/
200https://capri-world.com/

Preferred variant: non-www

HTTP → HTTPS

301http://capri-world.com/ → https://capri-world.com/

Consistent

A
Domain Intelligence
capri-world.com — via Total Web Solutions Limited, 27 years, 3 months old, hosted on FASTWEB - Fastweb SpA, IT
PASS
capri-world.com — via Total Web Solutions Limited, 27 years, 3 months old, hosted on FASTWEB - Fastweb SpA, IT
Warning::
Domain expires in 36 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Dec 12, 2026
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: Total Web Solutions Limited
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: FASTWEB - Fastweb SpA, IT
Got: AS12874
Domain expiry

34 days

December 12, 2026

SSL certificate

86 days

Issued by Let's Encrypt

Domain age

27 years, 3 months

Registered December 12, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

FASTWEB - Fastweb SpA, IT

ASN AS12874

93.42.238.68

Registrar

Total Web Solutions Limited

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Total Web Solutions Limited
Created December 12, 1999 (27 years, 3 months ago)
Expires December 12, 2026 (1 months)
Last Updated December 13, 2025
Name Servers ns1.pointel.it, ns2.pointel.it, ns3.pointel.it
DNSSEC Not enabled
Hosting
IP Address 93.42.238.68
ASN AS12874 (FASTWEB - Fastweb SpA, IT)
Provider FASTWEB - Fastweb SpA, IT
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

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

Send Feedback