Infrastructure - https://www.studiolegalenoviligure.com BeaverCheck Audit

D

Multi-Resolver DNS Speed

Action

Mean 201ms across 3 resolvers (spread 413ms)

FIX

Mean 201ms across 3 resolvers (spread 413ms)

Cloudflare: 2ms

Got: 2ms via 1.1.1.1:53

Quad9: 188ms

Got: 188ms via 9.9.9.9:53

Google: 415ms

Got: 415ms via 8.8.8.8:53

High latency spread between resolvers: 413ms (min 2ms / max 415ms)

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

DNS Records

2 A records, 836 ms lookup

REVIEW

2 A records, 836 ms lookup

Resolves to 2 IPv4 address(es)

Got: 75.2.0.180, 99.83.169.22

No IPv6 (AAAA) records

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: a3c02b2530d6f27ca.awsglobalaccelerator.com

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (836 ms)

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

Got: 836 ms

A	75.2.0.180, 99.83.169.22
AAAA	—
CNAME	a3c02b2530d6f27ca.awsglobalaccelerator.com
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 836 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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

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 75.2.0.180 does not match any cert SAN: a3c02b2530d6f27ca.awsglobalaccelerator.com

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 for 99.83.169.22 does not match any cert SAN: a3c02b2530d6f27ca.awsglobalaccelerator.com

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

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

HTTP Probe Timing

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

REVIEW

DNS Lookup

600 ms

TCP Connect

2 ms

TLS Handshake

228 ms

Time to First Byte

957 ms

Total Time

958 ms

Connection waterfall

DNS Lookup 600 ms TCP Connect 2 ms TLS Handshake 228 ms Server Processing 126 ms Content Transfer 2 ms

B

TLS Certificate Expiry & Recommendations

80 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

80

days left

0d 30d 60d 90d+

Recommended actions

Add includeSubDomains to the HSTS directive
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 AWS CloudFront (host iol-website.italiaonline.it, 10 assets); document served directly from origin

REVIEW

Assets on AWS CloudFront (host iol-website.italiaonline.it, 10 assets); document served directly from origin

Document not behind existing CDN (AWS CloudFront serves the assets)

The page's subresources are delivered by AWS CloudFront (iol-website.italiaonline.it, 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: delegation dw3zmm73bdwsn.cloudfront.net

Assets on AWS CloudFront: iol-website.italiaonline.it (assets: 10), cache Hit from cloudfront

Got: delegation dw3zmm73bdwsn.cloudfront.net

Assets on AWS CloudFront: irp.cdn-website.com (assets: 10), cache Hit from cloudfront

Got: x-amz-cf-id: x8-JVlqkIhL7GN3wu5hDsCplu8n17VhAT6Qd3qlK-TBRyqIoUiaCNQ==

Assets on AWS CloudFront: static.cdn-website.com (assets: 3), cache Hit from cloudfront

Got: x-amz-cf-id: 28lyWts1otZ_Jb4rIjzWkIAorB7oGcHZYKHXzUwDUV63wwy-FH-m4w==

Assets on a CDN, document is not: AWS CloudFront

Document origin not attributed

Asset hosts on a CDN

iol-website.italiaonline.it — AWS CloudFront · assets: 10 · Cache Status: Hit from cloudfront
irp.cdn-website.com — AWS CloudFront · assets: 10 · Cache Status: Hit from cloudfront
static.cdn-website.com — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront

Other asset hosts

consent.cookiebot.com — assets: 2 · below probe threshold
bcontact.paginegialle.it — assets: 1 · below probe threshold
consentcdn.cookiebot.com — assets: 1 · below probe threshold
www.googletagmanager.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

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.studiolegalenoviligure.com

https://www.studiolegalenoviligure.com

1034 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.studiolegalenoviligure.com	200	1034 ms	HTTP/1.1	nginx

A+

Crawlability

robots.txt present, sitemap with 4 URLs

PASS

robots.txt present, sitemap with 4 URLs

robots.txt is present

Got: 174 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 4 entries

robots.txt references sitemap

robots.txt 200 OK

Size 174 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

# Sitemap is also available on /sitemap.xml
Sitemap: https://www.studiolegalenoviligure.com/sitemap.xml
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=yes

sitemap.xml 200 OK

Type URL Set URLs 4 entries Valid XML Yes

Sample URLs:

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: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.studiolegalenoviligure.com/

301https://studiolegalenoviligure.com/

Preferred variant: www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

studiolegalenoviligure.com — via Register SPA, 9 days old, hosted on AWS

PASS

studiolegalenoviligure.com — via Register SPA, 9 days old, hosted on AWS

Domain registered until Oct 5, 2027 (11 months remaining)

Domain is only 9 days 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 Oct 5, 2026

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.

Registrar: Register SPA

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: AWS

Got: AS14618

Domain expiry

351 days

October 5, 2027

SSL certificate

80 days

Issued by Let's Encrypt

Domain age

9 days

Registered October 5, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

100.24.208.97

Registrar

Register SPA

Unlocked 2 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
Newly registered domain — build backlinks and content to establish SEO trust
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Register SPA

Created October 5, 2026 (9 days ago)

Expires October 5, 2027 (11 months)

Last Updated October 5, 2026

Name Servers ns1.register.it, ns2.register.it

DNSSEC Not enabled

Hosting

IP Address 100.24.208.97

ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (1.6s)

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.

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