herbalife.com — domain analysis
herbalife.com describes itself as "Willkommen bei Herbalife: einem Branchenführer mit über 40 Jahren Erfahrung. Entdecke unsere Premium-Produkte sowie Tipps für ein gesundes Leben – werde Teil unserer globalen…".…
herbalife.com describes itself as "Willkommen bei Herbalife: einem Branchenführer mit über 40 Jahren Erfahrung. Entdecke unsere Premium-Produkte sowie Tipps für ein gesundes Leben – werde Teil unserer globalen…". It is built on Next.js, registered in 1998, served from Frankfurt am Main, Germany. It has a valid HTTPS certificate, 4 of 6 common security headers.
What is herbalife.com about?
The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:
- unterst ×7
- entdecken ×7
- herbalife24 ×6
- eine ×6
- deine ×5
- herbalife ×4
- hrung ×4
- wellness ×4
- tzung ×4
- nach ×4
Does herbalife.com publish the usual trust pages?
Found: about. Not found at the usual addresses:
contact, privacy, terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does herbalife.com compare with other domains analysed here?
Measured against the 69 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 64% of them (median 408ms) |
|---|---|
| Security headers | More than 83% of them |
| Domain age | Older than 70% of them |
Related domains in this index
Analysed domains sharing the same network (AS16625 Akamai Technologies, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was herbalife.com registered?
herbalife.com was registered on 23 February 1998, which makes it about 28 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is MarkMonitor Inc..
Registration runs until 22 February 2027.
The domain carries 3 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 23 February 1998 |
|---|---|
| Expires | 22 February 2027 |
| Registrar | MarkMonitor Inc. |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited |
Where is herbalife.com hosted?
The first address resolves to infrastructure in Frankfurt am Main, Germany.
The network is operated by Akamai Technologies (AS16625 Akamai Technologies, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is herbalife.com running on?
herbalife.com exposes 1 identifiable technology: Next.js.
The build output indicates a server-rendered JavaScript framework, which means the HTML served to crawlers is generated ahead of time rather than assembled in the browser.
- Next.js
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 282ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 270KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | not disclosed |
|---|---|
| Compression | gzip |
| Page size | 276,793 bytes |
| Declared language | de-DE |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 63 characters, inside the range that displays without truncation.
The meta description is 185 characters and will be cut short in most result layouts.
25 of 39 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.
| Title | Willkommen bei Herbalife | Weltmarktführer im Bereich Ernährung (63 chars) |
|---|---|
| Meta description | Willkommen bei Herbalife: einem Branchenführer mit über 40 Jahren Erfahrung. Entdecke unsere Premium-Produkte sowie Tipps für ein gesundes Leben – werde Teil unserer globalen Community. (185 chars) |
| H1 | MACHE WELLNESS ZU EINER BEWEGUNG (1 on the page) |
| Canonical | https://www.herbalife.com/de-de |
| Open Graph title | Willkommen bei Herbalife | Weltmarktführer im Bereich Ernährung |
| Headings / images | 1 H2s, 39 images (25 without alt text) |
Is herbalife.com served over a valid certificate?
The HTTPS certificate is issued by DigiCert Inc and is
valid until 2026-10-07, which is 2 days from the date of this check. It covers
51 hostnames.
- Herbalife.com
- *.core.herbalife.com
- *.dev1-herbalife.com
- *.goherbalife.com
- *.herbalife-aruba.com
- *.herbalife.com
- *.herbalife.se
- *.herbalifenutrition.com
- *.qa1-herbalife.com
- *.stg1-herbalife.com
- *.uat1-herbalife.com
- *.zus2prs.goherbalife.com
The certificate expires in 2 days. If renewal is not automated this is close enough to be worth checking today.
It covers 51 hostnames, which is characteristic of a shared or platform-issued certificate rather than one bought for this domain alone.
Which security headers does it set?
4 of 6 are set (HSTS, X-Content-Type-Options, X-Frame-Options, Permissions-Policy). Absent: Content Security Policy, Referrer-Policy.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000 ; includeSubDomains ; preload |
| Content Security Policy | no | — |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | no | — |
| Permissions-Policy | yes | accelerometer=(self), camera=(self), geolocation=(self), gyroscope=(self), magnetometer=(self), microphone=(self), payme |
How is DNS configured for herbalife.com?
| IP addresses | 2.23.245.184 |
|---|---|
| Reverse DNS | a2-23-245-184.deploy.static.akamaitechnologies.com |
| Name servers | a13-67.akam.net, a28-66.akam.net, a18-65.akam.net, a14-64.akam.net, a3-67.akam.net, a1-90.akam.net |
| Mail (MX) | herbalife-com.mail.protection.outlook.com (pri 10) |
| SPF | v=spf1 mx include:spf.protection.outlook.com include:_spf-a.herbalife.com include:_spf-b.herbalife.com include:_spf-c.herbalife.com include:_spf.salesforce.com include:amazonses.com include:_spf.psm.knowbe4.com include:shops.shopify.com -all |
| TXT records | 21 |
herbalife.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to a2-23-245-184.deploy.static.akamaitechnologies.com, which usually names the hosting provider.
Who runs DNS and mail for herbalife.com?
DNS is operated by Akamai rather than self-hosted name servers.
Mail is handled by Microsoft 365.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about herbalife.com?
1 of 1 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
Can herbalife.com be spoofed in email?
DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 451 bytes and names
9 user-agent groups.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.herbalife.com/sitemap.xml
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| claudebot | allowed |
| perplexitybot | allowed |
| google-extended | allowed |
1 sitemap is declared in robots.txt, which gives crawlers a direct list of URLs.
Named AI crawlers are explicitly allowed (gptbot, claudebot, perplexitybot, google-extended).
What structured data does the homepage publish?
- WebSite
- SearchAction
- Organization
The homepage publishes 3 structured data types: WebSite, SearchAction, Organization.
What does herbalife.com load from third parties?
The homepage pulls resources from 2 third-party hosts (assets.adobedtm.com, rum.hlx.page). Each one sees the visitor IP and user agent on every page load.
1 cookie is set before any interaction (bm_sz). 1 lacks the Secure flag.
The page links or refers to X/Twitter, Facebook, Instagram, YouTube.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| bm_sz | no | no | none/unset |
Does herbalife.com settle on one address?
The www address redirects, so the site settles on one canonical hostname.
How easily can herbalife.com be crawled?
A sitemap index is served at https://www.herbalife.com/sitemap.xml listing 661 entries.
What tracking does herbalife.com run?
No analytics or advertising trackers were detected on the homepage of herbalife.com, which is unusual for a commercial site.
How does herbalife.com look when shared?
3 of 5 social preview tags are set. Missing: og:image, twitter:card.
How are images, fonts and scripts handled?
39 images on the homepage, 39 of them lazy-loaded (100%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
The page pulls 4 external stylesheets and 16 external scripts, with 3 carrying defer or async.
Responses carry Akamai and Varnish/Fastly edge edge headers, so content is served from a CDN rather than straight from the origin.
Is herbalife.com accessible and current?
The page uses 13 landmark elements and 79 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index herbalife.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 303 internal and 6 external links across 6 outside hosts.
Visible text is only 4.6% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is herbalife.com delivered?
The HTML is served with Cache-Control: max-age=1800, s-maxage=0.
No favicon is declared in the markup.
The TLS certificate also covers 1 subdomain: core.herbalife.com.
- core.herbalife.com
Frequently asked questions
Does herbalife.com set the usual HTTP security headers?
It sets 4 of 6. The ones not present are: Content Security Policy, Referrer-Policy.
Does herbalife.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is herbalife.com built with?
The homepage exposes these fingerprints: Next.js. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own herbalife.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →
How we estimate this
Every figure on this page is compiled from the public sources cited above and given as a low–typical–high range rather than a single false-precise number. Where costs vary by location we scale the national typical using published state price levels. We recheck figures on a set schedule and stamp each report with the date last verified. We are independent and are never paid to change a number — see how we price things.
