healthyceleb.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
healthyceleb.com was registered on 12 May 2012 via HOSTINGER operations, UAB and the registry expiry is 12 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/healthyceleb.com.
healthyceleb.com publishes 2 nameservers. DNSSEC is not signed.
healthyceleb.com has 2 IPv4 addresses (104.21.36.202, 172.67.199.73) and 2 IPv6 addresses (2606:4700:3035::6815:24ca, 2606:4700:3037::ac43:c749). The geolocation database places 104.21.36.202 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 44 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, HSTS, HTTP/3, MySQL, PHP, WP Rocket, WordPress and Yoast SEO. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for healthyceleb.com in the checks that ran.
healthyceleb.com was registered on 12 May 2012 via HOSTINGER operations, UAB. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/healthyceleb.com.
| Registered | since 12 May 2012 |
|---|---|
| Created | 12 May 2012 |
| Updated | 9 May 2026 |
| Expires | 12 May 2027 |
| Registrar | HOSTINGER operations, UAB |
| Status | client transfer prohibited |
| Nameservers | joan.ns.cloudflare.com, pablo.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/healthyceleb.com |
healthyceleb.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver joan.ns.cloudflare.com is published for healthyceleb.com in the registration record from https://rdap.verisign.com/com/v1/domain/healthyceleb.com.
Nameserver pablo.ns.cloudflare.com is published for healthyceleb.com in the registration record from https://rdap.verisign.com/com/v1/domain/healthyceleb.com.
healthyceleb.com has 4 address records, 8 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.36.202, 172.67.199.73 |
|---|---|
| AAAA | 2606:4700:3035::6815:24ca, 2606:4700:3037::ac43:c749 |
| NS | joan.ns.cloudflare.com, pablo.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google, us2.mx1.mailhostbox.com (100), us2.mx2.mailhostbox.com (100), us2.mx3.mailhostbox.com (100) |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at healthyceleb.com is "v=spf1 a mx ip4:51.178.153.3 include:_spf.elasticemail.com ~all".
The DMARC text record at _dmarc.healthyceleb.com is "v=DMARC1;p=none;pct=100;rua=mailto:[email protected];ruf=mailto:[email protected]".
IPv4 address 104.21.36.202 answers for healthyceleb.com at resolver 1.1.1.1:53.
IPv4 address 172.67.199.73 answers for healthyceleb.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:24ca answers for healthyceleb.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:c749 answers for healthyceleb.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger us2.mx1.mailhostbox.com has preference 100.
Mail exchanger us2.mx2.mailhostbox.com has preference 100.
Mail exchanger us2.mx3.mailhostbox.com has preference 100.
healthyceleb.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.36.202 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for healthyceleb.com is valid, with 44 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | healthyceleb.com |
| Valid from | 15 September 2026 |
| Valid until | 14 December 2026 |
| Days left | 44 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.healthyceleb.com, healthyceleb.com.
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
WP Rocket is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
Yoast SEO is filed under SEO, WordPress plugins.
The homepage returned HTTP 200 in 386 ms. The target title is 68 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 386 ms |
| Title length | 68 no |
| Quoted title | "Healthy Celeb - Celebrity Height, Weight, Fitness, Fashion, and More" |
| Meta description | "Healthy Celeb is an entertainment site that lets you maintain your health and get celeb news where you can read about your favorite celebs." yes |
| H1 count | 2 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1 |
| Canonical | https://healthyceleb.com/ |
| Language | en-US |
| Links | 237 |
| Images | 81 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for healthyceleb.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
healthyceleb.com is placed in Toronto, Canada.
healthyceleb.com expires on 12 May 2027 according to https://rdap.verisign.com/com/v1/domain/healthyceleb.com.
The registry did not return a person or a company for healthyceleb.com. RDAP often redacts the registrant. The registrar on file is HOSTINGER operations, UAB.
No other indexable reports share this TLD, host, or registrar yet.
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.