Skip to content
https://uky.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
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.

B
Redirect Chain
1 redirect(s), 1363 ms total
REVIEW
1 redirect(s), 1363 ms total
Info::
Single redirect
Got: https://uky.edu → https://www.uky.edu/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1363 ms total
Got: 1363 ms

https://uky.edu

490 ms · HTTP/1.1

301

https://www.uky.edu/

873 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uky.edu301490 msHTTP/1.1Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1
2https://www.uky.edu/200873 msHTTP/1.1Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1

See the visual redirect chain in the HTTP Probe tab →

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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.uky.edu/
200https://uky.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://uky.edu/ → https://www.uky.edu

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

190
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
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 333 ms lookup
PASS
1 A records, 333 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.163.35.46
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: sndc1.net.uky.edu, sndc2.net.uky.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 (333 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 333 ms
A128.163.35.46
AAAA—
CNAME—
NSsndc1.net.uky.edu, sndc2.net.uky.edu
MX
10 uky-edu.mail.protection.outlook.com
TXT
d365mktkey=lvnbxpv16zb3b3fq87qgx1w2
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:mailgun.org ~all
e2ma-verification=p2ggb
airtable-verification=08fe52ad65a781013d8f064036e4c3f3
asv=e9dbc7f36805498586275767226fbeaa
6VKUoai4abGMplE1Jiq3h85euv/TsSNHn1etOi0KTa1aW4UhtimO70Bav5S3j4N9Ba+QyVRLm5Rzc0dE...
cisco-ci-domain-verification=5580f815cfed6657f1b22c300d35a6b66f22360d25db7e5bd3b...
amazonses:MKxf4B6NI9ZrPl7eGND1YGMb307IRLN0eYwoDUWKWpE=
jamf-site-verification=4gvAry71nzooLy5CaIwegQ
00DDp0000017aZL=1TBcx00000002ra
e2ma-verification=lsrfb
e2ma-verification=1l8fb
cisco-ci-domain-verification=24fd540ebf927ee4d9183d90e2c13628480017b3b0172e2fb2b...
teamviewer-sso-verification=a65f5d182f1a4703aaf53ea73510508f
brevo-code:59b3a18744d24f960bd78166f34f87c5
docusign=d8f39723-ce11-4288-b54f-6ee4a7856058
google-site-verification=EiUlE6YVyy5Boyg8nVab7FLE6blJkVjH-LIhgjv8rMQ
d365mktkey=4j4h68c79ebqj3qp73n3jtwxv
intersight=92ce70cc8c0776e6ce23d47d46d3d0c952091278684c4b49b17d0368908677e9
airtable-verification=a7013d71581bcea786dc1aa07cc9d89d
00Df4000004kS17=1TBVq0000000eYZ
CAALookup not available with standard resolver
Resolved in 333 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.

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+
Crawlability
robots.txt present, sitemap with 32 URLs
PASS
robots.txt present, sitemap with 32 URLs
Info::
robots.txt is present
Got: 2027 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 32 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 32 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
uky.edu — 39 years, 5 months old, hosted on UKYEDU - University of Kentucky, US
PASS
uky.edu — 39 years, 5 months old, hosted on UKYEDU - University of Kentucky, US
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: UKYEDU - University of Kentucky, US
Got: AS23162
Domain expiry

19 days

July 31, 2026

SSL certificate

190 days

Issued by Internet2

Domain age

39 years, 5 months

Registered May 27, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UKYEDU - University of Kentucky, US

ASN AS23162

128.163.35.46

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar
Created May 27, 1987 (39 years, 5 months ago)
Expires July 31, 2026 (3 months)
Last Updated July 1, 2025
Name Servers sndc2.net.uky.edu, sndc1.net.uky.edu
Registrant University of Kentucky
Hosting
IP Address 128.163.35.46
ASN AS23162 (UKYEDU - University of Kentucky, US)
Provider UKYEDU - University of Kentucky, US
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 661 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
132 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
129 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
265 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
662 ms
Total Time Total request time from DNS lookup through full response.
662 ms

Connection waterfall

DNS Lookup 132 ms TCP Connect 129 ms TLS Handshake 265 ms Server Processing 136 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback