Skip to content
https://finecobank.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
9 PASS 7 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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)
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
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
135 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

135
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 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, 31 ms lookup
PASS
1 A records, 31 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.193.183.191
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: a22-67.akam.net, dns1.fineco.it, a16-67.akam.net, a1-118.akam.net, a24-65.akam.net, a11-64.akam.net
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 31 ms
Got: 31 ms
A193.193.183.191
AAAA—
CNAME—
NSa22-67.akam.net, dns1.fineco.it, a16-67.akam.net, a1-118.akam.net, a24-65.akam.net, a11-64.akam.net
MX
10 mxa-003adb01.gslb.pphosted.com
10 mxb-003adb01.gslb.pphosted.com
TXT
S3cioRXsSpDRIxwtnkybeuSS6NlNXqjSn73Fm0iVfpLyLqbZgFxY1vpMN/LolfiPGIBbkfSmZmWVw9DI...
google-site-verification=HZvbQWuPTvivcYYF2DJ8WsGVmSyxXCW0NZKjDBrlGtg
SPF v=spf1 ip4:193.193.183.0/24 ip4:84.14.129.206 ip4:204.115.118.0/24 ip4:195.135.2...
D/l5E8uyqgEzYpnTQZoLK4Bw3DiQrHCpm4tgx02hi3fuUvi50xJElJ1zkEgdJI7obu/DcKSHkZ8elFIU...
MS=ms11682783
google-site-verification=zTyoeIxDbHLMFOVqimEhJ8KaceHgsWFNPmRil7xYUK8
facebook-domain-verification=yvd3nkh1ihvope4wuflukg5wtv5hw6
CAALookup not available with standard resolver
Resolved in 31 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+
Reverse DNS
1/1 IPs match cert SAN
PASS
1/1 IPs match cert SAN
Info::
PTR for 193.193.183.191 matches certificate SAN: finecobank.com
A+
Multi-Resolver DNS Speed
Mean 37ms across 3 resolvers (spread 49ms)
PASS
Mean 37ms across 3 resolvers (spread 49ms)
Info::
Cloudflare: 19ms
Got: 19ms via 1.1.1.1:53
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
Info::
Quad9: 68ms
Got: 68ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 272 ms total
PASS
1 redirect(s), 272 ms total
Info::
Single redirect
Got: https://finecobank.com → https://it.finecobank.com/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://finecobank.com
Info::
Cross-domain redirect detected

https://finecobank.com

158 ms · HTTP/1.1

302

https://it.finecobank.com/

114 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://finecobank.com302158 msHTTP/1.1Microsoft-IIS/10.0
2https://it.finecobank.com/200114 msHTTP/1.1AkamaiGHost

See the visual redirect chain in the HTTP Probe tab →

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

A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 75 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 75 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
user-agent: *

disallow:

Sitemap: https://finecobank.com/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.finecobank.com/
200https://finecobank.com/

Preferred variant: non-www

HTTP → HTTPS

301http://finecobank.com/ → https://finecobank.com/

Consistent

A+
Domain Intelligence
finecobank.com — via Register SPA, 24 years, 9 months old, hosted on FINECO - FinecoBank S.p.A., IT
PASS
finecobank.com — via Register SPA, 24 years, 9 months old, hosted on FINECO - FinecoBank S.p.A., IT
Info::
Domain registered until Feb 7, 2027 (7 months remaining)
Info::
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.
Info::
Registrar: Register SPA
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: FINECO - FinecoBank S.p.A., IT
Got: AS12498
Domain expiry

210 days

February 7, 2027

SSL certificate

135 days

Issued by DigiCert Inc

Domain age

24 years, 9 months

Registered February 7, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

FINECO - FinecoBank S.p.A., IT

ASN AS12498

193.193.183.191

Registrar

Register SPA

Unlocked 6 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Register SPA
Created February 7, 2002 (24 years, 9 months ago)
Expires February 7, 2027 (7 months)
Last Updated February 8, 2026
Name Servers a1-118.akam.net, a11-64.akam.net, a16-67.akam.net, a22-67.akam.net, a24-65.akam.net, dns1.fineco.it
DNSSEC Not enabled
Hosting
IP Address 193.193.183.191
ASN AS12498 (FINECO - FinecoBank S.p.A., IT)
Provider FINECO - FinecoBank S.p.A., IT
Data source: rdap (0.4s)

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

A+
HTTP Probe Timing
Total 128 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
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.
40 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
45 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
128 ms
Total Time Total request time from DNS lookup through full response.
129 ms

Connection waterfall

DNS Lookup 1 ms TCP Connect 40 ms TLS Handshake 45 ms Server Processing 43 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