Infrastructure - https://splsezzespa.it BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 2437 ms total

FIX

2 redirect(s), 2437 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.splsezzespa.it/

Redirect overhead: 2437 ms total

Got: 2437 ms

https://splsezzespa.it

846 ms · HTTP/1.1

301

https://www.splsezzespa.it/

653 ms · HTTP/1.1

302

https://www.splsezzespa.it/it-IT/

937 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://splsezzespa.it	301	846 ms	HTTP/1.1	aruba-proxy
2	https://www.splsezzespa.it/	302	653 ms	HTTP/1.1	aruba-proxy
3	https://www.splsezzespa.it/it-IT/	200	937 ms	HTTP/1.1	aruba-proxy

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

F

IPv6 Readiness

Action

IPv6 records exist but unreachable

FIX

IPv6 records exist but unreachable

IPv6 DNS records exist but server is not reachable

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Got: 2a00:6d40:4:1::c326:27

IPv6 connection error

Got: dial tcp6 [2a00:6d40:4:1::c326:27]:443: connect: network is unreachable

IPv6 Misconfigured

AAAA Records 2a00:6d40:4:1::c326:27 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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)

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

PTR for 31.11.36.27 does not match any cert SAN: webx1501.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.

PTR lookup failed for 2a00:6d40:4:1::c326:27: lookup 2a00:6d40:4:1::c326:27: 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

Multi-Resolver DNS Speed

Mean 167ms across 3 resolvers (spread 21ms)

REVIEW

Mean 167ms across 3 resolvers (spread 21ms)

Cloudflare: 155ms

Got: 155ms via 1.1.1.1:53

Google: 172ms

Got: 172ms via 8.8.8.8:53

Quad9: 176ms

Got: 176ms via 9.9.9.9:53

B

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B

HTTP Probe Timing

Total 832 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

332 ms

TCP Connect

164 ms

TLS Handshake

171 ms

Time to First Byte

833 ms

Total Time

833 ms

Connection waterfall

DNS Lookup 332 ms TCP Connect 164 ms TLS Handshake 171 ms Server Processing 165 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

239 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

239

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

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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

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

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, 478 ms lookup

PASS

1 A records, 478 ms lookup

Resolves to 1 IPv4 address(es)

Got: 31.11.36.27

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2a00:6d40:4:1::c326:27

4 nameserver(s) configured

Got: dns3.arubadns.net, dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (478 ms)

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

Got: 478 ms

A	31.11.36.27
AAAA	2a00:6d40:4:1::c326:27
CNAME	—
NS	dns3.arubadns.net, dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz
MX	10 mx.splsezzespa.it
TXT	facebook-domain-verification=wvxfjczrdhzmtkva3gk4vbj6i6nsya SPF v=spf1 include:_spf.aruba.it ~all
CAA	Lookup not available with standard resolver

Resolved in 478 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

No CNAME record present

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.splsezzespa.it/

200https://splsezzespa.it/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A

Domain Intelligence

splsezzespa.it — via ARUBA-REG, 18 years old, hosted on ARUBA-ASN - Aruba S.p.A., IT

PASS

splsezzespa.it — via ARUBA-REG, 18 years old, hosted on ARUBA-ASN - Aruba S.p.A., IT

Domain expires in 74 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Sep 23, 2026

Registrar: ARUBA-REG

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.

Hosting: ARUBA-ASN - Aruba S.p.A., IT

Got: AS31034

Domain expiry

73 days

September 23, 2026

SSL certificate

239 days

Issued by Actalis S.p.A.

Domain age

18 years

Registered September 23, 2008

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ARUBA-ASN - Aruba S.p.A., IT

ASN AS31034

31.11.36.27

Registrar

ARUBA-REG

Unlocked 4 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 registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar ARUBA-REG

Created September 23, 2008 (18 years ago)

Expires September 23, 2026 (2 months)

Last Updated October 9, 2025

Name Servers dns.technorail.com, dns2.technorail.com, dns3.arubadns.net, dns4.arubadns.cz

Registrant spl Spa

Hosting

IP Address 31.11.36.27

ASN AS31034 (ARUBA-ASN - Aruba S.p.A., IT)

Provider ARUBA-ASN - Aruba S.p.A., IT

Data source: whois (0.9s)

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

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