If you've come across Liam Powell's blog and wondered whether it's safe to browse, the short answer is yes. This is a straightforward personal blog covering programming topics like Ada and Firefox security. It isn't asking for personal data, logins, or payments, so the typical red flags don't apply here. The site uses modern encryption, has no history of malware, and publishes a privacy policy and terms of service — which is more than most hobby blogs bother with. The domain is relatively young (under a year in the Wayback archive), but that's expected for a new writer starting out. There are no contact details on the homepage, but that's common for blogs where the author doesn't actively solicit messages. If you're looking for opinions or technical rants, blog.liampwll.com looks like a normal, low-risk site. As with any new blog, monitor your own gut feeling about the content, but the infrastructure and reputation signals are clean.
In plain English
This is a personal tech blog with no signs of malicious intent. It has solid security, a clean reputation, and even publishes legal pages that most hobby blogs skip. The only real caveat is that the domain is less than a year old, which is normal for a new personal project. Nothing here suggests risk.
Where the score comes from
Strong security for a personal blog: valid TLS 1.3 certificate with a reputable issuer, no blacklist or Google threat flags. Missing a few browser protections, but not a meaningful risk for a static content site.
The domain is a subdomain of liampwll.com, so the WHOIS gap is normal. The site does have an about page and a legal-entity disclosure, which is more than expected for a personal blog and adds some transparency.
Clean across all blacklists and Google Web Risk. The Wayback archive goes back 8 months, which is not long but consistent with a newer blog. No external review presence, which is typical for this kind of site.
The site provides an about page and business disclosure, but lacks visible contact info and social media links. For a personal blog that's not unusual; the presence of the disclosure page is actually a positive signal.
Both a privacy policy and terms of service are published, which goes beyond what's legally required for a non-commercial personal blog. No cookie consent visible, but no evidence of tracking that would trigger it.
Hosted on Cloudflare with fast load times and a proper sitemap. DNSSEC and email handling are missing, but neither is critical for a read-only blog. The setup is solid and well-maintained.
What we checked
Run this site? Show your score.
Add a trust badge so visitors can see your live score for themselves.
Get your badge →