Skip to content
https://ucla.edu

Infrastructure

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

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.ucla.edu/
200https://ucla.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Connection waterfall

DNS Lookup 314 ms TCP Connect 1 ms TLS Handshake 453 ms Server Processing 151 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
148 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
2 A records, 655 ms lookup
PASS
2 A records, 655 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 15.197.181.170, 3.33.167.235
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns2.dns.ucla.edu, ns1.dns.ucla.edu, ns3.dns.ucla.edu, ns4.dns.ucla.edu
Info::
1 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 (655 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 655 ms
A15.197.181.170, 3.33.167.235
AAAA—
CNAME—
NSns2.dns.ucla.edu, ns1.dns.ucla.edu, ns3.dns.ucla.edu, ns4.dns.ucla.edu
MX
1 smtp.google.com
TXT
openai-domain-verification=dv-85b2FcVGlrPNPqnmddUjAZw7
cisco-ci-domain-verification=6e1def6e2a0868a9419cfea9b832f97ad904319549068403851...
klaviyo-site-verification=YhxBRK
brevo-code:fb7abc76984900d8473089f6bc03c064
google-site-verification=_TtGYbOLonABpIn4mkZlKPmMEulT8077b3Nq_uo0RSM
docusign=027f23b4-d9f0-4ee3-9b88-971151b9799a
atlassian-domain-verification=PYB7nvhaSpskXk/oaGfNqyc/VDgWrQIhzaLLFKIUWI5kT9GXjR...
atlassian-domain-verification=q30yDADVaFnzLVOlyAKq90ajO6mW7k08cAxUyblTa5XYzaa8AA...
google-site-verification=QS5gayPg38zC46YsAx4a9c3v4qTBkn-R69g90pQgpB0
docusign=f69982ad-c0cf-4bc3-93aa-68a7daa19db5
MS=ms75307409
docusign=2443ab46-94b2-4538-963e-c51aecbf883a
jamf-site-verification=d5VBEA2LY6sHcp5mgWJWAQ
adobe-idp-site-verification=66a3bd1a9e558d8448ed38b1258c70ac3915d1a894e70ca110eb...
dtm-domain-verification=Vu-8a4ySCrzp7Vc_AEzyUFB33PIes1UYAU0ZICapRJc
google6505167087
google-site-verification=FLpFoWt5t_e08uK3oeAoq2aTuHe3YhWjqwQfA7YcDaM
atlassian-domain-verification=avKVbiyVZZ1DXWIHaaKKN7aaCdCcJeskGjVundz6pAgcOM9IKX...
klaviyo-site-verification=VUwRd8
google-site-verification=CYG7YvyVNclBzS9iQ5kfNRGyP2TCDkx5Y-zsS5dpmRo
ZOOM_verify_VyMyKp4xRESQCcHLpwFUvw
google-site-verification=Ra3XM5Y8Xemz62pY2Ul98YRmX21qNtvXnzaOZixTFWI
SPF v=spf1 ip4:128.97.0.0/16 ip4:149.142.0.0/16 ip4:131.179.0.0/16 ip4:164.67.0.0/16...
CAALookup not available with standard resolver
Resolved in 655 ms

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), 849 ms total
PASS
1 redirect(s), 849 ms total
Info::
Single redirect
Got: https://ucla.edu → https://www.ucla.edu:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 849 ms total
Got: 849 ms

https://ucla.edu

610 ms · HTTP/1.1

301

https://www.ucla.edu:443/

239 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ucla.edu301610 msHTTP/1.1awselb/2.0
2https://www.ucla.edu:443/200239 msHTTP/1.1Apache/2.4.66 () PHP/7.2.34

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 145 URLs
PASS
robots.txt present, sitemap with 145 URLs
Info::
robots.txt is present
Got: 94 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 145 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 94 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /admission/tuition-and-cost

Sitemap: https://www.ucla.edu/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 145 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ucla.edu — 41 years, 7 months old, hosted on AWS
PASS
ucla.edu — 41 years, 7 months old, hosted on AWS
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: AWS
Got: AS16509
Domain expiry

348 days

July 31, 2027

SSL certificate

148 days

Issued by Amazon

Domain age

41 years, 7 months

Registered April 24, 1985

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

15.197.181.170

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created April 24, 1985 (41 years, 7 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated January 15, 2025
Name Servers ns2.dns.ucla.edu, ns4.dns.ucla.edu, ns3.dns.ucla.edu, ns1.dns.ucla.edu
Registrant UCLA
Hosting
IP Address 15.197.181.170
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.8s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback