Skip to content
https://upm.es

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
3
PASS
4
INFO
1
Probed from Madrid, Spain
302 Found
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

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.upm.es/
200https://upm.es/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://upm.es/ → https://upm.es/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 26 ms lookup
PASS
1 A records, 26 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 138.100.200.6
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: einstein.ccupm.upm.es, galileo.ccupm.upm.es, sun.rediris.es, chico.rediris.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: 26 ms
Got: 26 ms
A138.100.200.6
AAAA—
CNAME—
NSeinstein.ccupm.upm.es, galileo.ccupm.upm.es, sun.rediris.es, chico.rediris.es
MX
10 mxa-006a4e02.gslb.pphosted.com
10 mxb-006a4e02.gslb.pphosted.com
TXT
google-site-verification=TVzg3pTNXeFDbscAznKHl-ZxwwMXAJKplXOTzEE4hF4
SPF v=spf1 ip4:138.100.198.70/31 include:spf.puc.rediris.es include:spf.protection.o...
google-gws-recovery-domain-verification=69261781
adobe-idp-site-verification=a21b9e2e-91fc-44d1-b66b-f7c3588d6b69
google-site-verification=lf-f_0LsZWcQAf54uV7YZQok3yHm1jqCqDLrpEbJu9k
ZOOM_verify_JyS9mzjlR9qlhzy8CchciQ
yahoo-verification-key=QHUrbU4w12OU9+HDD6yi9oPzmgxLzHr28S35KOba//E=
MS=ms92863215
CAALookup not available with standard resolver
Resolved in 26 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), 70 ms total
PASS
1 redirect(s), 70 ms total
Info::
Single redirect
Got: https://upm.es → https://www.upm.es/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://upm.es

https://upm.es

16 ms · HTTP/1.1

302

https://www.upm.es/

54 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://upm.es30216 msHTTP/1.1Apache
2https://www.upm.es/20054 msHTTP/1.1Apache

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+
Crawlability
robots.txt present, sitemap with 1100 URLs
PASS
robots.txt present, sitemap with 1100 URLs
Info::
robots.txt is present
Got: 24 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1100 entries
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 24 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
sitemap.xml 200 OK
Type URL Set URLs 1100 entries Valid XML Yes
Sample URLs:
A+
HTTP Probe Timing
Total 45 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
46 ms
Total Time Total request time from DNS lookup through full response.
46 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 2 ms TLS Handshake 6 ms Server Processing 5 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