Skip to content
https://uwm.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
266 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

266
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
A+
DNS Records
1 A records, 142 ms lookup
PASS
1 A records, 142 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.200.83.238
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: uwmdns2.uwm.edu, uwmdns1.uwm.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: 142 ms
Got: 142 ms
A52.200.83.238
AAAA—
CNAME—
NSuwmdns2.uwm.edu, uwmdns1.uwm.edu
MX
0 uwm-edu.mail.protection.outlook.com
TXT
adobe-idp-site-verification=530a4a64-8534-491f-abf7-32f0b5181869
ZOOM_verify_6FcVWA0eReCVkghafD9R6g
facebook-domain-verification=3h0exhauhuywcgulqeurbktt558552
apple-domain-verification=iPRxMRYTCx4oRcvL2i794GGsPQrDd4c1_y59mzn6Oh8
v=DKIM1; k=rsa; t=y; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzx3OoXBzNTyxB...
autodesk-domain-verification=b746h82TSsva0__iXWl9
jamf-site-verification=mRQ9vwBIy8e6kO8GRuDlcw
asv=c769fb154600130ccbf4dbb931147c85
SPF v=spf1 include:spf.protection.outlook.com ip4:129.89.209.50/32 ip4:129.89.216.10...
spf2.0/pra include:spf.protection.outlook.com ip4:129.89.209.50/32 ip4:129.89.21...
MS=ms87597351
atlassian-domain-verification=H7pYD/xx7sBh8Y7/TMCoew/S88ZUOlpcxqVLmz3uz6xygeg5iN...
CAALookup not available with standard resolver
Resolved in 142 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.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://uwm.edu

https://uwm.edu

56 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uwm.edu20056 msHTTP/1.1Apache/2.4.58 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 1271 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
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 1271 B Sitemaps referenced 0 User-agents EdenCrawler, *, SemrushBot, Bytespider, BLEXBot, ShapBot, ImagesiftBot, MJ12bot, DataForSeoBot, Baiduspider Blocking No — crawling allowed
## Allowed AI Crawlers (Company/Service: User agent name):
## ChatGPT GPTBot (And OAI-SearchBot?)
## Claude: ClaudeBot
## Gemini: Google-Extended
## Perplexity: PerplexityBot
## Google AI Mode (N/A, uses Uses Googlebot + Google-Extended bots)
## Google AI Overviews (N/A, uses Uses Googlebot + Google-Extended bots)
## Copilot (uses Bingbot)
## Meta AI: (uses Meta-ExternalAgent and facebookexternalhit)


User-agent: SemrushBot
Disallow: /

User-agent: ImagesiftBot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: MJ12bot
Disallow: /

User-agent: DataForSeoBot
Disallow: /

User-agent: BLEXBot
Disallow: /

User-agent: Baiduspider
Disallow: /

User-agent: EdenCrawler
Disallow: /

User-agent: ShapBot
Disallow: /

User-agent: *
Allow: /
Disallow: /languages/alum-feature-on-ryan-lee-mader-uwm-class-of-2008/
Disallow: /letters-science/news/alum-goes-from-german-class-to-germany-and-beyond/

## For Events Calendar
Disallow: *post_type=tribe_events*
Disallow: *hide_subsequent_recurrences=*
Disallow: *tribe-bar-date=*
Disallow: *tribe-venue=*
Disallow: *eventDisplay=*
Disallow: *eventDate=*
Disallow: *paged=*
Disallow: *pagename=*
Disallow: *shortcode=*
Disallow: *ical=*
Disallow: *outlook-ical=*
Disallow: *related_series=*
Disallow: *tribe_geofence=*
sitemap.xml 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

https://www.uwm.edu/
200https://uwm.edu/

HTTP → HTTPS

302http://uwm.edu/ → https://uwm.edu/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
uwm.edu — 37 years, 4 months old, hosted on AWS
PASS
uwm.edu — 37 years, 4 months old, hosted on AWS
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: AWS
Got: AS14618
Domain expiry

410 days

July 31, 2027

SSL certificate

266 days

Issued by Internet2

Domain age

37 years, 4 months

Registered June 21, 1989

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.200.83.238

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created June 21, 1989 (37 years, 4 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated July 22, 2024
Name Servers uwmdns1.uwm.edu, uwmdns2.uwm.edu
Registrant University of Wisconsin - Milwaukee
Hosting
IP Address 52.200.83.238
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.3s)
A+
HTTP Probe Timing
Total 62 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
59 ms
Total Time Total request time from DNS lookup through full response.
63 ms

Connection waterfall

DNS Lookup 27 ms TCP Connect 7 ms TLS Handshake 11 ms Server Processing 14 ms Content Transfer 4 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback