Skip to content
https://agenziaseolatina.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
12
PASS
5
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
5 PASS 12 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 57.131.134.102 does not match any cert SAN: vps-e73ba283.vps.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.
B
Multi-Resolver DNS Speed
Mean 162ms across 3 resolvers (spread 18ms)
REVIEW
Mean 162ms across 3 resolvers (spread 18ms)
Info::
Cloudflare: 151ms
Got: 151ms via 1.1.1.1:53
Info::
Google: 166ms
Got: 166ms via 8.8.8.8:53
Info::
Quad9: 169ms
Got: 169ms via 9.9.9.9:53
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.agenziaseolatina.it/
200https://agenziaseolatina.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://agenziaseolatina.it/ → https://agenziaseolatina.it/

Consistent

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

Connection waterfall

DNS Lookup 307 ms TCP Connect 160 ms TLS Handshake 169 ms Server Processing 166 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
31 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

31
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, 7 assets); document served directly from origin (OVH)
REVIEW
Assets on Bunny CDN (host cdn.iubenda.com, 7 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, 7 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: 7)
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: 7

Other asset hosts

  • cs.iubenda.com — assets: 2 · 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, 311 ms lookup
PASS
1 A records, 311 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 57.131.134.102
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns106.ovh.net, ns106.ovh.net
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (311 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 311 ms
A57.131.134.102
AAAA—
CNAME—
NSdns106.ovh.net, ns106.ovh.net
MX
1 mx1.mail.ovh.net
5 mx2.mail.ovh.net
100 mx3.mail.ovh.net
TXT
SPF v=spf1 include:mx.ovh.com -all
1|www.agenziaseolatina.it
CAALookup not available with standard resolver
Resolved in 311 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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://agenziaseolatina.it

https://agenziaseolatina.it

817 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://agenziaseolatina.it200817 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 72 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 72 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://agenziaseolatina.it/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 9 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
agenziaseolatina.it — via OVH-REG, 1 months old, hosted on OVH
PASS
agenziaseolatina.it — via OVH-REG, 1 months old, hosted on OVH
Info::
Domain registered until Jul 29, 2027 (10 months remaining)
Info::
Domain is only 1 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Jul 29, 2026
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

283 days

July 29, 2027

SSL certificate

31 days

Issued by Let's Encrypt

Domain age

1 months

Registered July 29, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

57.131.134.102

Registrar

OVH-REG

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar OVH-REG
Created July 29, 2026 (1 months ago)
Expires July 29, 2027 (10 months)
Last Updated July 29, 2026
Name Servers dns106.ovh.net, ns106.ovh.net
Registrant Web Project Group SRL
Hosting
IP Address 57.131.134.102
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
Data source: whois (1.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback