Skip to content
https://healio.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 4 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
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1565 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 1565 B Sitemaps referenced 0 User-agents OAI-SearchBot, CCBot, Bytespider, Applebot-Extended, YouBot, ChatGPT, Omgili, omglibot, anthropic-ai, Perplexity.ai, Claude-Web, FacebookBot, GPTBot, Meta-External Fetcher, ChatGPT-User, cohere-training-data-crawler, AmazonBot, Diffbot, Meta-ExternalAgent, Ai2Bot, Perplexity-User, Ai2Bot-Dolma, cohere-ai, *, PerplexityBot, Scrapy, Applebot, magpie-crawler, Jasper.ai, ClaudeBot Blocking No — crawling allowed
User-agent: *
#Disallow: /*/json/
Disallow: /~/hws/
Disallow: /h5news/
Disallow: /utilityapp/
Disallow: /~/user/
#Disallow: /find/
Disallow: /*.aspx
Disallow: /136749668/
Disallow: /6985521/
Disallow: /_Incapsula_Resource
Disallow: /cws/
Disallow: /presentation/
Disallow: /Presentation/
Disallow: /search
Disallow: /Search
Disallow: /shop/
Disallow: /sitecore modules/
Disallow: /sitecore/
Disallow: /sws/
Disallow: /trk/
Disallow: /webservices/
Disallow: /community/
Allow:/sws/feed/news/*

User-agent: Bytespider
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: Scrapy
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: Meta-External Fetcher
Disallow: /

User-agent: AmazonBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: YouBot
Disallow: /

User-agent: Applebot
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /

User-agent: Omgili
Disallow: /

User-agent: omglibot
Disallow: /

User-agent: Ai2Bot
Disallow: /

User-agent: Ai2Bot-Dolma
Disallow: /

User-agent: ChatGPT
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Perplexity.ai
Disallow: /

User-agent: Jasper.ai
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: cohere-training-data-crawler
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.healio.com/
200https://healio.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://healio.com/ https://healio.com/

Consistent

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

Certificate validity

51
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
2 A records, 263 ms lookup
PASS
2 A records, 263 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 107.154.110.198, 107.154.108.198
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns.rackspace.com, ns2.rackspace.com
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 (263 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 263 ms
A107.154.110.198, 107.154.108.198
AAAA
CNAME
NSns.rackspace.com, ns2.rackspace.com
MX
0 healio-com.mail.protection.outlook.com
TXT
MS=ms32864369
globalsign-domain-verification=6025797051738FDE2965AA4C820A57A8
_s8i9sps03c3cc1wpee9ncavluwsayj2
knowbe4-site-verification=63637659c997e74ed2f40e693daa158c
globalsign-domain-verification=gSDR-7ckQ1Z8UNdu8bU83YWY4IUbWueMPdY-NDWpB4
globalsign-domain-verification=174D9B642D4A7BAD9FA2AF75E710F103
globalsign-domain-verification=f162c5c44e81f07f1e1c5d44b418648e
_9blujehg1huycufovakaqd2o0ihbce5
globalsign-domain-verification=8AABECEABF8E98454D68423A6FC92F44
globalsign-domain-verification=e05809d5d8833284b3de621165e1c25f
_kupqdm4jqu9qpcbk5bwrdjtcagnd7zf
globalsign-domain-verification=3B1D12A3BFCFAB45B62B374D2539B25D
globalsign-domain-verification=164D039173775608F1B40D21B5DE298D
globalsign-domain-verification=f304ecbc504ed91dc69f90597a44e35c
globalsign-domain-verification=A1ED45A4C0588429EE78986055E391A5
google-site-verification=tprVxdhicAafUM-ydd3zOWoZO1ASSf8l4LWoNY_kPvk
globalsign-domain-verification=B1749524F095376A4729BF49ADF2AF63
SPF v=spf1 mx a ip4:174.143.106.190 ip4:174.143.106.187 ip4:174.143.106.188 ip4:74.2...
google-site-verification=EBgJxgYkq4J5OtI_F2gZJmZ0O9fRvnkgooMGlIvGjfs
CAALookup not available with standard resolver
Resolved in 263 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.

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), 672 ms total
PASS
1 redirect(s), 672 ms total
Info::
Single redirect
Got: https://healio.com → https://www.healio.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 672 ms total
Got: 672 ms

https://healio.com

93 ms · HTTP/1.1

301

https://www.healio.com/

579 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://healio.com30193 msHTTP/1.1
2https://www.healio.com/200579 msHTTP/1.1Microsoft-IIS/10.0

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
healio.com — via Network Solutions, LLC, 15 years, 9 months old, hosted on INCAPSULA - Incapsula Inc, US
PASS
healio.com — via Network Solutions, LLC, 15 years, 9 months old, hosted on INCAPSULA - Incapsula Inc, US
Info::
Domain registered until Sep 25, 2026 (5 months remaining)
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: Network Solutions, LLC
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: INCAPSULA - Incapsula Inc, US
Got: AS19551
Domain expiry

102 days

September 25, 2026

SSL certificate

51 days

Issued by DigiCert Inc

Domain age

15 years, 9 months

Registered September 25, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

INCAPSULA - Incapsula Inc, US

ASN AS19551

107.154.108.198

Registrar

Network Solutions, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created September 25, 2010 (15 years, 9 months ago)
Expires September 25, 2026 (5 months)
Last Updated August 7, 2023
Name Servers ns.rackspace.com, ns2.rackspace.com
DNSSEC Not enabled
Hosting
IP Address 107.154.108.198
ASN AS19551 (INCAPSULA - Incapsula Inc, US)
Provider INCAPSULA - Incapsula Inc, US
Data source: rdap (0.2s)

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 98 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
14 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
15 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
98 ms
Total Time Total request time from DNS lookup through full response.
98 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 14 ms TLS Handshake 15 ms Server Processing 19 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