Skip to content
https://rochester.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
1
REVIEW
6
PASS
2
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
2 PASS 6 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), 2685 ms total
REVIEW
1 redirect(s), 2685 ms total
Info::
Single redirect
Got: https://rochester.edu → https://www.rochester.edu/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2685 ms total
Got: 2685 ms

https://rochester.edu

1203 ms · HTTP/1.1

301

https://www.rochester.edu/

1482 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rochester.edu3011203 msHTTP/1.1Apache
2https://www.rochester.edu/2001482 msHTTP/1.1Apache

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 944 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 944 B Sitemaps referenced 0 User-agents ReadableBot, atraxbot/0.2, * Blocking No — crawling allowed
User-agent: atraxbot/0.2
Disallow: /
User-agent: *
Disallow: /adv/advancement/
Disallow: /report/
Disallow: /ITS/reports/
Disallow: /cgi-bin/
Disallow: /tmp/
Disallow: /ITS/web/group/dev/
Disallow: /calendar/
Disallow: /calendar/upload.php
Disallow: /calendar/epicker.php
Disallow: /beta/
Disallow: /ur-cgi-bin/
Disallow: /its/dcs/forms/
Disallow: /ITS/dcs/forms/
Disallow: /college/CCAS/clusters/cluster_search7.html
Disallow: /college/ccas/clusters/cluster_search7.html
Disallow: /its/acs/oge_verifies_form.html
Disallow: /college/alumni/reunion2011/classes/
Disallow: /giving/gec/roll
Disallow: /giving/gec/roll2
Disallow: /college/alumni/reunion/classes/
Disallow: /2013/donors
Disallow: /@rochester/archive/issue.php?iss=2701
Disallow: /currents/V41/N02/Sloan.html
Disallow: /college/ugresearch/ur-upp/
Disallow: /poc-tech/
Disallow: /working/hr/jobs/feeds/
Disallow: /wp-admin/
Disallow: /policies/all/
User-agent: ReadableBot
Disallow: 

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.rochester.edu/
200https://rochester.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://rochester.edu/ https://www.rochester.edu/

Consistent

B
HTTP Probe Timing
Total 1188 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
233 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
235 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
480 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.19 s
Total Time Total request time from DNS lookup through full response.
1.19 s

Connection waterfall

DNS Lookup 233 ms TCP Connect 235 ms TLS Handshake 480 ms Server Processing 240 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
171 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

171
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
  • 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, 244 ms lookup
PASS
1 A records, 244 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.151.77.39
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: ns-external2.rochester.edu, ns-external1.rochester.edu
Info::
8 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 (244 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 244 ms
A128.151.77.39
AAAA
CNAME
NSns-external2.rochester.edu, ns-external1.rochester.edu
MX
10 ppmx6.its.rochester.edu
10 ppmx3.its.rochester.edu
10 ppmx7.its.rochester.edu
10 ppmx4.its.rochester.edu
10 ppmx2.its.rochester.edu
10 ppmx8.its.rochester.edu
10 ppmx1.its.rochester.edu
10 ppmx5.its.rochester.edu
TXT
SFMC-t2dm_vrUidQ2icKpiVcl48icr4KiGits1SNoo3vf
apple-domain-verification=jMTUzYx2TaYoVoZu
smartsheet-site-validation=rcyF_qkX9gbG19E-200lJDSNEfI4NhLn
smartsheet-site-validation=QkMve04pGZHYZe1miacfthXdrq9t2kSA
google-site-verification=N3432SBzvUMr21bWQ--r3Jm6F9Xr-6V3HlyjZMV0VlI
ZOOM_verify_tVjaxJBzyzpZ3yJx7bi29I
wiz-domain-verification=6230f0d481f85f809ec811cd3d965cdf324f8c2307fccd796aa1eb5b...
google-site-verification=8djAyNsFylbBii26ILup3c3y0EDSgj7xKR7JP86_6F8
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
canva-site-verification=qsSID_a7_mmERenifH8oHg
sitecore-domain-verification=ed8276b52b8b4b9291db54e862912229
MS=ms89335153
amazonses:t0h51N4KcnLsmv0GCxTldTulccNcoipzJc6eAi5plW4=
BI33PP2GQL56UKH5AR4O9MCN36
CAALookup not available with standard resolver
Resolved in 244 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+
Domain Intelligence
rochester.edu — 40 years, 1 months old, hosted on UR - University of Rochester, US
PASS
rochester.edu — 40 years, 1 months old, hosted on UR - University of Rochester, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: UR - University of Rochester, US
Got: AS20
Domain expiry

380 days

July 31, 2027

SSL certificate

171 days

Issued by Internet2

Domain age

40 years, 1 months

Registered October 10, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UR - University of Rochester, US

ASN AS20

128.151.77.39

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created October 10, 1986 (40 years, 1 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated November 17, 2025
Name Servers ns-external1.rochester.edu, ns-external2.rochester.edu
Registrant University of Rochester
Hosting
IP Address 128.151.77.39
ASN AS20 (UR - University of Rochester, US)
Provider UR - University of Rochester, US
Data source: whois (1.6s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback