Stillthinking.net presents itself as a personal blog featuring math derivations and essays, but a trust assessment has to look past the content to the operation behind it. For a personal blog, anonymity is normal — many individual writers choose not to publish their real name or contact details. What's more concerning here is the combination of that anonymity with a domain that's only been live for three days and zero archived history. The site could be a genuine new project from someone who values privacy, but it could also disappear tomorrow with no way to reach the author or recover anything you've engaged with. The technical setup is fine: fast load times, a valid certificate, and clean blacklist status. But the missing contact info and about page mean there's no accountability. If you're thinking of subscribing via email or relying on this as a source, treat it as provisional until the site has had time to build a track record. Most legitimate long-running personal blogs eventually add an about page and a way to reach the author — that's the simplest signal to watch for here. Without it, stillthinking.net remains a question mark rather than a resource you can count on.
No — stillthinking.net doesn't look safe
In plain English
I'd hold off on trusting stillthinking.net for anything serious. The big issue is that the site is only three days old with no contact info, no about page, and no track record. It has solid technical basics, but you can't tell who wrote the content or whether the site will be here next week.
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 uses a valid modern certificate on a fast TLS 1.3 connection, but it falls short by accepting outdated TLS 1.0/1.1 and not setting basic browser protections like clickjacking prevention. For a personal blog this is a missed opportunity, not a crisis.
The domain is only three days old and registered through Cloudflare, which is neutral. But with no about page, no team info, and no contact details, there's effectively no way to tell who runs this blog. For a personal blog that's common, but paired with the new domain it still raises the question of whether it'll stick around.
No blacklists, no Google Safe Browsing threats, and the site is live and working. But the Wayback Machine has zero snapshots, which is expected for a three-day-old domain. There's simply no track record to evaluate yet.
There's no about page, no contact information anywhere on the homepage, and no social media links. A personal blog can get away with some anonymity, but the complete absence of any way to reach the author is a real gap. Readers can't confirm the person behind the writing or report issues.
Missing privacy policy and terms of service are normal for a personal blog that doesn't collect payments or sensitive data. The site does collect email addresses via a subscribe form, which is a minor GDPR consideration, but for a hobby project this is not a red flag.
The site uses Cloudflare's CDN and name servers, loads in under 100ms, and has a clean DNS setup. No email server is configured, which is fine for a blog that doesn't send mail from its own domain. DNSSEC is not enabled, which is a voluntary extra layer most personal sites skip.
What we checked
Think this verdict is wrong?
Site owners can request a fresh scan. Scores update automatically as signals change.