Skip to content
https://cornell.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://cornell.edu/ → https://www.cornell.edu/

Consistent

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

Certificate validity

77
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
6 A records, 112 ms lookup
PASS
6 A records, 112 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 128.253.173.243, 128.253.173.241, 128.253.173.244, 128.253.173.242, 128.253.173.246, 128.253.173.245
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: drdns.cit.cornell.edu, dns.cit.cornell.edu, cudns.cit.cornell.edu, bigred.cit.cornell.edu, drdns2.cit.cornell.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: 112 ms
Got: 112 ms
A128.253.173.243, 128.253.173.241, 128.253.173.244, 128.253.173.242, 128.253.173.246, 128.253.173.245
AAAA—
CNAME—
NSdrdns.cit.cornell.edu, dns.cit.cornell.edu, cudns.cit.cornell.edu, bigred.cit.cornell.edu, drdns2.cit.cornell.edu
MX
0 cornell-edu.mail.protection.outlook.com
TXT
google-site-verification=CauHX8dfnPle2exSgs6k3OuJ_rPzkV1d6n6E9OFJFO8
facebook-domain-verification=kiwj4xtbf69jsywfq4nlu7a0z81doz
adobe-idp-site-verification=f41c9778dd61e0b903e5daff9095300a03eb9ad4a2a7ce435b4e...
sending_domain44232=26593424e3f9a029c8413a3f66844938dd909eec6d3c1421168e0fa97495...
autodesk-domain-verification=9Y0MrpeHy7LiqjUs0Rpy
7OT7JRZVY1IKZ8J8U84AK2JX4T0J2BM42TL8LSZLV
SPF v=spf1 ip4:128.253.150.144/30 ip4:128.253.150.158 ip4:128.253.150.176 ip4:128.25...
NmwZsJfvHf2DUPwvPqMaLkflPi89l0leQfEkMtPmpxQNqlkPy0anm5LZM/N+sxrW+oJfdGKCyoi/qnhA...
google-site-verification=Gh3jhxuBIdlsH1dgfvJhSGS30sk0OFFvel_I9xQkI5c
apple-domain-verification=R62yGBLwZW9fUKsm
google-site-verification=V6u6xIMwPwKv6d55ZV4VqbkO1mjLlzyvQKkbz4usOM0
CAALookup not available with standard resolver
Resolved in 112 ms

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

https://cornell.edu

415 ms · HTTP/1.1

301

https://www.cornell.edu/

282 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cornell.edu301415 msHTTP/1.1
2https://www.cornell.edu/200282 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 16 URLs
PASS
robots.txt present, sitemap with 16 URLs
Info::
robots.txt is present
Got: 1046 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 16 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 1046 B Sitemaps referenced 0 User-agents *, Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0) SiteCheck-sitecrawl by Siteimprove.com, Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0) LinkCheck by Siteimprove.com, HTML validator: Siteimprove_W3C_Validator/1.3, CSS Validator: Jigsaw/2.3.0 W3C_CSS_Validator_JFouffa/2.0 Blocking No — crawling allowed
User-agent: *

Crawl-Delay: 6
Disallow: /_dynamic_files/

Disallow: /_tasks/

Disallow: /test/

Disallow: /tools/

Disallow: /template/

Disallow: /search/

Disallow: /visit/plan/

Disallow: /video/kaltura/

Disallow: /video/tasks/

Disallow: /server-health-check/



# SiteImprove should ignore these page particularly because they aren't actually used, but are still linked for historical reasons

User-agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0) SiteCheck-sitecrawl by Siteimprove.com

Disallow: /cuinfo/specialconditions/

Disallow: /_includes/header.cfm


User-agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0) LinkCheck by Siteimprove.com

Disallow: /cuinfo/specialconditions/

Disallow: /_includes/header.cfm


User-agent: HTML validator: Siteimprove_W3C_Validator/1.3

Disallow: /cuinfo/specialconditions/

Disallow: /_includes/header.cfm


User-agent: CSS Validator: Jigsaw/2.3.0 W3C_CSS_Validator_JFouffa/2.0

Disallow: /cuinfo/specialconditions/

Disallow: /_includes/header.cfm
sitemap.xml 200 OK
Type URL Set URLs 16 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
cornell.edu — 41 years, 4 months old, hosted on CORNELL - Cornell University, US
PASS
cornell.edu — 41 years, 4 months old, hosted on CORNELL - Cornell University, US
Info::
Domain registered until Jul 31, 2028 (2 years, 3 months remaining)
Info::
Hosting: CORNELL - Cornell University, US
Got: AS26
Domain expiry

776 days

July 31, 2028

SSL certificate

77 days

Issued by Internet2

Domain age

41 years, 4 months

Registered July 15, 1985

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CORNELL - Cornell University, US

ASN AS26

128.253.173.246

Registrar

Registrar unknown

Lock status unknown 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created July 15, 1985 (41 years, 4 months ago)
Expires July 31, 2028 (2 years, 3 months)
Last Updated June 2, 2025
Name Servers bigred.cit.cornell.edu, drdns.cit.cornell.edu, dns.cit.cornell.edu, cudns.cit.cornell.edu, drdns2.cit.cornell.edu
Registrant Cornell University
Hosting
IP Address 128.253.173.246
ASN AS26 (CORNELL - Cornell University, US)
Provider CORNELL - Cornell University, US
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 532 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
112 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
104 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
211 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
532 ms
Total Time Total request time from DNS lookup through full response.
532 ms

Connection waterfall

DNS Lookup 112 ms TCP Connect 104 ms TLS Handshake 211 ms Server Processing 104 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