Skip to content
https://eleconomista.es

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
4
PASS
4
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

80
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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 102 ms lookup
PASS
1 A records, 102 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.117.19.159
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.acens.net, ns2.acens.net
Info::
3 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 102 ms
Got: 102 ms
A34.117.19.159
AAAA—
CNAME—
NSns1.acens.net, ns2.acens.net
MX
10 eleconomista-es.mail.protection.outlook.com
20 mx.eleconomista.es
40 mx2.acens.net
TXT
zoho-verification=zb74994365.zmverify.zoho.eu
google-site-verification=9aN6wbLp7X5cbXqAtnowm0sdwcYbKvwThGWuF6SdVII
bx4dxbfx1jh44vc44nk7ntrh0g176yfl
ahrefs-site-verification_7b3c6d56a851f9d48bd6857993ab99e6975448933abd62e63e93875...
g70mmcbfm767z2vcdjgynd6j3f8grmnf
_c9gsg79xs7agkf8moyqfcmd3gg677cy
google-site-verification=PQqGubykeqi7H5Nn0fh1sWoyytXbzEwpsU00sjSaBLs
5z90n4tkyqxtrbypm38zgf64hvm6wft9
2xt1g0ygzd84p3zf2xv0r7y679x0nwbk
o7itl9tsbb6jhqttmnqhffc9rn
SPF v=spf1 mx ip4:217.116.23.4 ip4:217.116.23.6 ip4:217.116.23.13 ip4:217.116.23.14 ...
pinterest-site-verification=a411ab42a99ccd329758a7ae058b4055
google-site-verification=BS6W3sMLjNplWMirA_nMpOefMTbGzU4njwPuwssR5nE
google-site-verification=aLqOFEOjC1jSLvkoesxlmITv52Z0qLfmffVtIqOEb4g
Nkgso7AaK5PgMT47CF5WAGQ7Mio4txAAcS9/79q55um067p129tqWHE41SImkFIRgbQgouWHkyRjQluP...
google-site-verification=ObsLZLyABrZBKD0Hxo7FKCawH264wT3glCs53YA2O_A
google-site-verification=Hr9bveAI7WX-k7egZ1KwRkfcvaNjBgYz9ehE23vX36k
CAALookup not available with standard resolver
Resolved in 102 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 133 ms total
PASS
1 redirect(s), 133 ms total
Info::
Single redirect
Got: https://eleconomista.es → https://www.eleconomista.es/ (301)
Info::
WWW normalization redirect

https://eleconomista.es

71 ms · HTTP/1.1

301

https://www.eleconomista.es/

62 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://eleconomista.es30171 msHTTP/1.1Apache
2https://www.eleconomista.es/40362 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.eleconomista.es/
200https://eleconomista.es/

HTTP → HTTPS

301http://eleconomista.es/ → https://eleconomista.es:443/

Consistent

A+
HTTP Probe Timing
Total 106 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
44 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
21 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
106 ms
Total Time Total request time from DNS lookup through full response.
107 ms

Connection waterfall

DNS Lookup 44 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 24 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback