Skip to content
https://it-servizioclienti.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
11
PASS
6
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
17
6 PASS 11 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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.182.123: lookup 172.67.182.123: 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 104.21.67.231: lookup 104.21.67.231: 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 2606:4700:3034::6815:43e7: lookup 2606:4700:3034::6815:43e7: 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 2606:4700:3034::ac43:b67b: lookup 2606:4700:3034::ac43:b67b: 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.
C
Multi-Resolver DNS Speed
Action
Mean 84ms across 3 resolvers (spread 232ms)
REVIEW
Mean 84ms across 3 resolvers (spread 232ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 13ms
Got: 13ms via 8.8.8.8:53
Info::
Quad9: 236ms
Got: 236ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 232ms (min 4ms / max 236ms)
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
Redirect Chain
1 redirect(s), 3393 ms total
REVIEW
1 redirect(s), 3393 ms total
Info::
Single redirect
Got: https://it-servizioclienti.it → https://www.it-servizioclienti.it/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 3393 ms total
Got: 3393 ms

https://it-servizioclienti.it

2193 ms · HTTP/1.1

301

https://www.it-servizioclienti.it/

1200 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://it-servizioclienti.it3012193 msHTTP/1.1cloudflare
2https://www.it-servizioclienti.it/2001200 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1248 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 1248 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a content-signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a content-signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a content signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via content signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.it-servizioclienti.it/
200https://it-servizioclienti.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://it-servizioclienti.it/ https://it-servizioclienti.it/

Consistent

B
HTTP Probe Timing
Total 1423 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
17 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
88 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
460 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.42 s
Total Time Total request time from DNS lookup through full response.
1.42 s

Connection waterfall

DNS Lookup 17 ms TCP Connect 88 ms TLS Handshake 460 ms Server Processing 859 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
89 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

89
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
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
2 A records, 141 ms lookup
PASS
2 A records, 141 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.182.123, 104.21.67.231
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3034::6815:43e7, 2606:4700:3034::ac43:b67b
Info::
2 nameserver(s) configured
Got: sue.ns.cloudflare.com, terin.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
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: 141 ms
Got: 141 ms
A172.67.182.123, 104.21.67.231
AAAA2606:4700:3034::6815:43e7, 2606:4700:3034::ac43:b67b
CNAME
NSsue.ns.cloudflare.com, terin.ns.cloudflare.com
MX
1 smtp.secureserver.net
10 mailstore1.secureserver.net
TXT
CAALookup not available with standard resolver
Resolved in 141 ms

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+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3034::6815:43e7, 2606:4700:3034::ac43:b67b
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:3034::6815:43e7, 2606:4700:3034::ac43:b67b Connection Reachable (1 ms)
A+
Domain Intelligence
it-servizioclienti.it — via 1API-REG, 10 years, 3 months old
PASS
it-servizioclienti.it — via 1API-REG, 10 years, 3 months old
Info::
Domain registered until Jul 5, 2027 (10 months remaining)
Info::
Registrar: 1API-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

296 days

July 5, 2027

SSL certificate

89 days

Issued by Google Trust Services

Domain age

10 years, 3 months

Registered July 5, 2016

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3034::ac43:b67b

Registrar

1API-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 1API-REG
Created July 5, 2016 (10 years, 3 months ago)
Expires July 5, 2027 (10 months)
Last Updated July 21, 2026
Name Servers sue.ns.cloudflare.com, terin.ns.cloudflare.com
Registrant Mirkovic Group AB
Hosting
IP Address 2606:4700:3034::ac43:b67b
Data source: whois (1.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
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: NRT)
Got: cf-ray: a35dc28c2f33d767-NRT
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a35dc28c2f33d767-NRT
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback