Skip to content
https://webmd.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 5 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: 926 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 926 B Sitemaps referenced 0 User-agents *, AdsBot-Google, CCBot, ChatGPT-User, ClaudeBot, Doximity, GPTBot Blocking No — crawling allowed
# Robots.txt file WebMD

# Updated 3/4/2026 (CONSFE-362)


User-agent: *

Disallow: */search/search_results/

Disallow: /500

Disallow: /aim/

Disallow: /api/

Disallow: /bipolar-disorder/video/bipolar-fatherhood

Disallow: /bipolar-disorder/video/bipolar-toolbox

Disallow: /breast-cancer/bc-treatment-21/provider-select

Disallow: /click*

Disallow: /dna

Disallow: /drugs/2/search*

Disallow: /drugs/ReportAbuse.aspx*

Disallow: /kapi/

Disallow: /mm/

Disallow: /my-library

Disallow: /news/header.php

Disallow: /pill-identification/search-results*

Disallow: /search/2/api/

Disallow: /Share.aspx*

Disallow: /sponsored/

Disallow: /static/

Disallow: /story/

Disallow: /webmd_static_vue/


User-agent: AdsBot-Google

Disallow: /mm/


User-agent: CCBot

Disallow: /


User-agent: ChatGPT-User

Disallow: /


User-agent: ClaudeBot

Disallow: /


User-agent: Doximity

Disallow: /


User-agent: GPTBot

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.webmd.com/
200https://webmd.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://webmd.com/ https://www.webmd.com/

Consistent

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

Connection waterfall

DNS Lookup 29 ms TCP Connect 97 ms TLS Handshake 725 ms Server Processing 99 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

75
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+
DNS Records
1 A records, 75 ms lookup
PASS
1 A records, 75 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 207.231.204.56
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: amir.ns.cloudflare.com, vita.ns.cloudflare.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: 75 ms
Got: 75 ms
A207.231.204.56
AAAA
CNAME
NSamir.ns.cloudflare.com, vita.ns.cloudflare.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
SFMC-OzW5wNjIBpdXFIg-AnBOn39Kj0umwTThgg5Yfwm7
wrike-verification=MTkwMjI3MDo2ZmJlNDE2N2FiMzllNjE0MDdiYjJjN2NmOWE2ZDA5YTA4YzliZ...
google-site-verification=WUMAoNjAhtgdb0eWxrQUo1aE3Rvz4ApU-CRm0Dtw1-A
SPF v=spf1 include:spf.zohomail360.com include:mail.zendesk.com include:spf.protecti...
facebook-domain-verification=w0zj3kf18imt845aplzy38efaox23t
google-site-verification=8ndI6dMiz3lrBkg2YbMR_RMa3lihncz9VgamtujOXQo
v=DKIM1; k=rsa; p=MIIBIjANB" "gkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAglkiu3gC0LOVJ8u...
globalsign-domain-verification=-8kpivpbgMACeanB8hk0ansSLujEnFA_i1ukkwKY1Y
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAglkiu3gC0LOVJ8uWLf...
adobe-idp-site-verification=273cee5ce44db359754043668120f4ccf0076e55a5fe663ce1bc...
google-site-verification=tbLtuRpVup8Z965hPBFprdgjOoJw4VJqv1mkzJl84VE
s6fk0y05g78y03fjjkwynkb69sf9ggbb
google-site-verification=XIEa3Mj4EhHxjtJ0RrN1tSfKYwyPFKyhoKFKZrfTn3Y
a65ccd5662904680b467ccd142e9670b
google-site-verification=BR_G5pH8GUkbNgoC1nOdBpj3UZINgHU5Q9KltDsEGBM
e0cfe10a46f74485a608c50a63f263f9
CAALookup not available with standard resolver
Resolved in 75 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.

A
Redirect Chain
1 redirect(s), 832 ms total
PASS
1 redirect(s), 832 ms total
Info::
Single redirect
Got: https://webmd.com → https://www.webmd.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 832 ms total
Got: 832 ms

https://webmd.com

697 ms · HTTP/1.1

301

https://www.webmd.com/

135 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://webmd.com301697 msHTTP/1.1Apache
2https://www.webmd.com/200135 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
webmd.com — via MarkMonitor Inc., 28 years, 5 months old, hosted on WEBMD-IDC2-AS - WebMD, LLC, US
PASS
webmd.com — via MarkMonitor Inc., 28 years, 5 months old, hosted on WEBMD-IDC2-AS - WebMD, LLC, US
Info::
Domain registered until Apr 5, 2027 (11 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.
Info::
Hosting: WEBMD-IDC2-AS - WebMD, LLC, US
Got: AS46617
Domain expiry

265 days

April 5, 2027

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

28 years, 5 months

Registered April 6, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WEBMD-IDC2-AS - WebMD, LLC, US

ASN AS46617

207.231.204.56

Registrar

MarkMonitor Inc.

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 MarkMonitor Inc.
Created April 6, 1998 (28 years, 5 months ago)
Expires April 5, 2027 (11 months)
Last Updated March 4, 2026
Name Servers amir.ns.cloudflare.com, vita.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 207.231.204.56
ASN AS46617 (WEBMD-IDC2-AS - WebMD, LLC, US)
Provider WEBMD-IDC2-AS - WebMD, LLC, US
Data source: rdap (0.4s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback