Skip to content
https://ucsb.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
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.ucsb.edu/
200https://ucsb.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ucsb.edu/ → https://www.ucsb.edu/

Consistent

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

Certificate validity

34
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, 13 ms lookup
PASS
1 A records, 13 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.185.0.3
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:12a:8000::3, 2620:12a:8001::3
Info::
3 nameserver(s) configured
Got: ns1-ext.ucsb.edu, ns2-ext.ucsb.edu, ns3-ext.ucsb.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
Info::
DNS resolution time: 13 ms
Got: 13 ms
A23.185.0.3
AAAA2620:12a:8000::3, 2620:12a:8001::3
CNAME—
NSns1-ext.ucsb.edu, ns2-ext.ucsb.edu, ns3-ext.ucsb.edu
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
nintex.5eab2f5c65e22e0cb4175fa8
docusign=2db76460-ed70-4304-ac67-b0c4c3dbd8a0
docusign=d6165297-785e-475b-af29-230656dc9b6b
google-site-verification=HvW8p2akv29b_3SxKwREgQW3sWcdM4W_tBkFOBYUnCc
google-site-verification=1WJ9YafLWZub7TeqsJsmgkjWBmi78PeMfX9X8nAsBCo
google-site-verification=f1VE4Bh7TPu8csbCDpSdss9eNiDHm8nFz_WpwvFpFMc
google-site-verification=eEMgnykr-j3h3QqEc1Y3rY_IYJ61sLo30TicTXyEoRw
adobe-idp-site-verification=89eae806e1d6d933ad1bbc1dae756a88bbf2bd0b29a325541c9d...
SPF v=spf1 include:_spf.ucsb.edu ~all
e2ma-verification=6rtgb
e2ma-verification=qptgb
hcp-domain-verification=b83443062ec1a87d668a27b333cd650da55f407313cb6cc88c1f327a...
dtm-domain-verification=KzMugmmXJb3wvAHQSoQ2_KaATqj1YtscPtGVPyA7V5c
atlassian-domain-verification=qCi2CsOO2pP3njZFSIP5D0ydoujdKY1UDvOfLfk1PitUfyjhkt...
apple-domain-verification=Eod6qXeOKdrSMbsj
CAALookup not available with standard resolver
Resolved in 13 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), 165 ms total
PASS
1 redirect(s), 165 ms total
Info::
Single redirect
Got: https://ucsb.edu → https://www.ucsb.edu/ (301)
Info::
WWW normalization redirect

https://ucsb.edu

20 ms · HTTP/1.1

301

https://www.ucsb.edu/

146 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ucsb.edu30120 msHTTP/1.1Pantheon
2https://www.ucsb.edu/200146 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2620:12a:8000::3, 2620:12a:8001::3
Got: 1 ms connect
IPv6 Ready
AAAA Records 2620:12a:8000::3, 2620:12a:8001::3 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 141 URLs
PASS
robots.txt present, sitemap with 141 URLs
Info::
robots.txt is present
Got: 2027 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 141 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 2027 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
sitemap.xml 200 OK
Type URL Set URLs 141 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ucsb.edu — 39 years, 6 months old
PASS
ucsb.edu — 39 years, 6 months old
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Domain expiry

381 days

July 31, 2027

SSL certificate

34 days

Issued by Let's Encrypt

Domain age

39 years, 6 months

Registered April 27, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8001::3

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created April 27, 1987 (39 years, 6 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated December 1, 2025
Name Servers ns1-ext.ucsb.edu, ns2-ext.ucsb.edu, ns3-ext.ucsb.edu
Registrant University of California, Santa Barbara
Hosting
IP Address 2620:12a:8001::3
Data source: whois (0.3s)
A+
HTTP Probe Timing
Total 28 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
12 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.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
28 ms
Total Time Total request time from DNS lookup through full response.
29 ms

Connection waterfall

DNS Lookup 12 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 8 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-ewr-kewr1740054-EWR
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-ewr-kewr1740054-EWR
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback