Skip to content
https://umkc.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
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
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.umkc.edu/
200https://umkc.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://umkc.edu/ → https://www.umkc.edu/

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 838 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
458 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
125 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
130 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
838 ms
Total Time Total request time from DNS lookup through full response.
838 ms

Connection waterfall

DNS Lookup 458 ms TCP Connect 125 ms TLS Handshake 130 ms Server Processing 125 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
52 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 840 ms lookup
PASS
1 A records, 840 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 134.193.116.123
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2610:e0:a040:64a2::7b
Info::
3 nameserver(s) configured
Got: ns4.umkc.edu, ns5.umkc.edu, ns3.umkc.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
Warning::
DNS resolution is slow (840 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 840 ms
A134.193.116.123
AAAA2610:e0:a040:64a2::7b
CNAME—
NSns4.umkc.edu, ns5.umkc.edu, ns3.umkc.edu
MX
5 umkc-edu.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.protection.outlook.com ip4:104.130.62.151 ip4:107.23.183.185 ...
adobe-idp-site-verification=276791212a308fa02b35cf206aa6482420b88ff9e987d0dd502c...
atlassian-sending-domain-verification=309c3f0c-32c0-4192-88f9-e01b3a4e2b27
google-site-verification=fjWX4u3FFJQwLgW2nvJG029cSdciCHqfMPmQ0HKIMiI
MS=ms37481391
cisco-ci-domain-verification=79d05abcabb6423c035b08587eac0eb9a2e65ffd23ee82e248f...
d365mktkey=pf2utnhOFeChipg4qbw8G8qingrtpK5WKQ2taxUxPZwx
e2ma-verification=1qubb
facebook-domain-verification=d27lh69uvx88swjz2mn5485kguv2zx
google-site-verification=eOsGxRt_39Br3rmjnFC3UmN-47i0lmPYPPbGqYSYkiU
google-site-verification=4sj-5l8qpTXBKcZbrEhWPfHGoN1_P4uldIg-_qhCrfo
e2ma-verification=k00eb
d365mktkey=uLcatEnE8xIbg26dTG2LTZzdc6utsipHKzpNo7rFfm0x
e2ma-verification=b9nbb
mvjK4Pyj2ao8V5hry+Zxh0g/SutdmwvRHw9IaoCoOBM4JD6pILsZGn2hOIAe6Ei3E42dkYA0vm2MEF6s...
e2ma-verification=85lgb
google-site-verification=xAMUW-_WyKtXFouwiDOykJI2IWgYrDZwDKHl60MSOf0
docusign=8ceb9bc5-aa57-4b77-822a-ec060c9be72c
atlassian-domain-verification=B9bwYMmWIzKhaNG17aNfShbcc54NxQAxPjLWI/EWZy6AQavKcK...
CAALookup not available with standard resolver
Resolved in 840 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), 940 ms total
PASS
1 redirect(s), 940 ms total
Info::
Single redirect
Got: https://umkc.edu → https://www.umkc.edu/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://umkc.edu
Info::
Redirect overhead: 940 ms total
Got: 940 ms

https://umkc.edu

395 ms · HTTP/1.1

302

https://www.umkc.edu/

545 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://umkc.edu302395 msHTTP/1.1Apache
2https://www.umkc.edu/200545 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (114 ms)
PASS
IPv6 reachable (114 ms)
Info::
IPv6 is configured and reachable at 2610:e0:a040:64a2::7b
Got: 114 ms connect
IPv6 Ready
AAAA Records 2610:e0:a040:64a2::7b Connection Reachable (114 ms)
A
Crawlability
no robots.txt, sitemap with 67 URLs
PASS
no robots.txt, sitemap with 67 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 67 entries

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml 200 OK
Type URL Set URLs 67 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
umkc.edu — 37 years, 1 months old
PASS
umkc.edu — 37 years, 1 months old
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Domain expiry

410 days

July 31, 2027

SSL certificate

52 days

Issued by Internet2

Domain age

37 years, 1 months

Registered September 11, 1989

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2610:e0:a040:64a2::7b

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created September 11, 1989 (37 years, 1 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated December 15, 2025
Name Servers ns4.umkc.edu, ns3.umkc.edu, ns5.umkc.edu
Registrant University of Missouri - Kansas City
Hosting
IP Address 2610:e0:a040:64a2::7b
Data source: whois (0.7s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback