Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 2707 ms totalFIX
https://uaf.edu
828 ms · HTTP/1.1
https://www.uaf.edu/
1030 ms · HTTP/1.1
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.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
DTLS Certificate Expiry & RecommendationsAction6 days until leaf cert expires — 5 issues to addressFIX
Certificate validity
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
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNS Records1 A records, 218 ms lookupREVIEW
| 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 |
Multiple A records provide failover if one server goes down.
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.
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'.
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.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BHTTP Probe TimingTotal 1047 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
A+Crawlabilityrobots.txt present, sitemap with 50001 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
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/
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligenceuaf.edu — 30 years, 7 months old, hosted on ALASKA - University of Alaska, USPASS
45 days
July 31, 2026
6 days
Issued by Internet2
30 years, 7 months
Registered February 22, 1996
Status unknown
Protects against DNS spoofing
ALASKA - University of Alaska, US
ASN AS7774
137.229.114.150
Registrar unknown
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Renew the TLS certificate or verify auto-renewal is working