Ivan Gavran's GitHub-hosted blog is exactly what it looks like: a personal space for essays on formal verification, AI, and software correctness. For this kind of site, the signals line up well. The about page names the author, there's a two-year web archive history, and the site has never appeared on any blacklists. The technical setup is basic but functional – modern TLS, a CDN, and no security gaps that would matter for a read-only blog. If you're wondering whether ivan-gavran.github.io is a scam or fake, there's no evidence of that. The only missing pieces are a privacy policy and contact form, but those are standard omissions for a non-commercial personal blog. Overall, this is a typical hobby project from a developer sharing their work. You can trust the content here the same way you'd trust any independent tech blog.
In plain English
This is a personal technical blog run by Ivan Gavran. It's clean, transparent about who runs it, and has none of the warning signs you'd see with a scam site. You can read the articles here without worry.
Where the score comes from
Solid encryption setup with a valid certificate and modern TLS. The missing browser protections like clickjacking blockers are common for static sites and don't create a real risk for a blog.
The site is clearly run by an individual named Ivan Gavran, with an about page and social media links. The domain ownership isn't publicly visible because it's a GitHub Pages subdomain, which is standard and not a red flag here.
No blacklists or Google Web Risk flags. The site has been archived for two years and shows consistent technical content. It's not a popular site, but that's expected for a personal blog.
There's an about page, custom branding, and links to social media. Contact info is missing, but that's normal for a hobby blog where the author isn't offering services or selling anything.
No privacy policy or terms of service are present. For a non-commercial personal blog, legal documents aren't expected. The site doesn't collect user data or process payments, so there's no compliance concern.
The site loads quickly from Fastly's CDN and has a proper sitemap. DNSSEC isn't enabled and email handling isn't set up, but that's typical for a static GitHub Pages site and doesn't affect trust for reading content.
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 →