Skip to content
https://miami.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 1438 ms total
FIX
3 redirect(s), 1438 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
3-hop chain could be reduced to 1 hop
Redirect directly from https://miami.edu to https://welcome.miami.edu/
Warning::
Redirect overhead: 1438 ms total
Got: 1438 ms
Info::
Cross-domain redirect detected

https://miami.edu

305 ms · HTTP/1.1

301

https://www.miami.edu/

338 ms · HTTP/1.1

301

http://welcome.miami.edu/

287 ms · HTTP/1.1

301

https://welcome.miami.edu/

508 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://miami.edu301305 msHTTP/1.1Microsoft-IIS/10.0
2https://www.miami.edu/301338 msHTTP/1.1Microsoft-IIS/10.0
3http://welcome.miami.edu/301287 msHTTP/1.1Apache
4https://welcome.miami.edu/200508 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://miami.edu to https://welcome.miami.edu/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://miami.edu/ → http://www.miami.edu/

HTTP version does not redirect to HTTPS

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

Certificate validity

159
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
2 A records, 84 ms lookup
PASS
2 A records, 84 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.178.128.80, 52.149.175.238
Info::
No IPv6 (AAAA) records
Info::
7 nameserver(s) configured
Got: a3-64.akam.net, a14-64.akam.net, a16-67.akam.net, a22-65.akam.net, e1.miami.edu, a7-65.akam.net, a1-122.akam.net
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
Info::
DNS resolution time: 84 ms
Got: 84 ms
A172.178.128.80, 52.149.175.238
AAAA—
CNAME—
NSa3-64.akam.net, a14-64.akam.net, a16-67.akam.net, a22-65.akam.net, e1.miami.edu, a7-65.akam.net, a1-122.akam.net
MX
10 mxb-0070ba02.gslb.pphosted.com
10 mxa-0070ba02.gslb.pphosted.com
TXT
asv=cded384eb9e63f5a309a8d6b83be4866
vmware-cloud-verification-58425a25-8591-4324-ab2d-d84079daf85c
82e26b83-aad7-4a29-88dc-7a38eb1f3837
yahoo-verification-key=U0R0Qth2xLT41zz24dYUIPWGEy2EMeswNQP14OENwoo=
d365mktkey=1a8bmrgw68j8xy3v8f2ghso55
ePMDlQ1WeZcbbNByB8sbw+RkRC6t+ytuddjCPw7epVvQlkIrMmtLBnfhzWU+xz/QdJAOQgv2P7HXU3be...
e2ma-verification=h8pgb
d365mktkey=5b1uxn26z1h9kdmh6l8cfdkd5
docusign=976e96ac-0bb0-4d2e-8b80-1d357f6327dd
google-site-verification=_XjVLooDf-mw5rTPAS7yb1qhXIFO6i6VJHRqhcuwuho
cisco-ci-domain-verification=5c4535182cd793359752ab769f672828754fd8b02b5f4d4ee06...
_spf.salesforce.com
hibp-verify=dweb_h21a0dozzl85zyciyslfjnk9
smartsheet-site-validation=FlKzvNGFFgCJn8NTh0gG1ADRK77FJ8Si
canva-site-verification=aAwfD3Toabc8cxBt9HFeTw
reftab-domain-verification=c73b2c8ef90e89979510440c628debf7
uber-domain-verification=1b75b275-b726-4913-a662-78e6558285e1
apple-domain-verification=Ze3n7HnNBrfGGEw3
yahoo-verification-key=uRx2KQC2IJ+swahJPBz4S94SwnZgWPhDr1nKe2stPGk=
adobe-idp-site-verification=47a823b8-a77f-465f-b881-dedc9faac723
e2ma-verification=vhmgb
ciscocidomainverification=3c41fd034402b930a3303af01c5719360f5d59d2a1d8ca24e44b1e...
facebook-domain-verification=wgymd9ja0kvyigr78tnuq6t62ycsam
google-site-verification=7EqI0Eq-N8o7V9nyLVHuBBD_kiH4pCcT5ijoLcB1X1Y
MS=ms40877570
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
ZOOM_verify_s2FpU5L9TRHePhChqn9o6t
docusign=772e287f-e342-4f5a-aff7-56ff320d3c7d
pardot748963=41fb8b46b958b3145bf43881d3c9ede5ddf2f6d80bec0ab6d3c34baa9282a2ab
smartsheet-site-validation=4ObKgkt_NNtZ0kF9jjnjWkc41140FtCH
CAALookup not available with standard resolver
Resolved in 84 ms

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+
Crawlability
robots.txt present, sitemap with 40 URLs
PASS
robots.txt present, sitemap with 40 URLs
Info::
robots.txt is present
Got: 130 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 40 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 130 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *

Disallow: /_assets/php/

Disallow: /_assets/apache-error-pages/


Sitemap: https://welcome.miami.edu/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 40 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
miami.edu — 39 years, 3 months old, hosted on Microsoft Azure
PASS
miami.edu — 39 years, 3 months old, hosted on Microsoft Azure
Info::
Domain registered until Jul 31, 2028 (2 years, 3 months remaining)
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

744 days

July 31, 2028

SSL certificate

159 days

Issued by Internet2

Domain age

39 years, 3 months

Registered July 23, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

172.178.128.80

Registrar

Registrar unknown

Lock status unknown 7 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created July 23, 1987 (39 years, 3 months ago)
Expires July 31, 2028 (2 years, 3 months)
Last Updated June 12, 2025
Name Servers a1-122.akam.net, a14-64.akam.net, a16-67.akam.net, a22-65.akam.net, e1.miami.edu, a3-64.akam.net, a7-65.akam.net
Registrant University of Miami
Hosting
IP Address 172.178.128.80
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: whois (0.9s)
A
HTTP Probe Timing
Total 690 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
163 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
329 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
691 ms
Total Time Total request time from DNS lookup through full response.
691 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 163 ms TLS Handshake 329 ms Server Processing 163 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