Infrastructure - https://uaf.edu BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 2707 ms total

FIX

2 redirect(s), 2707 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.uaf.edu/

Redirect overhead: 2707 ms total

Got: 2707 ms

https://uaf.edu

828 ms · HTTP/1.1

301

https://www.uaf.edu/

1030 ms · HTTP/1.1

302

https://www.uaf.edu/uaf/

849 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://uaf.edu	301	828 ms	HTTP/1.1	Apache
2	https://www.uaf.edu/	302	1030 ms	HTTP/1.1	Apache
3	https://www.uaf.edu/uaf/	200	849 ms	HTTP/1.1	Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

D

TLS Certificate Expiry & Recommendations

Action

6 days until leaf cert expires — 5 issues to address

FIX

Certificate validity

6

days left

0d 30d 60d 90d+

Renew urgently — under 14 days remaining

Recommended actions

Renew certificate — 6 days remaining
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

D

CDN & Delivery

Action

No CDN detected

FIX

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 (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B

DNS Records

1 A records, 218 ms lookup

REVIEW

1 A records, 218 ms lookup

Resolves to 1 IPv4 address(es)

Got: 137.229.114.150

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns1.uaf.edu, aduans-f.alaska.edu, aduans-a.alaska.edu, ns2.uaf.edu

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (218 ms)

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

Got: 218 ms

A	137.229.114.150
AAAA	—
CNAME	—
NS	ns1.uaf.edu, aduans-f.alaska.edu, aduans-a.alaska.edu, ns2.uaf.edu
MX	10 seven.alaska.edu
TXT	apple-domain-verification=LEgsruKoS26Vjo5h
CAA	Lookup not available with standard resolver

Resolved in 218 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

HTTP Probe Timing

Total 1047 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

216 ms

TCP Connect

207 ms

TLS Handshake

418 ms

Time to First Byte

1.05 s

Total Time

1.05 s

Connection waterfall

DNS Lookup 216 ms TCP Connect 207 ms TLS Handshake 418 ms Server Processing 207 ms Content Transfer 0 ms

A+

Crawlability

robots.txt present, sitemap with 50001 URLs

PASS

robots.txt present, sitemap with 50001 URLs

robots.txt is present

Got: 330 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 50001 entries

robots.txt does not reference a 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 330 B Sitemaps referenced 0 User-agents ZanranCrawler, Baiduspider, * Blocking No — crawling allowed

User-agent: ZanranCrawler
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: *
Disallow: /templates/
Disallow: /ua-templates/
Disallow: /roxen-files/
Disallow: /__internal/
Disallow: /_internal/
Disallow: /__frame/
Disallow: /coursefinder/search-results/
Disallow: /anla/collections/search/resultDetail.xml
Disallow: /hr/

sitemap.xml 200 OK

Type URL Set URLs 50001 entries Valid XML Yes

Sample URLs:

A

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.uaf.edu/

200https://uaf.edu/

Preferred variant: non-www

HTTP → HTTPS

302http://uaf.edu/ → https://uaf.edu/

Use a permanent redirect (301 or 308) instead of a temporary one

A+

Domain Intelligence

uaf.edu — 30 years, 7 months old, hosted on ALASKA - University of Alaska, US

PASS

uaf.edu — 30 years, 7 months old, hosted on ALASKA - University of Alaska, US

Domain registered until Jul 31, 2026 (3 months remaining)

Hosting: ALASKA - University of Alaska, US

Got: AS7774

Domain expiry

EXPIRED

July 31, 2026

SSL certificate

6 days

Issued by Internet2

Domain age

30 years, 7 months

Registered February 22, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ALASKA - University of Alaska, US

ASN AS7774

137.229.114.150

Registrar

Registrar unknown

Lock status unknown 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Domain has EXPIRED — renew immediately to avoid total site outage
Renew the TLS certificate or verify auto-renewal is working

Registrar

Created February 22, 1996 (30 years, 7 months ago)

Expires July 31, 2026 (3 months)

Last Updated June 3, 2025

Name Servers ns1.uaf.edu, aduans-a.alaska.edu, ns2.uaf.edu, aduans-f.alaska.edu

Registrant University of Alaska Fairbanks

Hosting

IP Address 137.229.114.150

ASN AS7774 (ALASKA - University of Alaska, US)

Provider ALASKA - University of Alaska, US

Data source: whois (1.2s)