Skip to content
https://tenlolisto.com

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
307 Temporary Redirect
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).
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 64.29.17.1: lookup 64.29.17.1: 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.
Info::
PTR lookup failed for 216.198.79.65: lookup 216.198.79.65: 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

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.tenlolisto.com/
200https://tenlolisto.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://tenlolisto.com/ → https://tenlolisto.com/

Use 301 (permanent) instead of 302 (temporary)

B
TLS Certificate Expiry & Recommendations
62 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: cdg1::46pm5-1781018538873-1909a5c343b0
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: cdg1::46pm5-1781018538873-1909a5c343b0
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
2 A records, 34 ms lookup
PASS
2 A records, 34 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 64.29.17.1, 216.198.79.65
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.vercel-dns.com, ns1.vercel-dns.com
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 34 ms
Got: 34 ms
A64.29.17.1, 216.198.79.65
AAAA—
CNAME—
NSns2.vercel-dns.com, ns1.vercel-dns.com
MX—
TXT
google-site-verification=_o6E74toGzy1N0Aij_iFnxSp79r3XQY_sdnKfMHL3iI
CAALookup not available with standard resolver
Resolved in 34 ms

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)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: letsencrypt.org, pki.goog, sectigo.com
PASS
issue: letsencrypt.org, pki.goog, sectigo.com
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org, pki.goog, sectigo.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 40ms across 3 resolvers (spread 44ms)
PASS
Mean 40ms across 3 resolvers (spread 44ms)
Info::
Cloudflare: 21ms
Got: 21ms via 1.1.1.1:53
Info::
Google: 34ms
Got: 34ms via 8.8.8.8:53
Info::
Quad9: 65ms
Got: 65ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 141 ms total
PASS
1 redirect(s), 141 ms total
Info::
Single redirect
Got: https://tenlolisto.com → https://www.tenlolisto.com/ (307)
Info::
WWW normalization redirect

https://tenlolisto.com

67 ms · HTTP/1.1

307

https://www.tenlolisto.com/

74 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tenlolisto.com30767 msHTTP/1.1Vercel
2https://www.tenlolisto.com/20074 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1080 URLs
PASS
robots.txt present, sitemap with 1080 URLs
Info::
robots.txt is present
Got: 207 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1080 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 207 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /admin/
Disallow: /profile/
Disallow: /carrito/
Disallow: /wallet/
Disallow: /subscription/

Host: https://www.tenlolisto.com
Sitemap: https://www.tenlolisto.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 1080 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
tenlolisto.com — via HOSTINGER operations, UAB, 1 years, 2 months old, hosted on AWS
PASS
tenlolisto.com — via HOSTINGER operations, UAB, 1 years, 2 months old, hosted on AWS
Info::
Domain registered until Apr 13, 2027 (10 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: HOSTINGER operations, UAB
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: AWS
Got: AS16509
Domain expiry

304 days

April 13, 2027

SSL certificate

62 days

Issued by Let's Encrypt

Domain age

1 years, 2 months

Registered April 13, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

64.29.17.1

Registrar

HOSTINGER operations, UAB

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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar HOSTINGER operations, UAB
Created April 13, 2025 (1 years, 2 months ago)
Expires April 13, 2027 (10 months)
Last Updated March 12, 2026
Name Servers ns1.vercel-dns.com, ns2.vercel-dns.com
DNSSEC Not enabled
Hosting
IP Address 64.29.17.1
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

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