Skip to content
https://andiamonline.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
6 PASS 10 REVIEW 1 FIX
F
HTTP Probe Timing
Action
Total 12827 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
1 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
33 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
12.79 s
Total Time Total request time from DNS lookup through full response.
12.83 s

Connection waterfall

DNS Lookup 1 ms TCP Connect 33 ms TLS Handshake 36 ms Server Processing 12.72 s Content Transfer 35 ms
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 46.252.151.217 does not match any cert SAN: hostingssd73-217.netsons.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.
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::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

https://www.andiamonline.it/
200https://andiamonline.it/

HTTP → HTTPS

http://andiamonline.it/

HTTP version does not redirect to HTTPS

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
C
CDN & Delivery
Action
Assets on AWS CloudFront (host cdn.trustindex.io, 55 assets); document served directly from origin
REVIEW
Assets on AWS CloudFront (host cdn.trustindex.io, 55 assets); document served directly from origin
Warning::
Document not behind existing CDN (AWS CloudFront serves the assets)
The page's subresources are delivered by AWS CloudFront (cdn.trustindex.io, 55 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 dhtt2nmvztmk3.cloudfront.net
Info::
Assets on AWS CloudFront: cdn.trustindex.io (assets: 55), cache Hit from cloudfront
Got: delegation dhtt2nmvztmk3.cloudfront.net
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin not attributed

Asset hosts on a CDN

  • cdn.trustindex.io — AWS CloudFront · assets: 55 · Cache Status: Hit from cloudfront

Other asset hosts

  • lh3.googleusercontent.com — assets: 8 · Google
  • fonts.googleapis.com — assets: 4 · Google
  • cdn.iubenda.com — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 2 · below probe threshold
  • embeds.iubenda.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
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
1 A records, 2 ms lookup
PASS
1 A records, 2 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 46.252.151.217
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns4.netsons.net, dns1.netsons.net, dns2.netsons.net, dns3.netsons.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 2 ms
Got: 2 ms
A46.252.151.217
AAAA—
CNAME—
NSdns4.netsons.net, dns1.netsons.net, dns2.netsons.net, dns3.netsons.net
MX
0 mail.andiamonline.it
TXT
google-site-verification=ZVjhzSkU4XGHPynUU-BGLp4gKA2MBCA20CQWc_VuUb0
SPF v=spf1 +a +mx ~all
brevo-code:3524152d58884aeed428023bc6c01380
CAALookup not available with standard resolver
Resolved in 2 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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 28ms across 3 resolvers (spread 44ms)
PASS
Mean 28ms across 3 resolvers (spread 44ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 40ms
Got: 40ms via 8.8.8.8:53
Info::
Cloudflare: 45ms
Got: 45ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://andiamonline.it

https://andiamonline.it

1789 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://andiamonline.it2001789 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 92 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 92 B Sitemaps referenced 0 User-agents MSNBot, bingbot Blocking No — crawling allowed
#Simple Robots.txt 0.1
User-agent: MSNBot
Crawl-delay: 5
User-agent: bingbot
Crawl-delay: 5
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
andiamonline.it — via NETSONS-REG, 10 months old, hosted on ASSUPERNOVA - Netsons s.r.l., IT
PASS
andiamonline.it — via NETSONS-REG, 10 months old, hosted on ASSUPERNOVA - Netsons s.r.l., IT
Warning::
Domain expires in 59 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jan 2, 2027
Info::
Registrar: NETSONS-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: ASSUPERNOVA - Netsons s.r.l., IT
Got: AS60087
Domain expiry

54 days

January 2, 2027

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

10 months

Registered January 2, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ASSUPERNOVA - Netsons s.r.l., IT

ASN AS60087

46.252.151.217

Registrar

NETSONS-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 NETSONS-REG
Created January 2, 2026 (10 months ago)
Expires January 2, 2027 (1 months)
Last Updated January 2, 2026
Name Servers dns1.netsons.net, dns2.netsons.net, dns3.netsons.net, dns4.netsons.net
Registrant hidden
Hosting
IP Address 46.252.151.217
ASN AS60087 (ASSUPERNOVA - Netsons s.r.l., IT)
Provider ASSUPERNOVA - Netsons s.r.l., IT
Data source: whois (0.4s)

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

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

Send Feedback