health.blog

#49E0BBFC · Very Safe
100 / 100
ArrowWatchlist · health.blog — Report card
United States 192.0.78.31 Valid HTTPS 9.7 years Knock Knock WHOIS There, Updated

Technical audit of health.blog

We pulled the latest public records for health.blog — registration history, certificate state, hosting infrastructure — and rolled them into the scorecard you see below.

IP Address · Server Location

192.0.78.31
United States · San Francisco

SSL Certificate

Valid HTTPS
E7
Valid Until: 2026-08-22

Registrar

Knock Knock WHOIS There, LLC
Registered On: 2016-10-10
9.7 years

Very Safe

100/100
Verdict at a glance

Technical Overview

The domain health.blog is reachable and resolves to United States via Unknown. Below we walk through the most relevant signals one by one.

Browser compatibility

Mainstream browsers will accept health.blog's TLS configuration if our probe returns "OK". The current value is: OK.

Maturity check

Maturity-wise, health.blog falls in the "mature" bracket — about 9.7 years on record. Most short-lived scams operate on domains under 12 months old, so age helps but does not exclude risk.

Routing & ISP

Traffic to health.blog currently terminates at Unknown in United States — visible to anyone running a traceroute. Hosting-country mismatches with the brand audience can be a useful signal.

Beyond the technical score

A clean technical profile only proves health.blog follows industry plumbing standards. It does NOT prove honest content. Always read the actual site before transacting.

Bottom line

health.blog ends up at 100/100 — that is very_safe in our scale. The result is computed from public technical data only, no human review.

What looks good

  • Reachable on standard ports
  • Certificate issued by a recognised CA
  • No DNS hijack indicators in current records
  • Returns valid SOA and TXT records

What to watch

  • TXT records expose minimal trust hints
  • TLS configuration accepts older cipher suites
  • Limited public reputation data

Frequently Asked Questions

What goes into the health.blog trust rating?
We mix four ingredients: domain age, certificate state, registrar reputation and DNS health, and project the result onto a 0-100 scale.
Is the WHOIS information about health.blog hidden?
Privacy services hide the registrant — this is normal and not a red flag in itself.
Is health.blog on a security blocklist?
Our quick lookup against common public blocklists did not return a hit for health.blog at the time of this report.
Is health.blog a phishing website?
Our scanner does not perform visual similarity checks. We can only confirm that no obvious infrastructure markers (cert mismatch, fresh registration with high traffic) were triggered.
What looks risky about health.blog?
For health.blog we look at: age 9.7 yrs, SSL OK, registrar Knock Knock WHOIS There, LLC and hosting in United States. Any single weak point can drag the technical confidence down.

This report is generated automatically from public technical signals. It is not legal or financial advice.

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →