Skip to content
https://verywellhealth.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
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.verywellhealth.com/
200https://verywellhealth.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://verywellhealth.com/ → https://verywellhealth.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 6 ms lookup
PASS
2 A records, 6 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 162.159.141.224, 172.66.1.220
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:58::1d8, 2606:4700:7::1d8
Info::
3 nameserver(s) configured
Got: blue.foundationdns.net, blue.foundationdns.org, blue.foundationdns.com
Info::
5 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: 6 ms
Got: 6 ms
A162.159.141.224, 172.66.1.220
AAAA2a06:98c1:58::1d8, 2606:4700:7::1d8
CNAME—
NSblue.foundationdns.net, blue.foundationdns.org, blue.foundationdns.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
MS=ms57306944
facebook-domain-verification=va1elzludh3ojpvwivhbunpopt2eqg
google-site-verification=Ihf_K3YFFOLhCC9MWXkVC0_KdzyMZ6gn1K9ykI8Qcvg
google-site-verification=Ujr6HrmQwXTvZGxh25uZ4zDyPRrm5KDyYI4VxucBI_g
google-site-verification=W-meaM6ot7vYcJ3u7J41l01eeOMoSkRsk5EsCbg5E9w
SPF v=spf1 ip4:64.125.213.247 ip4:216.223.13.247 ip4:34.194.76.185 ip4:35.164.185.21...
CAALookup not available with standard resolver
Resolved in 6 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
Redirect Chain
1 redirect(s), 704 ms total
PASS
1 redirect(s), 704 ms total
Info::
Single redirect
Got: https://verywellhealth.com → https://www.verywellhealth.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 704 ms total
Got: 704 ms

https://verywellhealth.com

153 ms · HTTP/1.1

301

https://www.verywellhealth.com/

551 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://verywellhealth.com301153 msHTTP/1.1cloudflare
2https://www.verywellhealth.com/200551 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:58::1d8, 2606:4700:7::1d8
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:58::1d8, 2606:4700:7::1d8 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 875 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 875 B Sitemaps referenced 2 User-agents Claude-Web, cohere-ai, Perplexity-User, Pinterestbot, CCBot, GPTBot, anthropic-ai, FriendlyCrawler, PerplexityBot, Google-Extended, Pinterest, ImagesiftBot, omgilibot, omgili, *, ChatGPT-User, news-please, Quora-Bot, OAI-SearchBot, ClaudeBot Blocking No — crawling allowed
User-agent: *

Disallow: *.pdf
Disallow: /embed?

User-agent: Pinterest
Disallow:

User-agent: Pinterestbot
Disallow:

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /thmb/

User-agent: OAI-SearchBot
Disallow: /thmb/

User-agent: GPTBot
Disallow: /thmb/

User-agent: news-please
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: ImagesiftBot
Disallow: /

User-agent: FriendlyCrawler
Disallow: /

User-agent: Quora-Bot
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: omgili
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: Google-Extended
Disallow: /


Sitemap: https://www.verywellhealth.com/sitemap.xml

Sitemap: https://www.verywellhealth.com/google-news-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
verywellhealth.com — via MarkMonitor Inc., 20 years, 6 months old
PASS
verywellhealth.com — via MarkMonitor Inc., 20 years, 6 months old
Info::
Domain registered until Jan 19, 2027 (9 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: MarkMonitor 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.
Domain expiry

187 days

January 19, 2027

SSL certificate

72 days

Issued by Let's Encrypt

Domain age

20 years, 6 months

Registered January 19, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:58::1d8

Registrar

MarkMonitor Inc.

Unlocked 3 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 MarkMonitor Inc.
Created January 19, 2006 (20 years, 6 months ago)
Expires January 19, 2027 (9 months)
Last Updated December 18, 2025
Name Servers blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org
DNSSEC Not enabled
Hosting
IP Address 2a06:98c1:58::1d8
Data source: rdap (0.0s)

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 9 ms Server Processing 150 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9eff1cafbd026694-AMS
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9eff1cafbd026694-AMS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback