Mark Pitblado's personal blog looks like a straightforward hobby site with a few years of history and clean reputation signals. But there's one problem that overshadows everything else: the SSL certificate is invalid, so your browser will warn you that the connection isn't secure. In practical terms, that means the site won't load for most visitors. For a personal blog that doesn't handle payments or logins, a broken certificate is unusual and suggests the site isn't being actively maintained. You might be able to dig up older versions on the Wayback Machine, but trying to visit the live site isn't worth the security warning. If you're looking for the kind of content described (privacy tips, tech thoughts), there are plenty of similar blogs with proper certificates. Markpitblado.me reviews are scarce because it's a small blog, but the core issue here isn't about what others say -- it's about a basic technical failure that makes the site unreachable.
No — markpitblado.me doesn't look safe
In plain English
This personal blog currently has a broken security certificate that makes it impossible to reach the site safely. The rest of the setup looks fine for a hobby blog, but you can't actually visit the page without a security warning. I'd skip it until the owner fixes the certificate.
What you should do now
Don't panic. These steps limit the damage, and the sooner you take them the better.
Don't enter any details
No passwords, card numbers or personal information — even if the site looks professional.
Close the tab
Especially if you got here from an email, text message or social media ad.
Already paid? Call your bank
Contact your bank or card provider right away. They can often stop or reverse a recent payment.
Warn others
Report the site and share this check with anyone who sent you the link.
Where the score comes from
The site's SSL certificate is invalid, which means a secure connection can't be established. This is a basic failure that blocks access entirely. No malware or phishing flags exist, but the certificate issue alone is a dealbreaker for safety.
The domain has been registered for over four years through a reputable registrar. WHOIS privacy is used, which is completely normal for a personal blog. Nothing here raises concern.
The domain hasn't appeared on any blacklists and has a clean Google Web Risk report. It's been on the Wayback Machine for two years with no red flags. This is consistent with a low-profile personal site.
The site has an About page and contact info, which is good for a personal blog. There's no social media presence, but that's not unusual for someone who just wants a quiet corner online.
Missing privacy policy and terms are completely normal for a personal blog that doesn't sell anything or collect sensitive data. No compliance concerns here.
DNSSEC is enabled, email authentication is set up, and the domain resolves correctly. The lack of security headers isn't ideal but isn't a red flag for a simple blog. The sitemap issue is minor.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.