bultrowicz.com

A blog by Michał “Butla” Bultrowicz — Butlablog

Last scanned 52 min agoCompare with another site →

Built with

No platform, CMS or framework detected. Detection is passive: it only sees what a site exposes in its HTML, headers and cookies, so custom or well-hidden stacks show up as nothing rather than as a guess. The page does announce itself as Docutils 0.19: https://docutils.sourceforge.io/.

Also detected

Libraries: jQuery
Infrastructure: Nginx

Overview

Status: alive
Registered: 2016-08-10 (10 years ago)
First seen here: 2026-09-22
Security grade: F (40/100, from headers & TLS)
Privacy score: 100/100 (0 third-party script hosts, 0 tracking/marketing services)
Hosting: DigitalOcean, LLC · AS14061 · United Kingdom
Server header: nginx/1.24.0 (Ubuntu)
Response time: 70 ms to first byte, measured from our crawler
TLS certificate: Let's Encrypt · TLSv1.3 · expires 2026-12-17
Language: en
Mobile-ready: yes (viewport meta tag)
RSS / Atom feed: yes
Linked to from: 10 other sites seen so far

What to fix

Add Strict-Transport-Security
Header: Strict-Transport-Security: max-age=31536000; includeSubDomains
Add a Content-Security-Policy
Limits which scripts can run, and is the main defense against XSS. Start with Content-Security-Policy-Report-Only to test.
Add X-Content-Type-Options
Header: X-Content-Type-Options: nosniff
Prevent clickjacking
Header: X-Frame-Options: DENY (or a CSP frame-ancestors directive).
Add a Referrer-Policy
Header: Referrer-Policy: strict-origin-when-cross-origin
Publish an SPF record
A DNS TXT record listing who may send email for this domain, which prevents spoofing.
Publish a DMARC record
A TXT record at _dmarc.<domain>; start with v=DMARC1; p=none; to monitor.

Security & email signals

✓ HTTPS
✗ HSTS
✗ Content-Security-Policy
✗ X-Content-Type-Options
✗ X-Frame-Options
✗ Referrer-Policy
✗ Permissions-Policy
✗ SPF record
✗ DMARC record
✗ DKIM record
✓ Cookies set securely
✓ Has real content (not an empty shell)
✓ Valid TLS certificate

Badge

Show this site's security grade in a README or footer:

<a href="https://webtelemetry.dev/site/bultrowicz.com"><img src="https://webtelemetry.dev/badge/bultrowicz.com.svg" alt="Security grade"></a>

Generated automatically from passive, publicly observable data. Think something here is wrong or want this profile removed? See /bot. Machine-readable: JSON.