Skip to content
https://upf.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from New York, United Stated
302 Found
Checks
9
5 PASS 4 REVIEW
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.upf.edu/
200https://upf.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://upf.edu/ → https://upf.edu:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A
DNS Records
1 A records, 403 ms lookup
PASS
1 A records, 403 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.36.90.148
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: ns1.upf.edu, ns2.upf.edu, ns3.upf.edu, ns6.upf.edu
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
Warning::
DNS resolution is slow (403 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 403 ms
A34.36.90.148
AAAA—
CNAME—
NSns1.upf.edu, ns2.upf.edu, ns3.upf.edu, ns6.upf.edu
MX
1 ASPMX.L.GOOGLE.COM
5 ALT1.ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
10 ALT4.ASPMX.L.GOOGLE.COM
10 ALT3.ASPMX.L.GOOGLE.COM
TXT
MS=ms16812314
HARICA-wRfGzQbVnxjED7qnoVI
nsf8f5p4py69q75j1p3kqxgpz0tjjqm6
ZOOM_verify_mJj8U21xGOXN3TtDXXeIyV
ca3-18091fbb111f4dc1b7efc926ad2ef9e7
apple-domain-verification=PFveFCetoRJyrpN4
MS=2B15116C3E2D6BCD712FE8F458ACB04333FD9B85
amazonses:SYeYZN1CinJGw33Osdhdjpfil5uFObr3oemjmWpKhk4=
facebook-domain-verification=g1lc5kyqo2hane7oiuxpvsmk3md5kb
google-site-verification=kgsCog5ACwbdbHmEZzsbw8ELk06sxYmcgr_XPCInTn4
google-site-verification=nlwqso-js1jx923vJMJUEYSK4Ht36lf65OEGZl1tgVE
adobe-idp-site-verification=d1f5f1a769e33160ebfdb915440efb7177a613cc5beee99c71fb...
atlassian-domain-verification=iWteD9JmqB0Xxuvyj/ZMat3EaYFeQ/9oen3F5pbSWIvcUYnyYy...
SPF v=spf1 include:_spf.google.com include:amazonses.com include:servers.mcsv.net in...
CAALookup not available with standard resolver
Resolved in 403 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 622 ms total
PASS
1 redirect(s), 622 ms total
Info::
Single redirect
Got: https://upf.edu → https://www.upf.edu/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://upf.edu
Info::
Redirect overhead: 622 ms total
Got: 622 ms

https://upf.edu

222 ms · HTTP/1.1

302

https://www.upf.edu/

400 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://upf.edu302222 msHTTP/1.1
2https://www.upf.edu/200400 msHTTP/1.1cloudflare

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 53 URLs
PASS
robots.txt present, sitemap with 53 URLs
Info::
robots.txt is present
Got: 23 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 53 entries
Info::
Sitemap index with 53 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 23 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow:
sitemap.xml 200 OK
Type Sitemap Index URLs 53 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
upf.edu — 27 years, 6 months old, hosted on Google Cloud
PASS
upf.edu — 27 years, 6 months old, hosted on Google Cloud
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

15 days

July 31, 2026

SSL certificate

188 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

27 years, 6 months

Registered February 16, 1999

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.36.90.148

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar
Created February 16, 1999 (27 years, 6 months ago)
Expires July 31, 2026 (3 months)
Last Updated April 7, 2026
Name Servers ns3.upf.edu, ns6.upf.edu, ns2.upf.edu
Registrant Universitat Pompeu Fabra
Hosting
IP Address 34.36.90.148
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (0.4s)
A+
HTTP Probe Timing
Total 222 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
103 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
13 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
223 ms
Total Time Total request time from DNS lookup through full response.
223 ms

Connection waterfall

DNS Lookup 103 ms TCP Connect 7 ms TLS Handshake 13 ms Server Processing 99 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback