Skip to content
https://cervantes.es

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
61
GRADE
D
FIX
3
REVIEW
4
PASS
1
INFO
1
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
1 PASS 4 REVIEW 3 FIX
F
Redirect Chain
Action
3 redirect(s), 6477 ms total
FIX
3 redirect(s), 6477 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
3-hop chain could be reduced to 1 hop
Redirect directly from https://cervantes.es to https://cervantes.org
Warning::
Redirect overhead: 6477 ms total
Got: 6477 ms
Info::
Cross-domain redirect detected

https://cervantes.es

813 ms · HTTP/1.1

301

http://www.cervantes.es/

518 ms · HTTP/1.1

301

https://www.cervantes.es/

1063 ms · HTTP/1.1

301

https://cervantes.org

4083 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cervantes.es301813 msHTTP/1.1
2http://www.cervantes.es/301518 msHTTP/1.1
3https://www.cervantes.es/3011063 msHTTP/1.1
4https://cervantes.org2004083 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://cervantes.es to https://cervantes.org

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

D
Crawlability
Action
robots.txt present, sitemap with 0 URLs
FIX
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 758 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 758 B Sitemaps referenced 0 User-agents Slurp, Yandex, AskJeeves, Baiduspider, ia_archiver, *, Googlebot, Bingbot Blocking Yes — all crawlers blocked
User-agent: Googlebot

User-agent: Bingbot

User-agent: Slurp

User-agent: Yandex

User-agent: AskJeeves

User-agent: Baiduspider

User-agent: ia_archiver

Disallow: /Vtemp/

Disallow: /seg_nivel/

Disallow: /boletin/

Disallow: /lengua_y_ensenanza/espacio_lenguas_ibericas/

Disallow: /sobre_instituto_cervantes/espacios_profesionales/

Disallow: /lengua_y_ensenanza/comprofes/inscripcion/

Disallow: /default_pruebas.htm

Disallow: /cultura_espanola/informacion_noindex.htm

Disallow: /bibliotecas_documentacion_espanol/default-noindex.htm

Disallow: /france/cours_espagnol_paris_bordeaux/

Disallow: /france/cours_espagnol_paris_lyon/

Disallow: /lengua_y_ensenanza/csf/

Disallow: /memoria_ic_web_2011-2012/

Crawl-delay: 20

User-agent: *

Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
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
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

301https://www.cervantes.es/
200https://cervantes.es/

Preferred variant: non-www

HTTP → HTTPS

301http://cervantes.es/ → http://www.cervantes.es/

HTTP version does not redirect to HTTPS

C
HTTP Probe Timing
Action
Total 1661 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
177 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
168 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
1.15 s
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.66 s
Total Time Total request time from DNS lookup through full response.
1.66 s

Connection waterfall

DNS Lookup 177 ms TCP Connect 168 ms TLS Handshake 1.15 s Server Processing 168 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
348 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

348
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, 189 ms lookup
PASS
1 A records, 189 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.146.5.10
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: dns.cervantes.es, machuca.cervantes.es
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: 189 ms
Got: 189 ms
A193.146.5.10
AAAA—
CNAME—
NSdns.cervantes.es, machuca.cervantes.es
MX
10 vela1.cervantes.es
10 vela2.cervantes.es
20 cervantes-mxbck.sistemaip.net
TXT
B140251800000877.601bedce765d30.62501949
MS=ms43241734
_5wfz80zbc3stjpoz4cq18siitm4ipbl
JIH9RzA0Jzb7gQh+IJbNqqvXAsRfj/TpBIgrLQQZRkgu/+snXkn2f5M2rtrrYF9DM2ocPSD4GwgrdNnB...
globalsign-domain-verification=vIvWiOCKbYBLSzj5CpRZ03BPgh9xJ5FEZxmCvjztZJ
xp10m4xdcnql0fjy9tzyqwmf9n3kyn8v
globalsign-domain-verification=-slX0MgqnRiACc2ng0H-ZY89alVk8Gw64Li4jPRUKM
atlassian-sending-domain-verification=668e60df-a990-4b79-a003-346425451e17
globalsign-domain-verification=uCCCTVMVLudm5wk8jiqoGVD7dvrzXqR2kNMJiUP8Vf
globalsign-domain-verification=Q2Qdb5M2M6rGo1-uOr4HPm4VVDL-s965kh-3FmVyvX
x6djzr1lgwzg9mmw1mzl5h262cx05vm6
globalsign-domain-verification=3B5kQrNjIbVGdoKorCiRN3k2nB4JRamI3MwtkrxKC3
B140251800000878.601bebf3e9b544.55675931
atlassian-domain-verification=HZVEGTjcr4P/2Qc1lIKTViUvhxjgaCqxG8iFpbQjwYLEKwdNV3...
202006180844274o3uw44j5o4i4vgvlqpebfvb1iecq2li0at7ldplb5wjiamjwz
SPF v=spf1 include:spf.protection.outlook.com ip4:193.146.3.230 ip4:193.146.3.229 ip...
globalsign-domain-verification=7l3pqAmzmoQ-e-TA25j_xo2Ax3N3Zzt6Gz79T1zeHM
CAALookup not available with standard resolver
Resolved in 189 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.

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