Skip to content
https://mayoclinic.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
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.

B
DNS Records
1 A records, 302 ms lookup
REVIEW
1 A records, 302 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 129.176.1.88
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: dns1.mayo.edu, a3-66.akam.net, a18-66.akam.net, dns2.mayo.edu, a14-64.akam.net, a10-66.akam.net, a1-70.akam.net, a13-66.akam.net
Info::
3 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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (302 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 302 ms
A129.176.1.88
AAAA—
CNAME—
NSdns1.mayo.edu, a3-66.akam.net, a18-66.akam.net, dns2.mayo.edu, a14-64.akam.net, a10-66.akam.net, a1-70.akam.net, a13-66.akam.net
MX
20 mail8.mayo.edu
20 mail9.mayo.edu
20 mail7.mayo.edu
TXT
google-site-verification=0o8iuRq3C2ji2-i8ajTpcBd1PZyOYjgyFRwCejdj39o
facebook-domain-verification=gnqlpuc6t32rfgtlpsmu7mcz0e30d6
google-site-verification=Y4YQPOeQ7IvHdDP0Yn7uqgrCxFWUTG4W2ixor7BrxZ8
google-site-verification=6Mm6uKAIYzio5exaZKwyNljPHu1FwB6eU4I-hSnMr3g
ncy863bz54x4hbfx0kxpzms73067ls2p
google-site-verification=Ke1F9FxDHjGwSRBikOSa1LEfrKoohWn80AMB1a0iHD8
_uz5g1k3wp3my53wj46cfl46g6oxkp54
CAALookup not available with standard resolver
Resolved in 302 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

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
302 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
Redirect Chain
1 redirect(s), 933 ms total
PASS
1 redirect(s), 933 ms total
Info::
Single redirect
Got: https://mayoclinic.com → https://www.mayoclinic.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 933 ms total
Got: 933 ms
Info::
Cross-domain redirect detected

https://mayoclinic.com

872 ms · HTTP/1.0

301

https://www.mayoclinic.org/

61 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mayoclinic.com301872 msHTTP/1.0BigIP
2https://www.mayoclinic.org/20061 msHTTP/1.1Google Frontend

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 3997 URLs
PASS
robots.txt present, sitemap with 3997 URLs
Info::
robots.txt is present
Got: 2307 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3997 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2307 B Sitemaps referenced 32 User-agents * Blocking No — crawling allowed
User-agent: *

Allow:  /


Disallow: /edu/

Disallow: *.model.json

Disallow: /static/chunks/*

Disallow: /api/*


sitemap: https://www.mayoclinic.org/arabic_condition_consolidated_concepts.xml

sitemap: https://www.mayoclinic.org/arabic_organization_concepts.xml

sitemap: https://www.mayoclinic.org/arabic_patient_consumer_faq.xml

sitemap: https://www.mayoclinic.org/arabic_patient_consumer_recipe.xml

sitemap: https://www.mayoclinic.org/arabic_patient_consumer_video.xml

sitemap: https://www.mayoclinic.org/arabic_patient_consumer_web.xml

sitemap: https://www.mayoclinic.org/arabic_procedure_concepts.xml

sitemap: https://www.mayoclinic.org/chinese_condition_consolidated_concepts.xml

sitemap: https://www.mayoclinic.org/chinese_organization_concepts.xml

sitemap: https://www.mayoclinic.org/chinese_patient_consumer_faq.xml

sitemap: https://www.mayoclinic.org/chinese_patient_consumer_recipe.xml

sitemap: https://www.mayoclinic.org/chinese_patient_consumer_video.xml

sitemap: https://www.mayoclinic.org/chinese_patient_consumer_web.xml

sitemap: https://www.mayoclinic.org/chinese_procedure_concepts.xml

sitemap: https://www.mayoclinic.org/condition_consolidated_concepts.xml

sitemap: https://www.mayoclinic.org/london.xml

sitemap: https://www.mayoclinic.org/organization_concepts.xml

sitemap: https://www.mayoclinic.org/patient_consumer_biography.xml

sitemap: https://www.mayoclinic.org/patient_consumer_drug.xml

sitemap: https://www.mayoclinic.org/patient_consumer_faq.xml

sitemap: https://www.mayoclinic.org/patient_consumer_recipe.xml

sitemap: https://www.mayoclinic.org/symptoms_all.xml

sitemap: https://www.mayoclinic.org/patient_consumer_video.xml

sitemap: https://www.mayoclinic.org/patient_consumer_web.xml

sitemap: https://www.mayoclinic.org/procedure_concepts.xml

sitemap: https://www.mayoclinic.org/spanish_condition_consolidated_concepts.xml

sitemap: https://www.mayoclinic.org/spanish_organization_concepts.xml

sitemap: https://www.mayoclinic.org/spanish_patient_consumer_faq.xml

sitemap: https://www.mayoclinic.org/spanish_patient_consumer_recipe.xml

sitemap: https://www.mayoclinic.org/spanish_patient_consumer_video.xml

sitemap: https://www.mayoclinic.org/spanish_patient_consumer_web.xml

sitemap: https://www.mayoclinic.org/spanish_procedure_concepts.xml
sitemap.xml 200 OK
Type URL Set URLs 3997 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.mayoclinic.com/
200https://mayoclinic.com/

Preferred variant: non-www

HTTP → HTTPS

301http://mayoclinic.com/ → https://www.mayoclinic.org/

Consistent

A
Domain Intelligence
mayoclinic.com — via CSC Corporate Domains, Inc., 29 years, 2 months old, hosted on MAYO - Mayo Foundation for Medical Education and Research, US
PASS
mayoclinic.com — via CSC Corporate Domains, Inc., 29 years, 2 months old, hosted on MAYO - Mayo Foundation for Medical Education and Research, US
Warning::
Domain expires in 89 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 21, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: MAYO - Mayo Foundation for Medical Education and Research, US
Got: AS7973
Domain expiry

35 days

July 21, 2026

SSL certificate

302 days

Issued by Sectigo Limited

Domain age

29 years, 2 months

Registered July 22, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

MAYO - Mayo Foundation for Medical Education and Research, US

ASN AS7973

129.176.1.88

Registrar

CSC Corporate Domains, Inc.

Unlocked 8 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
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created July 22, 1997 (29 years, 2 months ago)
Expires July 21, 2026 (2 months)
Last Updated July 17, 2024
Name Servers a1-70.akam.net, a10-66.akam.net, a13-66.akam.net, a14-64.akam.net, a18-66.akam.net, a3-66.akam.net, dns1.mayo.edu, dns2.mayo.edu
DNSSEC Not enabled
Hosting
IP Address 129.176.1.88
ASN AS7973 (MAYO - Mayo Foundation for Medical Education and Research, US)
Provider MAYO - Mayo Foundation for Medical Education and Research, US
Data source: rdap (0.6s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 194 ms TCP Connect 142 ms TLS Handshake 288 ms Server Processing 142 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