Skip to content
https://umich.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
6 PASS 3 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 97 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 97 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /admin/
Disallow: /announcements/
Disallow: /pingtest/
Disallow: /search
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9efe93bafbc3b6e3-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9efe93bafbc3b6e3-CDG
A
DNS Records
2 A records, 671 ms lookup
PASS
2 A records, 671 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 162.159.140.37, 172.66.0.37
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:7::25, 2a06:98c1:58::25
Info::
4 nameserver(s) configured
Got: dns4.umich.org, dns2.itd.umich.edu, dns3.umich.org, dns1.itd.umich.edu
Info::
2 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 (671 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 671 ms
A162.159.140.37, 172.66.0.37
AAAA2606:4700:7::25, 2a06:98c1:58::25
CNAME—
NSdns4.umich.org, dns2.itd.umich.edu, dns3.umich.org, dns1.itd.umich.edu
MX
0 mx1.a.mail.umich.edu
0 mx2.a.mail.umich.edu
TXT
SPF v=spf1 redirect=_spf.mail.umich.edu
e2ma-verification=zsz
brevo-code:66f1aea179b9dac1e341bc96730a0903
e2ma-verification=1y0cb
google-site-verification=wlYuEbd-YP88QiCM4sz9RHQXkSlspXVdipF-EApRWLw
atlassian-domain-verification=BJherM6FKfh9Y50Eyv/P7vk1rHJVssQEspD7zXqN8IbUzbCsgA...
brevo-code:3adf9f193073a2e465f1178a8226f655
asv=063783b9e2e7b71b1519995753900010
brevo-code:247d3d78ed9e663c50b0a12efce3b095
e2ma-verification=7a9eb
atlassian-domain-verification=aOp85M18PqRt/5EUYxQey4nzX1W9HysNJrHZYX8vmb0Eu2k9t2...
e2ma-verification=nuhgb
e2ma-verification=exibb
jamf-site-verification=81Baq4qavxoOLkx1VulB7w
d365mktkey=74u3ef6g3xjf80kvbz3v70bwb
d365mktkey=733lw7ffo31ti7ozxout3x5l3
google-site-verification=L00w8kdtX1yuVhzX8BrAZcAkJlYZ47T7f9sXnygWI78
google-site-verification=P8BwxmavP7AqtCMjn4NWvFtyZWrP4-JA92e09PiKUTU
SFMC-OQN3tnmPOSz-fGaE5by31y_6Ub4VviyOxT1e3RMt
iContact1258624
atlassian-sending-domain-verification=64ae59ad-0030-417d-9da0-02203860823b
verified-for-netlify=123201_umich_virtual_tour_project
e2ma-verification=bbueb
e2ma-verification=nslgb
google-site-verification=b3J-sqZ0hI_gOlJLW3djTVXFHJYYKE_ojG38_5QJYLM
brevo-code:6a22fe2075c7836824d65669a2b8d509
google-site-verification=oLGMsCZznEy3f0Wxww-5I9AF0m30h9m6Oqi3gclG9nY
atlassian-sending-domain-verification=db703b44-8548-4108-894a-1cf49c66b2dd
google-site-verification=xUO8BnEbTYcXYAAYFj4R1B_gXSBGJGT4el26p0w1RZ4
e2ma-verification=3c9eb
miro-verification=701abed028a466315e4e96a7c16e0ae7b964447f
google-site-verification=Vrq1UHkE6hvICU5PcYAEn-9eY2fAazHkfH_-UprlcDQ
e2ma-verification=460eb
google-site-verification=mEb2ZEP3MoTTKDdiDTgoLUkRr5ycOhriZurxfxMYdCM
google-site-verification=139Z5IVFcA9BZBRUlFv0cgAzAC4yLg8VWpmIcOPNqgM
wpe-verification=readinqwrite
facebook-domain-verification=earrkog9l7y87qxotg01na6vp90ob6
SFMC-5lBIbO82RjFqIQn4tMyyKF3OpLINBTpPQjs6oLJu
dropbox-domain-verification=xibtqs96gswn
vmware-cloud-verification-0612e704-564b-4c09-a310-5c66291ba4ab
brevo-code:27c34e1b5038f713e91b18edc091f7d3
brevo-code:6a1b5714c794582638a3c22137ee387e
brevo-code:8a9b8c8b911006e247c943c7490896e5
e2ma-verification=u60eb
ZOOM_verify_nGh39JkJQSOoOFRUjwPmjA
smartsheet-site-validation=oY0nb96C6xG5_loWLLzVF04btLiZQow5
brevo-code:916190a5216b565989a619ded37b86f7
d365mktkey=V4QCbGNWEzxRcvUOEjaSIlUlkEvJCfVPxdCjV7uSNxIx
apple-domain-verification=QcSjbo9Nu9vbTHeW
e2ma-verification=sk8fb
asv=3409cea16f931a90453c4c4e1fcadf99
e2ma-verification=m3pgb
MS=ms49510218
google-site-verification=ePeJieY3ub5dyqoCqCMxcb00j5MqHIOfff7ev8gvp5M
e2ma-verification=4o6
asv=a7593c4cc71712a01968795279d22556
dropbox-domain-verification=a5yb6qz6602l
mailerlite-domain-verification=4c9bd8e9bcc9532050d764926d28a7b0837605a3
CAALookup not available with standard resolver
Resolved in 671 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.

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+
Redirect Chain
0 redirect(s), 63 ms total
PASS
0 redirect(s), 63 ms total

https://umich.edu

63 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://umich.edu40363 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2606:4700:7::25, 2a06:98c1:58::25
Got: 16 ms connect
IPv6 Ready
AAAA Records 2606:4700:7::25, 2a06:98c1:58::25 Connection Reachable (16 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.umich.edu/
200https://umich.edu/

HTTP → HTTPS

301http://umich.edu/ → https://umich.edu/

Consistent

A+
Domain Intelligence
umich.edu — 41 years, 1 months old
PASS
umich.edu — 41 years, 1 months old
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Domain expiry

348 days

July 31, 2027

SSL certificate

60 days

Issued by Google Trust Services

Domain age

41 years, 1 months

Registered October 7, 1985

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:7::25

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created October 7, 1985 (41 years, 1 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated February 11, 2026
Name Servers dns3.umich.org, dns1.itd.umich.edu, dns4.umich.org, dns2.itd.umich.edu
Registrant University of Michigan -- ITD
Hosting
IP Address 2606:4700:7::25
Data source: whois (0.8s)
A+
HTTP Probe Timing
Total 280 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
219 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
280 ms
Total Time Total request time from DNS lookup through full response.
280 ms

Connection waterfall

DNS Lookup 219 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 21 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