Skip to content
https://fineco.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
9
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 9 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.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 20.4.145.130: lookup 20.4.145.130: 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.
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
TLS Certificate Expiry & Recommendations
173 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

173
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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 & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
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, 55 ms lookup
PASS
1 A records, 55 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 20.4.145.130
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a24-65.akam.net, a1-118.akam.net, a22-67.akam.net, a16-67.akam.net, a11-64.akam.net, dns1.fineco.it
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 55 ms
Got: 55 ms
A20.4.145.130
AAAA—
CNAME—
NSa24-65.akam.net, a1-118.akam.net, a22-67.akam.net, a16-67.akam.net, a11-64.akam.net, dns1.fineco.it
MX
10 mxb-003adb01.gslb.pphosted.com
10 mxa-003adb01.gslb.pphosted.com
TXT
trustpilot050919
hmATVg7sw2hqCy3pHm0pxmALCmI0UjwaaPg1Rjs4eGk0eSxcyD+Dud0Bi6mFYDc7fc8rRWBacFkAwvHR...
SPF v=spf1 ip4:193.193.183.0/24 ip4:20.19.165.89 ip4:204.115.118.0/24 ip4:195.135.20...
apple-domain-verification=Jla4Aud4gmdl9SjY
autodesk-domain-verification=GUXJ0pE2wDU4mmcHjPZ-
google-site-verification=9JXMCbHKPtbY2ZAfMYbiwLOoV3Df6-wJ_5mDrAmTNMY
facebook-domain-verification=pb7esdax456penzjgc2okyyx054z9k
mPXrQ+ZNo6wTN07Cixe2YHhdnkCYTMPRFxHf+wnjd5h/wu3O5wiia5VFphM3dqn1ldHpvxauqt4MICuk...
CAALookup not available with standard resolver
Resolved in 55 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 40ms across 3 resolvers (spread 59ms)
PASS
Mean 40ms across 3 resolvers (spread 59ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
Info::
Quad9: 76ms
Got: 76ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 283 ms total
PASS
1 redirect(s), 283 ms total
Info::
Single redirect
Got: https://fineco.it → https://it.finecobank.com/ (301)
Info::
Cross-domain redirect detected

https://fineco.it

93 ms · HTTP/1.1

301

https://it.finecobank.com/

190 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fineco.it30193 msHTTP/1.1AkamaiGHost
2https://it.finecobank.com/200190 msHTTP/1.1AkamaiGHost

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 510 URLs
PASS
robots.txt present, sitemap with 510 URLs
Info::
robots.txt is present
Got: 71 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 510 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 71 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
user-agent: *
disallow:
Sitemap: https://it.finecobank.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 510 entries Valid XML Yes
Sample URLs:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.fineco.it/
200https://fineco.it/

Preferred variant: non-www

HTTP → HTTPS

302http://fineco.it/ → https://fineco.it/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
fineco.it — via BARBERO-REG, 30 years, 9 months old, hosted on Microsoft Azure
PASS
fineco.it — via BARBERO-REG, 30 years, 9 months old, hosted on Microsoft Azure
Info::
Domain registered until Oct 18, 2026 (3 months remaining)
Info::
Registrar: BARBERO-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: Microsoft Azure
Got: AS8075
Domain expiry

98 days

October 18, 2026

SSL certificate

173 days

Issued by DigiCert Inc

Domain age

30 years, 9 months

Registered February 21, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.4.145.130

Registrar

BARBERO-REG

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar BARBERO-REG
Created February 21, 1996 (30 years, 9 months ago)
Expires October 18, 2026 (3 months)
Last Updated November 3, 2025
Name Servers dns1.fineco.it, a16-67.akam.net, a11-64.akam.net, a22-67.akam.net, a24-65.akam.net, a1-118.akam.net
Registrant Finecobank S.p.A.
Hosting
IP Address 20.4.145.130
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: whois (0.8s)

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+
HTTP Probe Timing
Total 153 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
31 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
31 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
153 ms
Total Time Total request time from DNS lookup through full response.
154 ms

Connection waterfall

DNS Lookup 60 ms TCP Connect 31 ms TLS Handshake 31 ms Server Processing 31 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback