Skip to content
https://uam.es

Infrastructure

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

B
Redirect Chain
1 redirect(s), 1364 ms total
REVIEW
1 redirect(s), 1364 ms total
Info::
Single redirect
Got: https://uam.es → https://www.uam.es/uam/inicio (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://uam.es
Warning::
Redirect overhead: 1364 ms total
Got: 1364 ms

https://uam.es

701 ms · HTTP/1.1

302

https://www.uam.es/uam/inicio

663 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uam.es302701 msHTTP/1.1
2https://www.uam.es/uam/inicio200663 msHTTP/1.1

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

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
TLS Certificate Expiry & Recommendations
238 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

238
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, 181 ms lookup
PASS
1 A records, 181 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 150.244.214.237
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: sun.rediris.es, chico.rediris.es, dns4.uam.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: 181 ms
Got: 181 ms
A150.244.214.237
AAAA
CNAME
NSsun.rediris.es, chico.rediris.es, dns4.uam.es
MX
10 mxb-006a4e02.gslb.pphosted.com
10 mxa-006a4e02.gslb.pphosted.com
TXT
google-gws-recovery-domain-verification=68163565
SPF v=spf1 ip4:150.244.8.56 ip4:150.244.8.129 ip4:150.244.8.130 ip4:150.244.8.131 ip...
openai-domain-verification=dv-yYtetSELvV4MgkiuWopfuO83
google-site-verification=G0Ba_ou1Uy2u5r5xRiVzV4WfoVRvUMvxmgV_lHoFTso
adobe-idp-site-verification=ddfac0458805ea55ffcc67a1c8a19014ed83a2be49102a1b9800...
autodesk-domain-verification=PiAVlPz1leUu-AAETf3P
CAALookup not available with standard resolver
Resolved in 181 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+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 1013 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1013 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

#

Disallow: /BOUAM/documento/1446811653168/I.2.5._Acuerdo_5CG_de_13-11-20_por_el_que_se_aprueba_la_la_Resoluci%C3%B3n_de_la_Convocatoria_de_contratos_predoctorales_PDI_2020_(FPI-UAM)..pdf

Disallow: /estaticos/UAM-R/css/*.css

Disallow: /estaticos/UAM-R/js/*.js

Disallow: /BOUAM/I.1.14.-Acuerdo-14/Pleno-294-de-19-03-18/1446760465569.htm?language=es&pid=1234892145844

Disallow: /BOUAM/I.1.4.-Acuerdo-4/Pleno-279-de-09-05-16/1242697382167.htm?language=es&pid=1234892145844

Disallow: /EscuelaDoctorado/documento/1446843986193/tesis-depositadas-enero2024.web.pdf

Disallow: /EscuelaDoctorado/(es_ES)Tesis-pr%C3%B3xima-defensa/1446832238817.htm?language=es_ES&nodepath=Tesis%20de%20pr%C3%B3xima%20defensa

Disallow: /EscuelaDoctorado/documento/1446845592187/tesis-proxima-defensa-mayo2024.pdf

Disallow: /BOUAM/documento/1242677399547/I.1.10._Acuerdo_10_Pleno_263_de_28_04_14_por_el_que_se_aprueba_el_M_ster_propio_en_Inteligencia_Econ_mica.pdf

#

Sitemap: https://www.uam.es/sitemap.xml
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.uam.es/
200https://uam.es/

Preferred variant: non-www

HTTP → HTTPS

307http://uam.es/ https://uam.es/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 173 ms TLS Handshake 178 ms Server Processing 177 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