Skip to content
https://eldiario.es

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
4
INFO
1
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 3 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.

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::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.eldiario.es/
200https://eldiario.es/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://eldiario.es/ → https://www.eldiario.es/

Consistent

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

Certificate validity

66
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
A+
DNS Records
1 A records, 23 ms lookup
PASS
1 A records, 23 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 176.34.179.218
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: ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com
Info::
5 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: 23 ms
Got: 23 ms
A176.34.179.218
AAAA—
CNAME—
NSns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
MS=ms77120734
google-site-verification=74ZalOYJ42fLZ70DV7fC8U_PugxuQk-Dd0s1u9rX3A4
MS=32110645D93EF4C741A67C29A0A80ADEC40520D0
google-site-verification=vUuSUgrTKfWs59LtgWRK8iEYojxMy6vwc0qJlLtPDfs
SPF v=spf1 include:_spf.google.com include:servers.mcsv.net include:mail.zendesk.com...
CAALookup not available with standard resolver
Resolved in 23 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), 236 ms total
PASS
1 redirect(s), 236 ms total
Info::
Single redirect
Got: https://eldiario.es → https://www.eldiario.es/ (301)
Info::
WWW normalization redirect

https://eldiario.es

81 ms · HTTP/1.1

301

https://www.eldiario.es/

155 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://eldiario.es30181 msHTTP/1.1Caddy
2https://www.eldiario.es/200155 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 76 URLs
PASS
robots.txt present, sitemap with 76 URLs
Info::
robots.txt is present
Got: 880 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 76 entries
Info::
Sitemap index with 76 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 880 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /api/
Disallow: /api/comment/user/featureds
Disallow: /api/comment/user/subscribers
Disallow: /api/comment/user/muted
Disallow: /api/comment/user/voted
Disallow: /bbtcaptcha/
Disallow: /bbtcomment/create/
Disallow: /bbtcomment/vote/
Disallow: /bbtcomment/report/
Disallow: /bbtcomment/entityComments/
Disallow: /bbtcontent/poll/vote/
Disallow: /bbtcontent/poll/getresults/
Disallow: /props/
Disallow: /bbtmail/sendEntity/
Disallow: /bbtshop/
Disallow: /bbtstats/
Disallow: /logout.html
Disallow: /buscador/
Disallow: /vertele/lo-mas-visto-tv/2*
Disallow: /vertele/lo-mas-visto-tv/cadenas/2*
Disallow: /vertele/lo-mas-visto-tv/cadenas/mes/2*
Disallow: /vertele/lo-mas-visto-tv/informativos/2*
Disallow: /vertele/lo-mas-visto-tv/todos/2*

Sitemap: https://www.eldiario.es/sitemap_index_25b87.xml
Sitemap: https://www.eldiario.es/sitemap_google_news_25b87.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 76 entries Valid XML Yes
Child Sitemaps:
A+
HTTP Probe Timing
Total 84 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
10 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
23 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
27 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
84 ms
Total Time Total request time from DNS lookup through full response.
84 ms

Connection waterfall

DNS Lookup 10 ms TCP Connect 23 ms TLS Handshake 27 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