Skip to content
https://um.es

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
2
PASS
5
INFO
1
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 2 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
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.um.es/
200https://um.es/

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://um.es/ → https://um.es/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

217
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
A+
DNS Records
1 A records, 82 ms lookup
PASS
1 A records, 82 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 155.54.212.103
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:720:1710:212::1:d
Info::
2 nameserver(s) configured
Got: dns2.um.es, dns1.um.es
Info::
2 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: 82 ms
Got: 82 ms
A155.54.212.103
AAAA2001:720:1710:212::1:d
CNAME—
NSdns2.um.es, dns1.um.es
MX
10 mx04.puc.rediris.es
10 mx03.puc.rediris.es
TXT
1636711086872
SPF v=spf1 include:spf.puc.rediris.es include:spf.protection.outlook.com ip4:155.54....
google-gws-recovery-domain-verification=42333511
google-site-verification=1qcW0cUDcu_BgQmMWle_JPs30cNCmzepUYhICTR0IMM
HARICA-1yT4Ui7PchIVljfyW4C
MS=ms14083789
CAALookup not available with standard resolver
Resolved in 82 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), 407 ms total
PASS
1 redirect(s), 407 ms total
Info::
Single redirect
Got: https://um.es → https://www.um.es/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://um.es

https://um.es

70 ms · HTTP/1.1

302

https://www.um.es/

337 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://um.es30270 msHTTP/1.1nginx
2https://www.um.es/200337 msHTTP/1.1nginx

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+
IPv6 Readiness
IPv6 reachable (22 ms)
PASS
IPv6 reachable (22 ms)
Info::
IPv6 is configured and reachable at 2001:720:1710:212::1:d
Got: 22 ms connect
IPv6 Ready
AAAA Records 2001:720:1710:212::1:d Connection Reachable (22 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 739 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 739 B Sitemaps referenced 0 User-agents 008, * Blocking No — crawling allowed
# robots.txt for www.um.es
# Updated: 2024-12-04

# Bloqueo de User-agent específico '008'
User-agent: 008
Disallow: /

# Directivas generales para todos los bots
User-agent: *
Crawl-delay: 1

# Bloqueo de directorios específicos
Disallow: /ayudaumu/
Disallow: /cgi-bin/
Disallow: /si/
Disallow: /atica/index.php
Disallow: /atica/directorio/
Disallow: /publicaciones/estadisticas/

# Bloqueo de todo lo que cuelgue de /web/universidaddemurcia/ y sus descendientes
Disallow: /web/universidaddemurcia
Disallow: /web/universidaddemurcia/
Disallow: /*/web/universidaddemurcia
Disallow: /*/web/universidaddemurcia/

# Bloqueo de patrones en cualquier subdirectorio que contenga /web/modelo-*
Disallow: /web/modelo-*
Disallow: /*/web/modelo-*
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
HTTP Probe Timing
Total 129 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
18 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
29 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
130 ms
Total Time Total request time from DNS lookup through full response.
130 ms

Connection waterfall

DNS Lookup 60 ms TCP Connect 18 ms TLS Handshake 29 ms Server Processing 23 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