Skip to content
https://ku.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
4 PASS 3 REVIEW 2 FIX
D
HTTP Probe Timing
Action
Total 2346 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
33 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
71 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.28 s
Total Time Total request time from DNS lookup through full response.
2.35 s

Connection waterfall

DNS Lookup 32 ms TCP Connect 33 ms TLS Handshake 71 ms Server Processing 2.15 s Content Transfer 64 ms
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.ku.edu/
200https://ku.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ku.edu/ https://ku.edu/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 183 ms lookup
PASS
1 A records, 183 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 129.237.135.76
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.ku.edu, ns4.ku.edu, ns2.ku.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
Info::
DNS resolution time: 183 ms
Got: 183 ms
A129.237.135.76
AAAA
CNAME
NSns1.ku.edu, ns4.ku.edu, ns2.ku.edu
MX
10 ku-edu.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.ku.edu include:spf_ext.ku.edu include:spf.protection.outlook....
atlassian-domain-verification=gQCZy44gSs5Yx57YSpBxrMfmLMivsakMdzreSxsnjfNW6MvR14...
successfactors-site-verification=OGExNzcwYmNiZDk1Y2U3MTljYTMxMTQ4MDc0ODJhMGFiNDA...
d365mktkey=3ueavnqhjw5qfn7d21527vbre
d365mktkey=4w2j821zye63c3hnlh0nyxpoi
google-site-verification=3Tl0zBArHvPOpUbBMT7-11tzsjBm7wNlWgDjzCyNA8Q
autodesk-domain-verification=qMG6J-b2W3t7FDzKDCcx
AAN9AKL6LXPKZ9N7ESKASI4OKO7NQFFTPIFKBGTGD
apple-domain-verification=JhKfJomP9t7riHbm
asv=48acefc2e47d4b28b157a840e0a1d784
smartsheet-site-validation=bXQOKEcoHu0i4aZzbnPcuCmrkyfYqgZv
google-site-verification=r7LEBI_MR5CuwNS_EwTv8rVxkEZ3j8BYbYYPGol3dok
wRKpeJXZH9um0P8Z8nHveU807tX/siME1gdYYbrhxs+dNygXN6XIdKzSjEndF7Zwc2rzqthffH96Dqze...
google-site-verification=l2tSxHkgr5ZAiDpKrnBZq3u626h_PbdVnWIGwyI7iMU
atlassian-domain-verification=hd9p3p0eZsHHSZykEaj9cUsC3OoqPYmaW4zCwEwqJuMFhPnO/O...
atlassian-domain-verification=wAajbyjQxjyyOTEBzp7eP+K/ca8h+MTLhCH3Pf8OGiHhj1DFkJ...
e2ma-verification=x7bgb
CAALookup not available with standard resolver
Resolved in 183 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://ku.edu

https://ku.edu

253 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ku.edu200253 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 2027 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 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

A+
Domain Intelligence
ku.edu — 29 years, 9 months old, hosted on UKANS - University of Kansas, US
PASS
ku.edu — 29 years, 9 months old, hosted on UKANS - University of Kansas, US
Info::
Domain registered until Jul 31, 2028 (2 years, 3 months remaining)
Info::
Hosting: UKANS - University of Kansas, US
Got: AS2496
Domain expiry

744 days

July 31, 2028

SSL certificate

80 days

Issued by Internet2

Domain age

29 years, 9 months

Registered December 23, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UKANS - University of Kansas, US

ASN AS2496

129.237.135.76

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created December 23, 1996 (29 years, 9 months ago)
Expires July 31, 2028 (2 years, 3 months)
Last Updated December 12, 2025
Name Servers ns3.ku.edu, ns4.ku.edu, ns1.ku.edu, ns2.ku.edu
Registrant University of Kansas
Hosting
IP Address 129.237.135.76
ASN AS2496 (UKANS - University of Kansas, US)
Provider UKANS - University of Kansas, US
Data source: whois (0.3s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback