Skip to content
https://uc.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.uc.edu/
200https://uc.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

http://uc.edu/

HTTP version does not redirect to HTTPS

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), 1338 ms total
REVIEW
1 redirect(s), 1338 ms total
Info::
Single redirect
Got: https://uc.edu → https://www.uc.edu/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1338 ms total
Got: 1338 ms

https://uc.edu

595 ms · HTTP/1.0

301

https://www.uc.edu/

742 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uc.edu301595 msHTTP/1.0BigIP
2https://www.uc.edu/200742 msHTTP/1.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

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

Certificate validity

189
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
  • 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, 656 ms lookup
PASS
1 A records, 656 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 129.137.4.225
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: ucdnsb.uc.edu, ucdnsa.uc.edu, domainkey.journals.uc.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 (656 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 656 ms
A129.137.4.225
AAAA—
CNAME—
NSucdnsb.uc.edu, ucdnsa.uc.edu, domainkey.journals.uc.edu
MX
10 uc-edu.mail.protection.outlook.com
TXT
MS=ms53665973
e2ma-verification=yz1bb
google-site-verification=C_iv7QbxXNurOpxyYFh5fLf0ot6HAsJD2jaxffH8CC0
adobe-idp-site-verification=a457a018c7521a1b9aec806acdcd9cbde2b0c0fec5f83791fe4b...
e2ma-verification=9fqgb
apple-domain-verification=39onPGWa1rM7aOwt
mailerlite-domain-verification=40b3af4339094ec203fac3eb2c76ca448b8d5a57
MS=ms97300204
d365mktkey=1xtohdy6wasjuo3e0hodc1xve
Oyyi08/mpdZN/n4/Qdy6tmEoGI+ZRFHIiRyIKHyhnlJCwiHmUAm23n5OOVKVvGDGYbndMU08NsTZA3Dk...
e2ma-verification=tqlgb
docusign=9e0db14e-9a66-4dc6-8b05-19215ff1a107
asv=8d2e8e2802c887e482a3eb8b8b4f5f04
MS=ms32493827
MS=045195AD9D7F9D60040082F3E2D54AB88833094C
MS=B46B9D52012A9C41A289E46E066AB8B32D828CD8
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.mlsend.com ...
docusign=83075e3b-43be-43e5-8cf4-96869c4e4cc7
d365mktkey=5mjwopy7ccj8t8e0ezl566iod
google-site-verification=MQ9coDFt5h1X0zYAL8cIIykgvrtYKMYhOcCMyf0f0d8
pardot989952=efeaa3be3746473306e44ab33e8d491e541e5ffa035e760d6234e6ec08acd6a7
e2ma-verification=43mcb
e2ma-verification=sbzbb
atlassian-domain-verification=7gS5WxRMMm0EcXaNrKV6S3haguQFevlr5LOCom117nHDkpmiIW...
CAALookup not available with standard resolver
Resolved in 656 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 14469 URLs
PASS
robots.txt present, sitemap with 14469 URLs
Info::
robots.txt is present
Got: 664 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14469 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 664 B Sitemaps referenced 0 User-agents Googlebot, Siteimprove, GPTBot, Bytespider, TikTokSpider, * Blocking No — crawling allowed
# robots.txt for production environments


User-agent: * 

Disallow: /content/dam/*

Disallow: /system/

Disallow: /libs/

Disallow: /apps/

Disallow: /bin/

Disallow: /content/forms/

Disallow: /content/experience-fragments/

Disallow: /content/launches/

Disallow: /content/campaigns/

Disallow: /content/uc/news/articles/legacy/


# Explicitly allow Googlebot

User-agent: Googlebot

Allow: /


# Allow Siteimprove bot

User-agent: Siteimprove

Allow: /


# Block aggressive bots

User-agent: GPTBot

Disallow: /


User-agent: Bytespider

Disallow: /


User-agent: TikTokSpider

Disallow: /


# Explicitly allow Googlebot

User-agent: Googlebot

Allow: /
sitemap.xml 200 OK
Type URL Set URLs 14469 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
uc.edu — 38 years, 11 months old, hosted on UC-DOM - University of Cincinnati, US
PASS
uc.edu — 38 years, 11 months old, hosted on UC-DOM - University of Cincinnati, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: UC-DOM - University of Cincinnati, US
Got: AS20126
Domain expiry

377 days

July 31, 2027

SSL certificate

189 days

Issued by Internet2

Domain age

38 years, 11 months

Registered November 16, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UC-DOM - University of Cincinnati, US

ASN AS20126

129.137.4.225

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created November 16, 1987 (38 years, 11 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated August 29, 2025
Name Servers ucdnsa.uc.edu, ucdnsb.uc.edu
Registrant University of Cincinnati
Hosting
IP Address 129.137.4.225
ASN AS20126 (UC-DOM - University of Cincinnati, US)
Provider UC-DOM - University of Cincinnati, US
Data source: whois (0.9s)
A
HTTP Probe Timing
Total 740 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.
121 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
366 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
740 ms
Total Time Total request time from DNS lookup through full response.
741 ms

Connection waterfall

DNS Lookup 132 ms TCP Connect 121 ms TLS Handshake 366 ms Server Processing 121 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