Skip to content
https://uiowa.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
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
142 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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, 131 ms lookup
PASS
1 A records, 131 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 54.163.225.50
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: dns-ext-lc-1.uiowa.edu, dns-ext-itf-1.uiowa.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: 131 ms
Got: 131 ms
A54.163.225.50
AAAA—
CNAME—
NSdns-ext-lc-1.uiowa.edu, dns-ext-itf-1.uiowa.edu
MX
10 uiowa-edu.mail.protection.outlook.com
TXT
yahoo-verification-key=lx2RJkUkXI54qs3azM8ywsc28eK1tgJxGFaouuYYW4I=
teamviewer-sso-verification=cde1d570abed47f98bc15d793290579a
atlassian-domain-verification=ygNri5ECC84kT83856PFXv066QWSKzEEEa9AjYlCnHqaAKNpHr...
google-site-verification=Van5uzYwrIPsFOJlZiEb0df5s2CO1vJa4FnHM8LMSEc
google-site-verification=XcHbHHcSlecyo2gXnBRxfxyiURQUmMITmHuym6UueaM
SPF v=spf1 ip4:128.255.224.128/26 ip4:128.255.173.0/25 ip4:128.255.6.0/23 ip4:128.25...
jamf-site-verification=4ByDVCEDKSxUjP1UmUTO2g
apple-domain-verification=tDq7zCvrNrUcAfae
openai-domain-verification=dv-nvjyGxyTXOp055iSGSBF6M3E
docusign=87525fec-abf7-4589-a5aa-d1cb7e3dc3f9
zone-ownership-verification-5aa04fe02a65855bbdd08495995798ad6bdc73edc967693651de...
mnnAFzvTGU6aSXFfzkLxBINle4iylvbMEQYk9Iuc7lBYqUx9z3Ubw6q/iRQysN68PMuZVQTxcVWwWOLg...
google-site-verification=cRJtf1Ph06yQPxM6LYD04qyawWqAoJt-nOn8djR7Xuc
CAALookup not available with standard resolver
Resolved in 131 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://uiowa.edu

https://uiowa.edu

394 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uiowa.edu200394 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 61 URLs
PASS
robots.txt present, sitemap with 61 URLs
Info::
robots.txt is present
Got: 1855 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 61 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 1855 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#

# robots.txt

#

# This file is to prevent the crawling and indexing of certain parts

# of your site by web crawlers and spiders run by sites like Yahoo!

# and Google. By telling these "robots" where not to go on your site,

# you save bandwidth and server resources.

#

# This file will be ignored unless it is at the root of your host:

# Used:    http://example.com/robots.txt

# Ignored: http://example.com/site/robots.txt

#

# For more information about the robots.txt standard, see:

# http://www.robotstxt.org/robotstxt.html


User-agent: *

# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

Allow: /profiles/*.css$

Allow: /profiles/*.css?

Allow: /profiles/*.js$

Allow: /profiles/*.js?

Allow: /profiles/*.gif

Allow: /profiles/*.jpg

Allow: /profiles/*.jpeg

Allow: /profiles/*.png

Allow: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

# Files

Disallow: /README.txt

Disallow: /web.config

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /search/

Disallow: /user/register

Disallow: /user/password

Disallow: /user/login

Disallow: /user/logout

Disallow: /media/oembed

Disallow: /*/media/oembed

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/search/

Disallow: /index.php/user/password

Disallow: /index.php/user/register

Disallow: /index.php/user/login

Disallow: /index.php/user/logout

Disallow: /index.php/media/oembed

Disallow: /index.php/*/media/oembed

# SiteNow

Disallow: /libraries/*.htm

Disallow: /saml/login

# Bots

crawl-delay: 1
sitemap.xml 200 OK
Type URL Set URLs 61 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.uiowa.edu/
200https://uiowa.edu/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
uiowa.edu — 38 years, 7 months old, hosted on AWS
PASS
uiowa.edu — 38 years, 7 months old, hosted on AWS
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: AWS
Got: AS16509
Domain expiry

412 days

July 31, 2027

SSL certificate

142 days

Issued by Internet2

Domain age

38 years, 7 months

Registered March 30, 1988

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.163.225.50

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created March 30, 1988 (38 years, 7 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated February 23, 2026
Name Servers dns3.uiowa.edu, dns1.uiowa.edu, dns2.uiowa.edu
Registrant University of Iowa
Hosting
IP Address 54.163.225.50
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.8s)
A
HTTP Probe Timing
Total 543 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
133 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
102 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
104 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
542 ms
Total Time Total request time from DNS lookup through full response.
543 ms

Connection waterfall

DNS Lookup 133 ms TCP Connect 102 ms TLS Handshake 104 ms Server Processing 203 ms Content Transfer 1 ms
A+
CDN & Delivery
Varnish (HIT)
PASS
Varnish (HIT)
Info::
Site is served via Varnish CDN
Got: via: varnish
Info::
CDN cache status: HIT
CDN Detected: Varnish
Provider Varnish Cache Status HIT Evidence via: varnish
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback