Skip to content
https://wayne.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 1 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.

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

Certificate validity

113
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, 660 ms lookup
PASS
1 A records, 660 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 141.217.1.160
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: 2606:9700:4208:101::abcd
Info::
2 nameserver(s) configured
Got: ns.wayne.edu, ns2.wayne.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 (660 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 660 ms
A141.217.1.160
AAAA2606:9700:4208:101::abcd
CNAME—
NSns.wayne.edu, ns2.wayne.edu
MX
10 wayne-edu.mail.protection.outlook.com
TXT
d365mktkey=oYSG0SBTNINalvBK5lFaYz3dykmJLLxNYtXHpxNMBOox
docusign=80e55b4b-ad0b-4c9d-8aca-f36b2ebba5f9
amazonses:cuHOUvV6kRZpssGG752KDsZrzjCaAMuQBPJhSzSXIEU=
canva-site-verification=GGt_1KI6BxAMPDYiUu0n_w
jamf-site-verification=yWzbfagiObsB2uRtb0tPcQ
d365mktkey=sM5E4xJwSQeX4xb39zbXeZ6hE2BagjcoLHUs5v1o0Akx
SPF v=spf1 ip4:206.107.42.249 ip4:206.107.42.254 ip4:52.86.188.131 ip4:52.43.50.148 ...
d365mktkey=Ll0Rfh1BnveYTB86yfkQBUTRXxbCINYPNs9BvwIFwl0x
adobe-idp-site-verification=ddbeb555fc8a20d286f6b1d043d01bd99ee50a5dba59579cfb58...
ZOOM_verify_3dMxWZWESlOPEjXlkigf_w
google-site-verification=hZnBBTNOyCDFYD7cz3-qD3SjduTy79m4aaDPydN88VU
yahoo-verification-key=05AvU90HDTEUU33VPjZQtaqMIbzPvsPt0mHhKQatfoA=
brevo-code:e4cdc9c04f471ce35db5b24dc5ab50c8
d365mktkey=m9O2gjLNkg7o7uvVPyIHbTdN68rfz3hj3L5yfwQBqqEx
FITA2T5UEVFGQ1PSSG6A88864D
MS=ms12725973
CAALookup not available with standard resolver
Resolved in 660 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://wayne.edu

https://wayne.edu

751 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wayne.edu200751 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (129 ms)
PASS
IPv6 reachable (129 ms)
Info::
IPv6 is configured and reachable at 2606:9700:4208:101::abcd
Got: 129 ms connect
IPv6 Ready
AAAA Records 2606:9700:4208:101::abcd Connection Reachable (129 ms)
A+
Crawlability
robots.txt present, sitemap with 7242 URLs
PASS
robots.txt present, sitemap with 7242 URLs
Info::
robots.txt is present
Got: 94 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7242 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 94 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /styleguide/
Disallow: /search

Sitemap: https://wayne.edu/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 7242 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.wayne.edu/
200https://wayne.edu/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
wayne.edu — 38 years, 9 months old
PASS
wayne.edu — 38 years, 9 months old
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Domain expiry

15 days

July 31, 2026

SSL certificate

113 days

Issued by Internet2

Domain age

38 years, 9 months

Registered January 29, 1988

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:9700:4208:101::abcd

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar
Created January 29, 1988 (38 years, 9 months ago)
Expires July 31, 2026 (3 months)
Last Updated October 13, 2025
Name Servers ns.wayne.edu, ns2.wayne.edu
Registrant Wayne State University
Hosting
IP Address 2606:9700:4208:101::abcd
Data source: whois (0.8s)
A
HTTP Probe Timing
Total 769 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
148 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
123 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
128 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
769 ms
Total Time Total request time from DNS lookup through full response.
769 ms

Connection waterfall

DNS Lookup 148 ms TCP Connect 123 ms TLS Handshake 128 ms Server Processing 370 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback