Skip to content
https://wisc.edu

Infrastructure

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

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: 23 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 23 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: * 
Allow: /
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.wisc.edu/
200https://wisc.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • 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, 340 ms lookup
PASS
1 A records, 340 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 144.92.9.70
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: adns2.doit.wisc.edu, adns4.doit.wisc.edu, adns3.doit.wisc.edu, adns1.doit.wisc.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 (340 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 340 ms
A144.92.9.70
AAAA
CNAME
NSadns2.doit.wisc.edu, adns4.doit.wisc.edu, adns3.doit.wisc.edu, adns1.doit.wisc.edu
MX
10 mxa-007b0c01.gslb.pphosted.com
10 mxb-007b0c01.gslb.pphosted.com
TXT
google-site-verification=eeNB2eTtYXezQH14f8Ugnx8AdZf5OxBKo4VG1uc4hEU
google-site-verification=mXxeq0tbLbPOvRqaUd1iWuG50pD6NdNc6_W-1rmF8QY
google-site-verification=7k2kKl8AIqOYpWTRG01Eh_uGtpRlCRAr2QCkcnKXoYI
MS=ms73471359
adobe-idp-site-verification=522ccfe1-897f-4b0b-877e-d2628e2f6153
google-site-verification=NEyn-YZpHoB9VM-Lck9t9NqXGFnXrTIXqsCGDUwhyPI
atlassian-domain-verification=PrHpnmgrBgHdilLtJWwjJv7zK233bvwigP9gKE9savzE7jOQ/4...
docusign=eaef99ef-533a-4bbf-b2c9-2ca9cf48fe5d
atlassian-domain-verification=KV2mAjd8Bz9s//3RKm9RtqVGFusE80kK0XbLmEVhYaSew2MYJM...
smartsheet-site-validation=KysGL3IvYdXE0wecgsNmAEFJqFAH9jgM
atlassian-domain-verification=6iiuF12j3WiokyCZrA6kg/SkZOPEtakMfrsACpSq9EQuC3NpGZ...
atlassian-domain-verification=ytA3k//Ojg7IrqdEZpn57c/bHdPO/whwLrOiKh5SpdED2O9XdX...
onetrust-domain-verification=09dec2392aeb4de1839dd5c66c44b1be
1password-site-verification=FNJK4BQYWZDAPB75ZKG5BJSH64
atlassian-domain-verification=gebAaRNn0sDQa1Cv6xaIQ0csoPLkxK6PAc7wWRxIRf4w3cfT/j...
SPF v=spf1 include:spf.protection.outlook.com include:_spf.wiscmail.wisc.edu include...
smartsheet-site-validation=1N5odaIr7WAnmtiy7NSf-1WsimV1ZRSB
ZOOM_verify_E78OLta6TIKRJNMD0Wgw5w
CAALookup not available with standard resolver
Resolved in 340 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
Redirect Chain
1 redirect(s), 909 ms total
PASS
1 redirect(s), 909 ms total
Info::
Single redirect
Got: https://wisc.edu → https://www.wisc.edu/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 909 ms total
Got: 909 ms

https://wisc.edu

372 ms · HTTP/1.1

301

https://www.wisc.edu/

536 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wisc.edu301372 msHTTP/1.1Apache
2https://www.wisc.edu/200536 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
wisc.edu — 41 years, 1 months old, hosted on WISC-MADISON-AS - University of Wisconsin Madison, US
PASS
wisc.edu — 41 years, 1 months old, hosted on WISC-MADISON-AS - University of Wisconsin Madison, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: WISC-MADISON-AS - University of Wisconsin Madison, US
Got: AS59
Domain expiry

381 days

July 31, 2027

SSL certificate

38 days

Issued by Let's Encrypt

Domain age

41 years, 1 months

Registered September 30, 1985

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

WISC-MADISON-AS - University of Wisconsin Madison, US

ASN AS59

144.92.9.70

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created September 30, 1985 (41 years, 1 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated March 5, 2026
Name Servers adns1.doit.wisc.edu, adns4.doit.wisc.edu, adns3.doit.wisc.edu, adns2.doit.wisc.edu
Registrant University of Wisconsin
Hosting
IP Address 144.92.9.70
ASN AS59 (WISC-MADISON-AS - University of Wisconsin Madison, US)
Provider WISC-MADISON-AS - University of Wisconsin Madison, US
Data source: whois (1.2s)
A
HTTP Probe Timing
Total 465 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
97 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
122 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
126 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
466 ms
Total Time Total request time from DNS lookup through full response.
466 ms

Connection waterfall

DNS Lookup 97 ms TCP Connect 122 ms TLS Handshake 126 ms Server Processing 122 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