Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

200 OK

Checks

6 PASS 10 REVIEW 1 FIX

HTTP Probe Timing

Action

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

FIX

DNS Lookup

1 ms

TCP Connect

20 ms

TLS Handshake

23 ms

Time to First Byte

4.93 s

Total Time

4.95 s

Connection waterfall

DNS Lookup 1 ms TCP Connect 20 ms TLS Handshake 23 ms Server Processing 4.89 s Content Transfer 20 ms

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).

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.

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 51.75.127.110 does not match any cert SAN: 110.ip-51-75-127.eu

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.

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

Crawlability

robots.txt present, sitemap with 0 URLs

REVIEW

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 600 bytes

sitemap.xml is present

sitemap.xml contains invalid XML

Search engines may not be able to parse the sitemap. Fix XML validation errors.

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK

Size 600 B Sitemaps referenced 5 User-agents Blocking No — crawling allowed

# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
#
# To ban all spiders from the entire site uncomment the next two lines:
#User-Agent: *
#Disallow: /

Sitemap: http://www.reteassociazioni.it/sitemaps/sitemap_articles_index.xml.gz
Sitemap: http://www.reteassociazioni.it/sitemaps/sitemap_events_index.xml.gz
Sitemap: http://www.reteassociazioni.it/sitemaps/sitemap_galleries_index.xml.gz
Sitemap: http://www.reteassociazioni.it/sitemaps/sitemap_pages_index.xml.gz
Sitemap: http://www.reteassociazioni.it/sitemaps/sitemap_organizations_index.xml.gz

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML No

URL Variants

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.reteassociazioni.it/

200https://reteassociazioni.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

TLS Certificate Expiry & Recommendations

82 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

CDN & Delivery

Action

Assets on Bunny CDN (host cdn.iubenda.com, 11 assets); document served directly from origin (OVH)

REVIEW

Assets on Bunny CDN (host cdn.iubenda.com, 11 assets); document served directly from origin (OVH)

Document not behind existing CDN (Bunny CDN serves the assets)

The page's subresources are delivered by Bunny CDN (cdn.iubenda.com, 11 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

Assets on Bunny CDN: cdn.iubenda.com (assets: 11)

Got: delegation cdn-iubenda.b-cdn.net

Assets on a CDN, document is not: Bunny CDN

Document origin OVH

Asset hosts on a CDN

cdn.iubenda.com — Bunny CDN · assets: 11

Other asset hosts

s3.amazonaws.com — assets: 25 · AWS
connect.facebook.net — assets: 2 · below probe threshold
pagead2.googlesyndication.com — assets: 2 · below probe threshold
cs.iubenda.com — assets: 1 · below probe threshold
www.google.com — assets: 1 · below probe threshold
www.googletagmanager.com — assets: 1 · below probe threshold
www.gstatic.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.

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.

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.

DNS Records

1 A records, 47 ms lookup

PASS

1 A records, 47 ms lookup

Resolves to 1 IPv4 address(es)

Got: 51.75.127.110

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

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: reteassociazioni.it

2 nameserver(s) configured

Got: ns81.domaincontrol.com, ns82.domaincontrol.com

2 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 47 ms

Got: 47 ms

A	51.75.127.110
AAAA	—
CNAME	reteassociazioni.it
NS	ns81.domaincontrol.com, ns82.domaincontrol.com
MX	0 mx1.mailchannels.net 0 mx2.mailchannels.net
TXT	SPF v=spf1 mx include:netblocks.dreamhost.com include:relay.mailchannels.net -all
CAA	Lookup not available with standard resolver

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

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

Multi-Resolver DNS Speed

Mean 49ms across 3 resolvers (spread 68ms)

PASS

Mean 49ms across 3 resolvers (spread 68ms)

Google: 26ms

Got: 26ms via 8.8.8.8:53

Cloudflare: 27ms

Got: 27ms via 1.1.1.1:53

Quad9: 94ms

Got: 94ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.reteassociazioni.it

https://www.reteassociazioni.it

689 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.reteassociazioni.it	200	689 ms	HTTP/1.1	nginx/1.14.0 + Phusion Passenger 5.3.7

Domain Intelligence

reteassociazioni.it — via 1API-REG, 16 years, 1 months old, hosted on OVH

PASS

reteassociazioni.it — via 1API-REG, 16 years, 1 months old, hosted on OVH

Domain expires in 31 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Oct 11, 2026

Registrar: 1API-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: OVH

Got: AS16276

Domain expiry

29 days

October 11, 2026

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

16 years, 1 months

Registered October 11, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

51.75.127.110

Registrar

1API-REG

Unlocked 2 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 1API-REG

Created October 11, 2010 (16 years, 1 months ago)

Expires October 11, 2026 (1 months)

Last Updated October 27, 2025

Name Servers ns81.domaincontrol.com, ns82.domaincontrol.com

Registrant DevInterface di Stefano Mancini

Hosting

IP Address 51.75.127.110

ASN AS16276 (OVH - OVH SAS, FR)

Provider OVH

Data source: whois (0.7s)

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

A+

Health Check Endpoint

Health endpoint at https://www.reteassociazioni.it/health (HTTP 200)

PASS

Health endpoint at https://www.reteassociazioni.it/health (HTTP 200)

Public health endpoint at https://www.reteassociazioni.it/health

Got: https://www.reteassociazioni.it/health

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